It seem almost poetic lyrical - Is there a tune that goes with it?

Good question

Up Coming Stuff: I'm currently working on the (much needed) "live" timer countdown interface. The plan is to have a single location where a selectable group of active timers can be monitored.

Sounds nice!  Would a hotkey to toggle visibility make sense?

Also working on making the stopwatch controllable from the command prompt, so a script can start/stop/lap/reset the counter for execution time checking.

Mmmmm, command line access.  More of that!

Beyond that ... I'm running out of ideas

How easy/likely is a non-registry-using (=> portable-friendly) version?

Okay, first beta of TC2010 now available.

Stopwatch can now can be controlled form the command line:

  /exit : Exit T-Clock 2010
  /prop : Open T-Clock 2010 Properties
  /start : Start the Stopwatch Counter (open as/if needed)
  /stop : Stop (pause really) the Stopwatch Counter
  /lap : Record a (the current) Lap Time
  /reset : Reset Stopwatch to 0 (stop as/if needed)


Timers Can now be viewed/monitored:


Highlight a timer in ListView & hit Delete - To get Exit Options.

Note: Timer Watch will automatically close if last timer is removed, or if a Single watched timer Expires.

Feedback Appreciated.

Trying out the first beta of TC2010 (congratulations, btw  )

Quote from: Stoic Joker on March 27, 2010, 06:16 PM

Stopwatch can now can be controlled form the command line:

  /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)

Woohoo!  Mmm, command line options...Sorry, I'll try to contain myself.

The quoted 1 + 3 items appear to work as expected here.

Quote

  /prop : Open T-Clock 2010 Properties
  /start : Start the Stopwatch Counter (open as/if needed)

These 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?

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.

Quote

Timers Can now be viewed/monitored:

Took me a bit to figure out how to make that window appear  

Some observations:

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.

Quote

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.

Quote

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.

[/quote]

Granted I'm assuming ... But...
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.

Thank You,

Stoic Joker

For you Astronomy buffs, I've added the Julian Date as a custom formatting option (JD)

If you are wondering what the Julian Date is...

Today is: 2455283.5

Download in usual place

Quote from: Stoic Joker on March 28, 2010, 06:08 PM

Okay, as it turns out Hotkeys are a hell of a lot easier that I'd originally thought. So...

T-Clock Hotkeys
Ctrl + Shift + S : Opens the T-Clock Stopwatch.
Ctrl + Shift + T : Opens T-Clock Add/Edit Timers.
Ctrl + Shift + W : Opens the T-Clock Timer Watch Window.
Note: Timer Watch will auto-close if it isn’t needed (has no timers being watched).

Thanks for adding these.  They seem to work here.

Ctrl+Shift+T happens to be something I use often for Firefox (opening the most recently closed tab).

Shit, I was afraid that would happen.

Given the possibility of conflicting shortcut keys, I wonder if configurability of the specific keys would be helpful.  If that's a pain or too much work or whatever, perhaps you can punt on the shortcut keys for the moment (sorry, I know I asked for them initially).

It seemed reasonable enough at the time (and I like Hotkeys). I figure there are three options:
1. Add the Alt key to the Ctrl + Shift + X combo (and hope that's not used too)
2. Switch to Ctrl + Fx (and hope nobody else thought of that option)
3. Make the keys configurable - which means adding a tab to the properties dialog, in which case I'll have to reorganize all the existing pages (again).

A random thought: if command line options for the functionality of opening (and closing or toggling) the various windows were available, it'd be possible to set up something else (e.g AHK or FARR) to handle the specification and triggering of hotkeys.  What do you think?

If it's gotta be written in something, I might as well write it into the existing app. ...Guess I'll just half to get blind drunk and a dart board to figure this one out.

So I sent a hoot out to the void in June of 2008, not really expecting any return, but sometimes you try, you know, just in case. - So imagine my pleasant surprise to find a message in my inbox from that most stoic of jokers. 

Not only that, but he had done the thing I asked for(!) How totally awesome!


Now, just one little thing....
I asked for Julian date, but it turns out that what is often referred to as 'Julian date' is, um, really Ordinal date   In other words, what I was really looking for is 'Day of the year' 1-135, 366 on leap years. Please? Pretty Please?

I actually quite glad you brought this up. I had to research Julian Date to find out what it was, before having a go at it. But As I recall your Email did mention that you were looking for a YYYY.DDD format ... Which doesn't quite match the JD standard that I found and used. Now I understand why (thank you).

So at this point I'd really only need to add a Day-Of-Year option and then the Ordinal date format you're after would be easily configurable. I can do that - I was actually already on-the-fence about adding the DOY, so I'll just toss it into the next build.

Also, one of the neat features in TClockEx was having 'launch other application' in the Mouse config menus.

Um... TClockEx was Dale Nurden's project ... I'm the other guy...

Gotta say, us power users tend to have a couple applications tied to hotkeys, so you really have to allow users to re-assign or disable them.

Yes, I've slowly been resigning myself to that. The last build was just a test to see if I could do it (add hotkeys) ... Next trip through we get to find out if I can do it correctly...

been using TClock, TClockEX, etc. for about the last 10 years, and it is really nice to see this work and refreshing. THANK YOU! 

I'm glad to see folks still enjoying T-Clock - and Thank You, I truly do appreciate the feedback.

Guess I'll just half to get blind drunk and a dart board to figure this one out.

And yet, I'm sure you'll hit the bulls-eye!

A few Donation Credits coming your way for the indefatigable effort and constant improvement!

I hope not - That'll make the bull real mad ... Then What'll I Do...

Try for the udder one?

Awesome. Thanks for this, Stoic Joker.

Would love to see a portable edition too.

Dunno if there's much you can do about the time sync issue - unless you're willing to run a background service with admin privileges that t-clock can communicate with

Dunno if there's much you can do about the time sync issue - unless you're willing to run a background service with admin privileges that t-clock can communicate with

Compounded by the fact that there is already an existing time service that I don't want to run afoul of (domain membership). While I could (for simplicity sake and to allow portability) leverage the existing Windows Time Service, it quickly turns into a kludge because of the (workgroup membership) defaults which only update every 7 days, and then there's the issue that most folks tend to use the default time.microsoft.com which fails frequently for a multitude of reasons.

We are on the same page here (privileges wise), I was just hoping you could think of something I was missing.

who cares if a uac prompt comes up?

I do. ...One of the core premises for the project is that it be (draconian) Corporate Network user friendly ... So administrators need not worry if it was set-off within their realm.

if time sync is a manual action triggered from system tray i dont mind if i have to ok a UAC prompt.  i just want to have easy access to the command.

Understood. point taken, but "we" still have to contend with the proclivities of the rest of the great unwashed masses... that also might be inclined to set this thing off, and spasticly panic of an ominous looking security message is triggered.

Remember I'm working in pure C here, it's all-or-none - I don't have the luxury of the C# style runtime code level permissions checking/validation/prompting. Best I can do is what I hinted at earlier, which is to configure Quicky Menu option to point at a script that fires the Windows Time Service re-sync. That way the script handles/contends with the permissions prompting.

My typical uptimes are measured in months. I know the clock in Windows likes to drift a bit, because it completely ignores the hardware clock (after boot) and keeps its own time going forward during the session (it's a HAL thing). Unfortunately, the only current (reduced permissions) security model safe option is to let Windows handle the time.

The only reason I haven't completely closed the book on this is that I'm a bit of a (die-hard) nonconformist and love bending the rules in an attempt to invent have-your-cake-and-eat-it-too solutions. This one however has me stumped.

Thanks for the update.

I briefly tried the HotKeys feature in beta -5-.



To reproduce, please try:

1. Bring up HotKeys tab in Properties dialog (what, no hotkey for this?  kidding)
2. Click Reset button for "Display Timer Watch Hotkey"
3. Enter hotkey: Control+Shift+S
4. Click Apply buton
5. Press: Control+Shift+S (notice window pop up)
6. Click Reset button for "Display Timer Watch Hotkey"
7. Try to enter hotkey: Control+Shift+S (notice that only the text Control+Shift shows up and a timer watch window pops up)
8. Click on Properties dialog
9. Try to enter hotkey: Control+Shift+S (notice that the text field gets additional content)