I think that this is a great app, but in my oppinion it drains a little battery since it can force the events to events screen.. Is there any possibility of running the daemon only when you open schedule app? or even when you add a new entry..
I think that this is a great app, but in my oppinion it drains a little battery since it can force the events to events screen..
The event update mechanism is push based (the application does not consume any resources unless the calendar changes or an event expires and other minor housekeeping tasks such as updating the labels at midnight).
Is there any possibility of running the daemon only when you open schedule app? or even when you add a new entry..
No as that would lead to an inconsistent view on the home screen (if you don't start the scheduler on one day old events won't be removed or the label won't be changed from tomorrow to today). Reacting to entry changes requires a daemon all the time (the platform calendar library uses a file watch for that).
I think that this is a great app, but in my oppinion it drains a little battery since it can force the events to events screen.. Is there any possibility of running the daemon only when you open schedule app? or even when you add a new entry..
My idle consumption is 3 mA with this app or without, so the drain is limited.
I am really busy right now so I won't have time for it at the moment. I'll try and release a beta with the other already implemented functionality (undone to-dos, single event feed display mode and some other changes) within the coming weeks though.
I just cloned the git source and did a quick search for a 'qtn_caln_personal_caln' translation, and I'm wondering if it needs to be added for the device/personal calendar...
I just cloned the git source and did a quick search for a 'qtn_caln_personal_caln' translation, and I'm wondering if it needs to be added for the device/personal calendar...
Hmm, it seems like it didn't find the translation when it created the default calendar. I am not translating the calendar names at all (I assumed they were stored localised) but can add a call to trId in the next version for names which start with qtn_.