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

[q-stankovic]

Not a good idea, I prefer to stop fade in using some of this buttons. Better solution is proposed by gren

Now i think so too.

Why 2 meanings? One meaning: EVENT will be handled by scheduler (checked state) or not (unchecked state)! Using a menu item is an EVENT. If you don't want scheduler to handle menu item event, why this menu item must be displayed in submenu?

It is hard for me to explain it in english, so let me try again by giving an example. Let's say it is 00:00 and you want to start playback at 01:00 - you can create a date/timer event which starts playback at 01:00 or a menu item event which starts playback in 60 minutes. I expected that checking the box would lead to the same result: Playback starts in one hour. But in case of a menu item event you have additionally to go to main menu. I hope you can understand now what the reason of my confusion was. (The screenshot from gren in post18 on page1 shows what i had expected - he called that "timer event". )

Impossible. Due to internal architecture of the plugin.

I think you misunderstood my point b) because of my simple english. I just repeated what i described above. I didn't mean that checking one box should start all events (did you understand that?)

I hope i expressed mysel a little bit clearer

Edit: i read your answer to grens suggestion and now i understand. Just a stupid idea: Why not make a checkbox for menu items in a different style?

This post has been edited by q-stankovic: Nov 10 2006, 17:33