Trying out the first beta of TC2010 (congratulations, btw )
Stopwatch can now can be controlled form the command line:Woohoo! Mmm, command line options...Sorry, I'll try to contain myself.
/exit : Exit T-Clock 2010
/stop : Stop (pause really) the Stopwatch Counter
/lap : Record a (the current) Lap Time
/reset : Reset Stopwatch to 0 (stop as/if needed)
The quoted 1 + 3 items appear to work as expected here.
/prop : Open T-Clock 2010 PropertiesThese made a corresponding dialog of T-Clock active -- which seems to make sense for /prop, but I'm not sure it does for /start. Do you get the same behavior?
/start : Start the Stopwatch Counter (open as/if needed)
The /prop & /exit switches have always been in T-Clock, they're part of Kazubon's origional code. /stop, /lap, & /reset are all rather predictable as they assume (require) the stopwatch be running to effect their changes. /start however has a dual purpose (requirement) which will both start the counter and launch the stopwatch dialog window if it isn't already open. If the stopwatch window was already open, it would only start the counter in the pre-existing window.
Timers Can now be viewed/monitored:Took me a bit to figure out how to make that window appear
I had a single timer visible in the Timer Watch dialog, stopped it from the Add/Edit dialog (so this is neither expiring nor plain removal from the dialog), and noticed that the Timer Watch dialog went away. Is that what happens there? Not sure what I think of that yet.
I guess it would seem a bit quirky at first glance - But the logic behind it is that if there is only one timer(/purpose for the window) running, and that timer is canceled, why make the user close two windows just to get rid of it. Hence the window's self terminating if un-needed behavior.
...And yes, I do need to flush out the help file a bit in that department.
Highlight a timer in ListView & hit Delete - To get Exit Options.This seemed to work for all three cases.
I started to wonder whether it might be useful to be able to start expired or stopped timers from the Timer Watch dialog -- and/or perhaps have some way to get the Add/Edit Timer dialog to appear via a hotkey or button press. Still at the wondering stage though.
I've pondered that one myself, unfortunately getting the timers to restart from the watch window would require recoding the whole shebang from scratch as launching the timers is dependent on accessing a CBGetItemData structure which is only available when the add/edit window is open.
I haven't started exploring the hotkey option yet, but that will be dependent on how reliably I can make it without hooking even deeper into the shell.
Note: Timer Watch will automatically close if last timer is removed, or if a Single watched timer Expires.I observed these two results too. I'm not sure what I think of the latter yet.
Granted I'm assuming ...
If the last watched timer is removed, the next logical step would be to close the now un-needed window (which is why it's automated).
If a single timer expires, the alarm is more of an attention getter that a string of zeros (or the expired flag) so auto-closing the window while the clock is flashing & beeping saves an extra click.
The first (tricky) part was just get the thing to work ...
... *Shrug* the design behavior after that is up for debate. So let me know if it starts to grow on ya, or just itchs real bad.