A
Anonymous
Guest
Hi Devo,
I think that the wake-up-thing should be coded only once and made public to all plugins.
I've not talked to frodo yet but I'm thinking in terms of something like this.
If the current plugin interface was extended by a few more methods/events like
getNextEvent() return DateTime
allowShutdown() return bool
wakeupevent() - triggered when time is up
and the whole collections of plugings from MP core where made accessible to PowerScheduler then it could easily scan every active plugin for a time to wake'em up or check if any of them would prevent MP from going into sleep.
When I get some time I will do some testing to se if it could work.
/ Fred
I think that the wake-up-thing should be coded only once and made public to all plugins.
I've not talked to frodo yet but I'm thinking in terms of something like this.
If the current plugin interface was extended by a few more methods/events like
getNextEvent() return DateTime
allowShutdown() return bool
wakeupevent() - triggered when time is up
and the whole collections of plugings from MP core where made accessible to PowerScheduler then it could easily scan every active plugin for a time to wake'em up or check if any of them would prevent MP from going into sleep.
When I get some time I will do some testing to se if it could work.
/ Fred