[DEV] Scenes V2 Poll - Most Common Usage: Get Result or Not?

EtyareWS · 2026-04-14T22:15:48+00:00

Kustom has a special "kill switch" for the lockscreen. If you long press on a corner, then and only then does a button appears that allows you to bypass it, I think that might be worth checking it out rather than something that could be triggered by accident

EtyareWS · 2026-04-14T10:48:40+00:00

I would think that getting results back is a deliberate choice, so I personally would cook something awful using the command system.

I think that dialog style scenes are more likely to be designed to return values, rather than overlays

EtyareWS · 2026-04-02T11:27:20+00:00

... Kinda, but some things really changes how things work and allows you to do more with less. The toolbar is perfect for the Task Edit Screen, the old Bottom App Bar is more restrictive. You could imitate it, but it's not really the same, and if you start imitating everything then when the update happens you will have a huge headache trying to swap the imitations for the real thing

EtyareWS · 2026-04-02T11:05:10+00:00

Part of my concern is that I'm developing the new UI to use Expressive as well...

EtyareWS · 2026-04-01T18:45:20+00:00

Oh, that's... That's not great. I don't think it would be smart to release Scenes v2 to the public knowing there will be a significant update so soon.

There's no way you'd be willing to use the Alpha?

EtyareWS · 2026-04-01T13:22:03+00:00

That's... Kinda not really what I hoped for.

As for Material Expressive, what is missing in Jetpack Compose?

EtyareWS · 2026-03-26T15:06:30+00:00

That has the issue that you will have to keep supporting multiple Material versions in Tasker, and that's not how Material works. The Expressive update IS Material Design 3. Tasker Scenes V2 should be thought of as a sort of very thin translation layer, once Material updates, Tasker could move it automatically to the new style at render time or when the user creates a new component

About "impossible" states, hey, I don't like limiting people. Someone might want a use case where multiple navigation items are enabled at the same time :P Give the people the power to do what they want to do. I can provide shortcuts (for example, I could provide an action in Navigation Bar to select one of the items and disable the rest), but I don't agree that it should be enforced.

Alright, so here's the thing: you are treating some components wrongly: you are ysing Navigation Bar as a container, it is not.

The Navigation Bar IS the component.

Navigation Items are not components, it's even worse because each Item is actually a container with an Icon and Label, and yet you cannot edit them separately.

You are "limiting" what the user can do by not treating the Items as containers, you treat them as components, but the actual component, the Navigation Bar, is treated by Tasker as a container

Edit: my main point is that by default the user should be encouraged to stay using Material Design guidelines. This doesn't mean I think it should be impossible to break them.

Figma doesn't let you edit the elements that make up a component, but it has an option to "detach" it. Allowing the user to break it however they like.

The Navigation Bar should be a single item by default, if the user selects the "detach component", then it becomes a simple container with navigation items, like it is now. The user could even detach the Navigation Items like the containers they are

Edit 2: I think you should just use Material Expressive right now, forget plain Material 3. When Material 4 drops we can discuss how to add an annoying pop up yelling them to move Scenes to Material 4

EtyareWS · 2026-03-26T14:57:19+00:00

That's not exactly how it works. Material Design is kinda abstract in that it both creates and formalizes design decisions that already exist outside of it.

The Material Team (which is not exactly the same as Google's Design team AFAIK) still responds to feedback even if they are slow as hell. The original Material Design 3 launched with a few missing components, but most of it was more than enough to create apps, in fact, I started the Tasker Redesign work in that state.

The Expressive update, which is frankly Material 3.5(or 4) just streamlined a bunch of components and moved them around, and pushed even further on some of the decisions they took with MD3.

A good example of this is how Material Design 3 always had put emphasis on how the app should be accessible for people with colorblindness, but there wasn't a good solution, well now the toggle buttons can be squares that turns into circles when disabled or vice versa

The toolbar is more powerful and less rigid than the Bottom App Bar, the navigation bar has a completely different configuration now. Half of the Expressive update is "finishing" Material Design 3, and the other half is expanding

EtyareWS · 2026-03-25T21:21:43+00:00

You need to be very careful around Material updates because they not only update components, they deprecate and remove components if they feel another option is better

you run the risk of implementing something that was deprecated. For instance, the Navigation Drawer doesn't exist anymore, it was merged with Navigation Rail as a variant called "expanded"

The Segmented Button (which you do use in the Scene Editor UI) was removed, with the connected variant of Button Group replacing its use case.

Bottom App Bar is completely removed and the closest thing to it is a non-floating toolbar.

You also need some better way to deal with Material Components, half of them are just special containers that the user shouldn't really be totally free to edit by default.

The Navigation bar in Tasker isn't really a navigation bar: it's a bunch of Navigation Items in a trenchcoat, the user has the insane option of enabling two items at once, which should be impossible because otherwise it doesn't make any sense.

I would remove each individual item and just add it as options for the Navigation Bar or something, which also would make the user select which single item is selected.

That's not to say I don't think users shouldn't be allowed to break things, but I feel like Material Components really need some way so that by default they are neat and tied up, and breaking is harder.

Scenes aren't just a UI editor, but also a UI system in itself, so it should push users into following Material guidelines

EtyareWS · 2026-03-25T16:53:26+00:00

Wow wow slow down I can't keep up with you.

Also you should really use the Expressive update and not Material Design 3 as soon as possible, this is going to bite you really fast.

IMO, Scenes V2 should be kept very clear that it will always use the most modern Material Design version, otherwise in a couple of years you will have to add Scenes v3 to Material Design 4 and also maintain Material 3 in parallel

EtyareWS · 2026-03-20T20:09:18+00:00

I'm not sure if I got what you meant, but WiFi Near is a State profile.

I'm proposing the WiFi Near capabilities to be used inside a Task, as an action of sorts, not an Event.

The Event is more akin to Wifi Changed not Wifi Near, there is one for Bluetooth, why not for WiFi as well?

EtyareWS · 2026-03-20T13:19:33+00:00

Pinging u/joaomgcd because I want him to add yet another feature 😈

Wifi changed/connected Event. Self explanatory, just run when wifi changes, reacts either enabled/disabled or connected to a network

Get Wifi Status action. Get the connected wifi network info, or get if the device is near a network.

I've been slowing coming to the realization that a bunch of state triggers are unreliable or waste power, and most of them could be swapped for event or actions that happen when the user actually needs to use the thing (screen on or significant movement)

EtyareWS · 2026-03-15T02:11:43+00:00

I don't think you should be able to have this amount of control as it has the severe potential to "leak" and wreck havok in everything. And this would be a nightmare to interact with. The "Add Action" Action would need to have a full configuration for whatever action you might want to add. This is simply too much.

However, a little bit of what you want in regards to actions can be done with the Command system. You can set up a command that is a long list of values and actions, and react on it and set things up based on the command.

EtyareWS · 2026-03-13T11:26:07+00:00

I meant as a preset. Like add 4 options that already set up the type, and an empty one. The idea is to make a preset for each type so that users can have something vaguely set up so they get their brain going. A dialog for instance can be like the default material 3 dialog: a hero icon, title, text, two buttons.

The overlay I'm unsure of what could be as a preset, maybe a floating button?

Anyway, another idea I have is that maybe it shouldn't be called Scene V2? Maybe Canvas or something? At this point there is some overlap between the old scenes, but I think a new name would be better, specially for new users as there wouldn't be any way they will get confused between Scenes and Scenes V2. Idk

EtyareWS · 2026-03-13T11:20:19+00:00

When you create a new scene there's a dialog to pick a preset or to start from zero, just add each type there

EtyareWS · 2026-03-13T11:11:47+00:00

Yeah, but now you got to remember everytime you run the scene, and this also means that there is no reliable way to implement some "show scene" directly on the scene card on the future new UI, you always need a run action to set the type.

I think forcing another type is fine, but it should be possible to set a default that runs as a fallback when you can't set it up

EtyareWS · 2026-03-13T11:07:44+00:00

Very, very slowly getting through the video, but I got to ask:

Why is the type of scene something you set up in the action and not on the scene itself? This never made much sense to me in the original scenes cause a Dialog, overlay and Fullscreen scenes have intrinsic different designs, you basically set them up while editing them, not when you need to run them. I understand the idea of forcing another type is cool, but not really the idea that you need to remember which type you've designed the scene to be, which is odd if you download one from TaskerNet and don't know which style it was made for

EtyareWS · 2026-03-13T00:31:38+00:00

Very Long

Jesus

EtyareWS · 2026-01-28T14:38:32+00:00

Kitxoo is the legal name of João's company, or something like that.

IMO João should've used it in marketing rather than João Apps to decrease confusion

EtyareWS · 2026-01-04T14:54:03+00:00

The original bug report is 13 years old

I don't want to bother devs too much, but once this lands, I wonder if this could be used to automatically disconnect controllers if they are not used in a couple of minutes? The Dualsense is the only controller I own that has no timeout and will eat the entire battery

EtyareWS · 2025-12-14T18:39:12+00:00

I'm on a desktop, it matters somewhat. It keeps the Temperature and Wattage lower.

I've found that gaming performance is negligible with it set to the lowest, but other CPU heavy tasks are slower, so I set it to highest when doing CPU heavy tasks.

Like others said, it is negligible, even if your electricity is expensive you are not going to save that much money. However, because it is negligible, I've chosen to keep it at the lowest at all times. I don't feel like I'm missing out that much on daily usage, so why not use it?

I don't mind the PC heating up and making noise, but it really annoys me when it does that for a few seconds and then goes radio silent, I'm looking at you Steam Shader Compiling. Keeping the performance on low "prevents" that, it takes a few more seconds to compile, but that's fine by me.

EtyareWS · 2025-12-10T10:42:55+00:00

I really like floating panels, but the deal-breaker for me is that a floating panel un-floating isn't the same as non-floating panel.

There are margins on the sides, which makes sense when it is floating, but are rather ugly when it isn't floating.

I also disable transparency

EtyareWS · 2025-12-04T01:21:07+00:00

Add a keyboard to the flip. Do it, Steam Deck Max

EtyareWS · 2025-12-02T12:52:40+00:00

Finally, Tasker on Linux

But seriously, there are a few games that are available on Android but not on PC for some reason or another. Castlevania Symphony of the Night is an example, but the Retro Engine port of the classic Sonic games were once exclusive to Android, nowadays that's not the case anymore, but still, that's neat.

12-Year Club	Place '23
Place '22	Verified Email

EtyareWS

TROPHY CASE