Hide root when unavailable

Post your feature requets for new triggers, conditions, actions and other improvements.

Moderator: Martin

Locked
mathieson
Posts: 51
Joined: 13 Aug 2013 18:16

Hide root when unavailable

Post by mathieson » 26 Oct 2014 05:09

Hello,

I have a suggestion with regards to root. Could you please hide actions/triggers that require root when root is disabled in the preferences?

That way when searching for actions/triggers Automagic will only show the ones that are available.

Thanks!

User avatar
Martin
Posts: 4468
Joined: 09 Nov 2012 14:23

Re: Hide root when unavailable

Post by Martin » 26 Oct 2014 11:26

Hi,

I don't like to hide features since it usually leads to more support requests when stuff is available on one device but not on another. There are also some actions that only require root when some options in the action are set.
I could show trigggers/actions with a strike-through text in the list when an action is known to be unavailable for some reason (root required, wrong Android version, wrong ROM etc.). I add this to the todo-list.

Regards,
Martin

User avatar
MURTUMA
Posts: 697
Joined: 05 Mar 2013 22:43

Re: Hide root when unavailable

Post by MURTUMA » 26 Oct 2014 19:27

I had similar request some time ago for actions that aren't supported by OS but itwas ignored. Currently I'm stuck on GB and there are a lot of things not supported by it. Would be great if you could expand the idea this too.

User avatar
Bushmills
Posts: 286
Joined: 23 Sep 2014 21:56

Re: Hide root when unavailable

Post by Bushmills » 26 Oct 2014 20:09

Maybe allowing user to pick triggers, conditions and actions from "palettes" of items, added (or removed) and organised (put into sequence) by user, could be a more general solution than merely hiding a fixed set of specific functions. By default, one of those palettes could contain the same items as the list of all available items, thereby not changing user interface in any way for those not inclined to customise that list.

User avatar
Martin
Posts: 4468
Joined: 09 Nov 2012 14:23

Re: Hide root when unavailable

Post by Martin » 27 Oct 2014 17:25

A categorization of triggers/conditions/actions is something that's on my todo-list, unfortunately I still did not have the time to look into this yet.
Regardless of categorization, showing the items with a strike through text and maybe a filter check box like 'Hide Unavailable' would work. I just don't like the idea to completely hide some items on certain devices since this will almost certainly lead to questions when all the nice actions are missing on one device but show up on another.

User avatar
Bushmills
Posts: 286
Joined: 23 Sep 2014 21:56

Re: Hide root when unavailable

Post by Bushmills » 27 Oct 2014 18:34

But what is "unavailable" - same as one could root a device to make those unavailable root-requiring functions available, one could create a dropbox account to enable those dropbox related functions - of course those will have to be "unavailable" too as long the account hasn't been created ...

User avatar
Martin
Posts: 4468
Joined: 09 Nov 2012 14:23

Re: Hide root when unavailable

Post by Martin » 27 Oct 2014 19:41

That's true, especially for actions that require root. Items that are not available because of some more static reason like an old Android version seems to be quite unproblematic to me.

User avatar
MURTUMA
Posts: 697
Joined: 05 Mar 2013 22:43

Re: Hide root when unavailable

Post by MURTUMA » 27 Oct 2014 21:18

An interesting choise of a word, Martin; "unproblematic". Just to be sure that the meaning of it doesn't get lost in translation, do you mean that you have no problem in implementing that in future? :)

The check box filter sounds good, because I think the base for this request was to make element lists less cluttered.

User avatar
Martin
Posts: 4468
Joined: 09 Nov 2012 14:23

Re: Hide root when unavailable

Post by Martin » 29 Oct 2014 17:07

With "unproblematic" I mean that it looks technically feasible to me so I've added it to the todo-list. I don't promise anything yet since it looks like it might take a few weeks to fix everything that's currently not working properly on Android 5 :(

Locked