foo_scheduler, Plugin for scheduling actions like play, stop, system shutdown/wake up Options

[andrew_smolko]

Version 4.11 (download)

Changelog:

• 4.11
  
  • "Scheduler enabled" checkbox has been added.
• 4.10
  
  • Removed useless stop reason in player stop event.
  • Dropped packing of executable to be able to analyze crash dumps.
  • Rebuild with more stable versions of internal libraries.
• 4.09
  
  • Completely fixed keyboard shortcuts assignment problem.
• 4.08
  
  • Fixed tab order in "Wait until N tracks played" configuration dialog.
  • Fixed a bug with menu items, when keyboard shortcuts couldn't be assigned to them correctly. Please recreate your menu item events!
• 4.07
  
  • Added a new command "Stop all action lists" to the status window and to the main menu.
  • Header restyling to conform the style of preferences page.
  • New action "Wait until N tracks played".
• 4.06
  
  • Next/previous track actions added.
• 4.05
  
  • Preferences window fix due to changes in fb2k 1.1.
• 4.04
  
  • Added items reordering in events list.
  • The width of each column in events list window is stored in configuration.
• 4.03
  
  • Bug fix release.
• 4.02
  
  • Added more detailed config of "On playback stop" event.
  • Remaining time of "Delay" and "Set volume" actions is now displayed in status window.
• 4.01
  
  • Added keyboard context menu invocation in events list view and action lists view.
  • Volume fade out bug fix.
  • Volume fade in/out now uses logarithmic scale.
  • Final action combo-box has been returned in date/time event.
  • New "Mute/unmute" action.
• 4.0
  The plugin is rewritten from scratch. Short list of changes:
  
  • New "OK, Cancel, Apply" preferences page style, introduced in fb2k 1.0.
  • "Reset page" button works correct now.
  • Scheduler isn't stopped while its preferences page is opened. It's running all the time.
  • Added new status window, where you can see pending date/time events and manage running action lists.
  • Fixed crash with concurrently running action lists.
  • Fixed incorrect handling of date/time events in some cases.
  • Date/time events: completely new configuration dialog, added title support, "remove/disable event" option removed.
  • No more annoying message boxes, now only balloons are used.
  • Menus, treeviews and listviews use native Windows Vista/7 style.
  • New player events: on playback start, stop, pause, unpause, track change.
  • New actions: Pause/Unpause, Change playlist, Launch application.
  • For "Delay" and "Set volume" actions duration units can be selected.
  • New File/Scheduler menu.
  • No more configuration reset during version upgrade.

This post has been edited by andrew_smolko: Dec 24 2012, 14:39

[NeXT]

Wow, I waited this so long! =) Thanks! Trying to migrate from foo_scheduler for 0.8..

Will there be any significant interface modifications? Most of all I miss quick access to events via Components -> Scheduler and current inability to use once-defined action to multiple events (and lack of choosing exact track of playlist to play )..

And, there' s the first founded bug :

[andrew_smolko]

And, there' s the first founded bug :

Windows version please and language settings. Something is wrong with GetTimeFormat...

And now about the timer: IT'S ALREADY IMPLEMENTED!!! See "Delay" action. It pauses action list for a certain amount of time.

[gren]

And now about the timer: IT'S ALREADY IMPLEMENTED!!! See "Delay" action. It pauses action list for a certain amount of time.

But... that's only under a player event or a date/time event. What I think is useful is delay from right now. Did what I was saying make sense? Having a timer of 60 minutes with events under it and whenever you checked the box it would start the timer going? While I see that it's possible to do timer actions now... you first have to create a date/time that goes off right away to enact the delay which will lead to whatever other actions you schedule. It assumes that a timer must be started at a certain time event instead of starting a timer 'now'.

Here is what I envisioned:



The event waits there until you want to click on it... and when you do the timer for those actions starts. Maybe this is laziness... but using your delay you create a date/time event for one minute from now with those actions and then delay X minutes and each time you want to use this you have to change the time to being a minute from now to get the delay timer started.

[andrew_smolko]

Here is what I envisioned:



The event waits there until you want to click on it... and when you do the timer for those actions starts.

It will be impossible to start timer after click. While you edit options scheduler is stopped. It starts when the preferences window of scheduler is closed.

As for the idea... I'll think about it.