Thread: [Announce] ProfileMatic for Harmattan
View Single Post
slarti is offline slarti
2013-02-22 , 07:39
Posts: 277 | Thanked: 319 times | Joined on Jan 2010
#1140
Originally Posted by ajalkane View Post
I've updated the beta version. I'm trying now to set another option, that should result in the "not pressing snooze" resulting in same snooze value as pressing snooze. I haven't had time to test this at all myself.
This works.



Originally Posted by ajalkane View Post
It's not that hard to change the behaviour, but here is two problems:

- Even the minute precision is not EXACTLY on that minute. Instead in an effort to preserve battery I am using (heartbeat-based) timer, so that the wakeups try to occur on other wakeups of the device. In practice this means that the real timeout can be as much as 30 seconds later than that was set in condition. In light of that, setting precision by second doesn't make much sense.
This explains why it has sometimes seemed like the rule actions failed to execute. I just didn't wait long enough.

You're right, not much sense in the extra precision.

Originally Posted by ajalkane View Post
- The other problem is that changing the current behavior could have unexpected side-effects. So I wouldn't want to change it without a good reason.
Like I said, if tricky at all...

Originally Posted by ajalkane View Post
As a workaround, I think the interval time condition could be implemented by doing some ingenious scripting like slarti has done here http://talk.maemo.org/showpost.php?p...postcount=1028
I thought I'd highlight the important part of that sentence :

Seriously, though, I was thinking about a script that would take seconds as an argument and would set an alarm with that using some ProfileMatic magic. This would make it possible to make 'shortcuts' on the desktop to some timers.

That same logic could be used to make a script that would just update a rule to execute 15 minutes later from now. Then put that script as a custom action in the same rule it's updating thus creating a loop that repeats every 15 minutes. Of course, the script could do other things when executed or could be placed in another script.

I've read that you can install cron on the N9, too, although there are some permission problems. That might be an alternative way to go.

The stupid thing about all this is that the timed daemon was supposed to be a cron replacement but it wasn't documented at all and seems almost impossible to use from the command line. There is an add_events dbus method for it but no one seems to know how to use it.
 

The Following User Says Thank You to slarti For This Useful Post: