View Single Post
Posts: 1,313 | Thanked: 2,978 times | Joined on Jun 2011 @ Finland
#589
Originally Posted by chemist View Post
Some suggestions:
move the whole to settings, it is a daemon and its behaviour should be under "Settings -> Applications" me thinks
I kind of agree. I haven't looked at it, but if I've understood correctly integrating into Settings would require some fancy XML or MTF. Basically meaning a rewrite of the current QML UI. That's not realistic to happen. But perhaps I'm wrong about that.

add a slider to deactivate all and add a slider to deactivate each
The deactivate all is in the menu. I thought about putting it as a slider but had a bit of a dilemma where to put the slider so that it would look good. In the end I came to the conclusion that activating/deactivating all the rules is something you do quite rarely, so to keep the UI simple and non-obtrusive such functions should be "out of the way" in the menu. I'm open to different opinions on that of course.

Deactivate rules one-by-one will be in 1.7.0, it is implemented already. But no slider for similar reasoning as above, it will be accessible with long press on rule (and in the rule's menu).

add "if idle in this case for #min do $changes" additionally to cases
This one I don't understand. How does it differ from the current Idle condition?

copy a case (it is really hard to record cell-towers during meetings and such... like 5 cases for work, each time I add a new one I have to wander around to get the towerinfo)
You can copy a case with long press on a rule (Copy as new).

I have cases timed once a week but I do not have the device for a week yet so no idea if it's buggy or not...
Let me know if you hit the bug. It's only meaningful to try the test version if it's certain the current version has the time bug for you.

Thanks for the feedback!
__________________
My N9/N950 projects:
 

The Following 2 Users Say Thank You to ajalkane For This Useful Post: