Reply to thread

Message

<blockquote data-quote="michael_t" data-source="post: 852091" data-attributes="member: 85139">I already thought of this, but there are some reasons that prevent it: If I would release it as a &quot;regular&quot; plugin, PowerScheduler++ would run in parallel to the original PowerScheduler, which would lead to unpredictable standby / wakeup behaviour. Moreover I do not know how to implement this, because the PowerScheduler(++) plugin class implements some public interfaces (e.g. IPowerScheduler, IPowerSettings) that are used by the MP core / TV service and by other plugins and that should (can?) exist only once. I could imagine that there is a way to solve this problem, but I do not know it and therefore will stick to the &quot;replacement&quot; approach.This would mean to provide a complete MP installation package that comes with PS++ instead of PS. Since you benefit from this only when a new MP version is released (which happens not too often) and there is no advantage when a PS++ update is issued, I will stick to the plugin distribution for the time being. But maybe I will provide a full MP / PS++ installation package when MP 1.3 (final) is out...&nbsp;Michael</blockquote>

[QUOTE="michael_t, post: 852091, member: 85139"] I already thought of this, but there are some reasons that prevent it: If I would release it as a "regular" plugin, PowerScheduler++ would run in parallel to the original PowerScheduler, which would lead to unpredictable standby / wakeup behaviour. Moreover I do not know how to implement this, because the PowerScheduler(++) plugin class implements some public interfaces (e.g. IPowerScheduler, IPowerSettings) that are used by the MP core / TV service and by other plugins and that should (can?) exist only once. I could imagine that there is a way to solve this problem, but I do not know it and therefore will stick to the "replacement" approach.This would mean to provide a complete MP installation package that comes with PS++ instead of PS. Since you benefit from this only when a new MP version is released (which happens not too often) and there is no advantage when a PS++ update is issued, I will stick to the plugin distribution for the time being. But maybe I will provide a full MP / PS++ installation package when MP 1.3 (final) is out... Michael [/QUOTE]

Verification