-
Notifications
You must be signed in to change notification settings - Fork 527
UI - Another approach to selecting which apps/restrictions get an ondemand prompt #1247
Comments
I think this is more confusing, especially for new users, so I am not a fan of the proposal. |
damn, ok, maybe ill grow into the current implementation, although its a shame really, ......i dont suppose adding a "Ask" and "Restrict" title as headers would intice you to change your mind :) |
"i cant speak for jpeg, but for me, personally, it would help to less confuse things, if the original column would stay the way its always been used for restrictions, and any question marks (selectable) on any given restriction on the NEW column would basically mean "prompt this restriction if its called", simple, and you'd have a nice gui indication in xprivacy letting you know what is or isnt being prompted.....at the moment, at least for me, merging prompt selection with the original restriction column is a little confusing, .......well, not so much confusing, but it doesnt feel like the best approach to me, but maybe this is one of those things that is easy to say but not easy to code, maybe its one of those things you gotta get used too edit |
I can see what you mean, but I can also see myself using XPrivacy in ondemand mode permanently. In which case if I am going to be prompted for a function, I don't care whether it is stored as restricted or not. So, having just one checkbox and filling it with a "?" for undetermined categories/functions would be a nice friendly simple option. |
i "THINK", this implementation could accomadate both styles no, if there is an option to select ALL for the "?" column, then this way, both styles could be accomadated, i still wanna be able to go into xprivacy and restrict the catogories that are hardly used for new apps, and use the prompt for specific restrictions, like the examples above...............im so used to the original column that it feels weird not having a tick/box/blank in them, i get an irational thought that its not protected, thats why, the new column, to seperate the ondemand feature from the original restriction feature, and perhaps make clear "?" supercedes the original column, if its enabled somehow, i guess im set in my ways when it comes to xprivacy......it's what, 4, 5....6 months old?.....yep, set in my ways :) lll try not to bother you guys so much with this, gonna be difficult :), but ill try, and ill give the current implementation a better chance |
if "?" supercedes the original column, why not just put a "?" in the original column? That would be my suggestion. |
yeah, im trying to imagine it, and i guess your right, one question though, how will you implement the third option "?", do you simply touch the box a third time, so, restrict, or if the box is unrestricted first, then or wont we be able to manually turn on a prompt for anygiven restriction |
Something like that. |
ok thanks |
If this is possible, i think, for the user at least, this would be more intuative
The text was updated successfully, but these errors were encountered: