Switch any settings in Quick settings via API

elmuSSo shared this idea 31 days ago
Declined

Hi.

I would like to control different switches in Quick settings from eg. Tasker or my own plugin, but for now there is limited list of settings I can change.

So my idea is simple. Enable switching any settings in Quick settings via API.

Comments (1)

photo
1

Hello elmuSSo,

I'm surprised to read that "there is a limited list of settings I can change" > there are settings you may change over API?

It is a question if something like this should be allowed at all. The app currently does not provide any system for something like "add-ons permissions", so it is not possible to prevent any add-on from certain actions (like an un-wanted change of settings). And changing settings on the background over add-on sounds to me like a feature that not all users want to allow ...

So all together, because of the increased push on users-privacy and complexity of this feature for end-users, I just think that it does not worth extra work. Sorry.

Menion

photo
1

Would a solution be to add extra settings to presets

which could be then called from tasker

therefore they have to be enabled in advance

photo
1

Alistair Parsons, Agree, that would do the job

photo
1

Menion: "there are settings you may change over API?" - I was in particular thinking about Toggle centering from New "Action tasks" API, which can be accessed from API, but it is actually not in the Quick settings. But for me it can be seen as a setting

photo
1

Menion: I wanted to find workaround to change Quick Settings. I looked into AutoInput plugin for Tasker, to press those buttons in QS with use of accessibility service.


But i'm getting: "Field cannot be clicked" and their FAQ says:

Why can’t AutoInput click on my favorite app? What can I do?

Unfortunately not all apps work with AutoInput. AutoInput uses an accessibility service to click on stuff and sometimes apps are coded in such a way that the accessibility click is disabled.

What you should do is try to contact the app’s developer and ask them to make the button you want to click compatible with an accessibility service. It’s not a hard thing to do, so there’s a good chance they’ll do it


Any chances to at least implement this, please? To be able to virtually click on those switches in Quick Settings. But then, also buttons in the right panel should be clickable by their id (like tib_centre and tib_rotate currently are) to show Quick Settings screen

photo
1

I'm checking the documentation of how to make custom views "accessible" and for me, it does not look like an "easy task".

Because I know nothing about this system and because it really looks to me like a very specific use-case (and also because Locus Map isn't optimized for this accessibility usage), I'm sorry.

Menion

photo
1

@elmuSSo

Just to be clear

1.Do you want to use the API/Tasker to call any/all of the quick settings toggles

2.Or do you want more quick settings that can call features that are in API only


you mentioned centering which is API only

so while this at the moment cant be added to quick settings, as its API it can be added using tasker to quick bookmarks ( i mentioned this here https://help.locusmap.eu/topic/22994-tasker-and-quickbookmarks)

What would be REALLY good is if Locus could add standard android shortcuts to the side panel and/or the quick settings panel.

EVEN BETTER again, is if the toggles in quick settings were stand alone, and could be added to any side panel. If you could make custom panels that pop up, a bit like android folders.

That way you could have a custom folder that had several quick settings toggles, some shortcuts to navigation related web pages, shortcuts to tasker tasks, google maps navigations etc.

photo
1

So my main and only intent is to make Locus more hands-free. I'm using Locus as my car's main navigation computer. And when driving I really can't click on small buttons in right panel to open a window and then click on bigger button in Quick Settings to activate/deactivate certain functionality (it creates a dangerous situation on the road due to me focusing on the screen, instead of the road).


So I'm trying to write a suite where I will be able to change QS settings by my voice. But to do that, I need to somehow make Tasker to click or call changes of those settings.


So adding QS to api is impossible as Menion said, so the only hope for me is to "remotely" call clicks on certain icons to activate/deactivate them.

Menion I verified that buttons tib_centre and tib_rotate are compatible with AutoInput. Isn't this just a matter of buttons having IDs, and adding IDs to other buttons will make it works?


I can promise that I will write a tutorial and publish my scripts on how to use Tasker to click on those buttons if they will be clickable. Please reconsider it once again.

photo
1

Hmm ... this use-case sounds to me like ideal adept for system of "Presets". This already may be controled over API and presets already contains quite a lot of core settings. Isn't this a solution?

photo
1

To voice control the settings, tasker would need to be used anyway

So the easiest and most benefit to lots of users would be to make sure that all the quick settings toggle items are also available in presets.

It looks like some are available only in API, some in presets and some in quick settings.

I would like to request in presets

choose specific map

choose specific map item to show

photo