Login with username and password (forgot your password?)

[i dont mind]

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.

[f0dder if Ya happen to wander by...]

Glad to see the new features being well received ... as there's always a fine line between being feature rich and junked up (that I don't want to cross).

I had to take a short break due to getting completely fried bouncing between TC and the office projects. That and the configurable hotkey functionality is proving to be as difficult as I thought it would be (to do properly). Also my wife had surgery yesterday (which went well).

There are a couple of things I'm planning, but here are some of the highlights:
 1. I have concocted a rough plan on how to attack the hotkey project which I'll be exploring this afternoon.
 2. There are plans for an .ini based portable version, but they haven't completely gelled yet.
 3. I'm still getting hammered on the Time Sync front - which has me torn on what to do - All research attempts have led back to a (UAC prompt filled) dead end. So f0dder if Ya happen to wander by... I'm open for ideas.

The key to a good April Fools gag, is that it has to be at least marginally believe-able on some level. So unless there was a substantiating back story regarding Mouser becoming demoniacally possessed ... This is a rather obvious ruse.

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?

Luckily (for both of us) the code is strikingly similar - So I got all of the above it one shot. How ever while Julian Date was crystal clear regarding the "Thow Shalt Not Uses Any Other But UTC" part, the Ordinal Date (after an hour on Google) wouldn't break one way or the other. ... So I did both:
 1. OD = Ordinal Date (YYYY-DDD) Using UTC Time (shown in screen shot below).
 2. Od = Ordinal Date (YYYY-DDD) Using Local Time.
 3. DOY = Day-Of-Year in Decimal (001 - 366) format.

Yes, I was playing with the font size before taking the SS - The fonts do seem to scale nicely...

[attach=1]

Well, much as I hate to regard silence as acceptance ... I gotta go with it.

Sorry for not responding about the week feature request. Totally missed that post as you said, it'll take some time. Thank you for implementing this feature. I think it's perfect the way it is (ISO Sunday, ISO Monday, Simple). 

Thank you, I'm truly relieved to know that the function passed muster. ...And Thank You also for the encouragement.

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!

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

Thank You.

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.

[a digital photo frame]

The new Xtreme N Storage Router (DIR-685) makes networking easier by combining the superior features of a wireless N router, a built-in Network Attached Storage (NAS) and a digital photo frame

Oh goody, a Feng Shui router... *Sigh* ...Sounds like the kind of toy that you'll end up hating (mind you I am a minimalist). I'd much rather things stick to what they're supposed to do - All things, to all people constructs tend to end badly.

NetGear, on the other hand, while not top-shelf, has proven to be quite reliable. I generally go for LinkSys first - But I've worked with some NetGear hardware (on long term projects) that gave results that I couldn't argue with.

What is your current router doing that makes you think it's dieing? If the ping times for both the LAN & WAN ports are stable and low ... There's really not much else the box needs to do. Unless it one of those models with an SPI firewall that cronically tanks the connection.

[T-Clock Hotkeys]

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.

Hm... Not sure right now as the project is currently back burner-ed while I'm working on a production inventory/management system for the office (and T-Clock 2010 has my off time spoken for).

But I do understand where you're coming from. The scan date (date report saved actually)  is stored in the report file, it's just not given a column to keep the interface as compact as possible. However when you open a saved scan/report the message box that pops up displays the (that) date it was last scanned/saved. Granted it's in SQL (YYY-MM-DD) format, but that was a necessary evil for the SQL back-end and other applications in the suite.

Whenever I save a series of scan reports, I usually name the file using the SQL date format and location ID so it gives me a point of reference that appears on the title bar (opened report name is added to window title).

Let me know if that works for you, and I'll make a note in the project's To-Do list to explore other (less cryptic) options for last scan date verification/notification.

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

[T-Clock Hotkeys]

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

Now included in the new build available in the usual place.

[Stopwatch can now can be controlled form the command line:]

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

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.

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

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.

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.

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

[Stopwatch can now can be controlled form the command line:]

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:
[attach=1]

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.

Re: #2

If those NICs are using public IP addresses and this server is your DC, the short answer is you can't. You also never want to multihome a DC because it causes major problems for your network.

That sounds awfully much like a myth to me ... If DNS is setup properly, all IPs assigned to the DC, will resolve (correctly) as the DC. I spend a lot of time with SOHO/SMB networks, and if you need to isolate services between public & private, and the budget only allows for one box. Multihoming is the safest way to do it without sending the administrative overhead through the ceiling.

This question comes up a lot. Rather than me blathering, take a look at this link. It shows a way to work around this problem.

http://social.technet.mic...86-41b2-9477-27ab158d3932

Luck!

Not sure if that was the link you really wanted, but that guy is just babbling about DNS config (which granted most people do screw up), and never really answered the "Can you use 2 internet connections" question. The answer is simply yes...but you need a router with dual WAN ports to load balance the connections like this one

Public IPs assigned to (a SOHO) the DC ... ... Now that's scary.

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?

Hm... I'll look into it.

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!

I've already got a few issues with the current CLI options, so what else I can do in that direction will depend on how well that turns out.

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

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

Inside Program Files (UAC/File Permissions/etc.) no. Outside Program Files .ini handling isn't really that difficult - So it sounds do-able.

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

Nice to know somebody missed the font issue, I've got 50+ Emails from people that didn't. The new size 8 font is actually not bad now with 2 lines on the (default height) skinned XP taskbar ... But I wouldn't try it on 2k.

I've been thinking it might be nice to get folks to post a SS of their clock configuration - if a vague consensus of form can be found, I'll make it the (new) default.

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. 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. Beyond that ... I'm running out of ideas, but am reviewing the emails I received over the years to see if there is anything else I can add (that won't junk-it-up). <- Hint... ) Next build will most likely be the first beta.

Right, so who are the Vulcan looking make-out twins in the far left corner?

Here are the date time formatting settings i use; frankly i don't know why anyone on earth would use anything but these, so i suggest they be made not only the defaults, but the only option available unless the user is willing to hack the executable:

That seems a bit harsh...even by my (lack of) standards...

That looks like an awfully old build in the screenshot, but in defense (hehe) of alternate settings, here's  my current config at the office.
[attach=1]

Okay, this one is kind of a quicky - but it's for a weird issue that has plagued TC forever. The font size calculation had a bugg that caused the size 8 font to be way tiny (and almost impossible to see). I've reworked the calculation method so now size 8 is actually size 8. While this change causes the clock text to need to be repositioned after settings are applied,  each time (in testing) it needed to be repositioned back to 0 instead of the offset I'd been using to center the clock. This implies (to me) that it's now being calculated correctly which finally allows the clock to properly self-center itself.

I also bumped up the font creation quality to ClearType Natural (it was draft) ... which seems a bit crisper, but I'll leave it up to you folks to let me know if it really is better. Download available it the usual place.

Thank you,

Stoic Joker

Well, much as I hate to regard silence as acceptance ... I gotta go with it.
[...]
As Always, Feedback Greatly Appreciated.

Didn't you see me post above?...  or was the link useless?
http://www.donationcoder....21944.msg199412#msg199412

Yes, I spent a great deal of time studying both your link, and wr975's - therein lying the problem - The more I read it the more it started turning into a "If this week, ws next week, last week..." Bugs Bunny skit in my head.

I tried googling for a clearer (straight) answer but none could be found. I was looking for a simple (straight answer) chart of the week numbers going back a few years, that would give me the correct answers according to (Hoyle...) the ISO standard, so I could compare TC's output to it. What I found was warring Brain-Monkeys clashing (pontificating) over end of week 53 vs. week 0. ...At which point I gave up, and went with what I had.

So at this point it's up to you guys to tell me if it's "right", as the only one of the 3 that I can/could verify with any accuracy was the Ww SWN - Which I ended up writing myself because the Timex formula struck me as just way to convoluted a method of answering a simple question.

Week = floor(((DayOfYear) + 6) / 7);       // (Can't miss - End of Problem)


Thank you.

Interesting, but only 49 "surprises" ... Novell doesn't count - Not since they switched to (/jumped/bought) Suse because their own OS was too arcane to survive on the new hardware (no DOS drivers for SATA == byebye Novell). So They damn well better be dog-fooding that puppy.

Below is some feedback for: T-Clock 2010 (alpha -5- Release to DC).zip

1. All 3 of the afore mentioned Week-of-Year options listed above.

I haven't tried to grok the week stuff, but FWIW, I put Wm Ws and Ww in a custom format under "Advanced Clock Configuration Options".  What I see currently is:

[copy or print]
12 12 12

Perhaps that's working   Anyway, just some feedback on that functionality...

Yes at this point they all line up, but Ww (SWN) will go to week 13 on Thursday, Ws will go to 13 on Sunday, and Wm will go to 13 on Monday. *Shrug* I guess on other years it will skew farther - Making for a more dramatic effect. All I know is a lot of people were after this option (showed up frequently in the 300+ Emails I have received), so I had to figure out how to include it...Even tho the "Standard" is confusing as hell.

2. Finally... a help file describing the currently available custom format options.

I see and have opened a file named T-Clock Help.rtf.  I see sections for Date, Time, and Other Options

7. Finally created help file that explains how to make it do what it does.

Was this a reference to T-Clock Help.rtf?

Yes, Help file was the other most requested feature. While I was tracing through the output formatting code line by line to decide where & how best to include the week stuff, it occurred to my Hay why not take notes ... and those notes are now the help file (or at least a reasonably good start on one).

3. Bugg fix for the Menu Dismissal Issue (it didn't always go away when told - It does now)

I'm not sure I experienced this one before and I don't think I see it now.

5. Bugg fix for Child dialogs (Properties/Timers/Stopwatch)  failure to gain focus (pop-under) issue.
6. Bugg fix for bashful tooltip issue.

See remark for 3.

These were rather subtle, but very annoying.

 Thank you.

Well, much as I hate to regard silence as acceptance ... I gotta go with it.

New build now available (on first post) Includes:
 1. All 3 of the afore mentioned Week-of-Year options listed above.
 2. Finally... a help file describing the currently available custom format options.
 3. Bugg fix for the Menu Dismissal Issue (it didn't always go away when told - It does now)
 4. Bugg fix for Stopwatch's Evil Psychotic Twin issue.
 5. Bugg fix for Child dialogs (Properties/Timers/Stopwatch)  failure to gain focus (pop-under) issue.
 6. Bugg fix for bashful tooltip issue.
Note: 5 & 6 were closely related to 3.
 7. Finally created help file that explains how to make it do what it does.


As Always, Feedback Greatly Appreciated.

Address looks to be a public hosting company in Amsterdam

Mailing list sign-up appears to be optional - or at least I could uncheck it and still proceed to the download.

Not sure what to do with it - I have 0 art skills - But thanks for the tip!

Ask not why song the sirens fling...