T-Clock 2010 (download)

[t42]

t42, did you try deactivating other apps to find if one of them may be interfering with TClock?

-LonelyPixel (November 10, 2012, 08:27 AM)

In fact almost nothing to deactivate, because I made several new installations, x86 including, only to test  TClock.

[t42]

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

-Stoic Joker (November 11, 2012, 08:49 AM)

All above commands are working OK. Changing the time format in /prop mode is working after restart.
Changing various "Clock Text" options and quality doesn't remove unresponsiveness.

Please note that in the safe mode TClock is fully functional.

[t42]

Also might be worth a shot to try the released with sourcecode build 98 to see if it behaves differently.

-Stoic Joker (November 11, 2012, 08:49 AM)

Can someone kindly compile the build 98 code? Unluckily I can't compile nothing except assembler and usual Linux routine.

[LonelyPixel]

t42, the archive already contains executable files, in the directory "Release". I've just noticed that while building it here and looking for the actual build result in that complicated directory structure. I didn't find the download anymore, though, so you'd have to search for that if you don't already have it. (I've downloaded it 2 weeks ago and can't remember from where exactly.)

[t42]

the archive already contains executable files

-LonelyPixel (November 12, 2012, 10:50 AM)

Thanks, I've got it. Same unresponsiveness as build 95.

[t42]

It is a miracle. After starting once build 98 and (after that build 95 again) with no luck the system (x64 W8 Enetprise) was rebooted. After system reboot both builds are working as it should be.

Update.
Can't repeat the situation on the VM. 95 and 98 are not responsive.

[t42]

Final and identical results, received on three Win 8 x64 systems (one Inspiron i7 and two VM [enterprise & enterprise "N" on Phenom x6])

1. If I run T-Clock from file manager (Total Commander 8.0 and 8.01, no matter with administrative rights or not, UAC is off), it is unresponsive to left and right mouse clicks.
(My message, posted on November 12, 2012, 10:55:45 AM was  not precise because it was a single event. Another such single instance was observed once on another system)

2. Anyway after the shortcut was placed in a StartUp folder, T-Clock is initializing and working absolutely normally. Same if started from Windows "Run" applet. Same if started from Windows Explorer.

3. Started from the .bat file T-Clock is also unresponsive.

Sorry that I could not describe it all in full in my first message.

[LonelyPixel]

Does Total Commander offer multiple ways to start processes? Altap Salamander has some workaround option for that which I've never used. They use a separate process or so to start applications. Maybe TClock cannot be run from a console process, I've never tried that. (Wild speculation: Maybe when the console host is closed, TClock loses its stdout stream and writing to it blocks. Not that it should write something to it...)

[t42]

Maybe TClock cannot be run

-LonelyPixel (November 13, 2012, 08:42 AM)

There were never such problems in Server 2008 R2, Win 7. It is Win 8 specific, maybe only with final builds.
I just checked with Server 2012 one more time, it is OK to start from .bat file and Total Commander.

[pilgrim]

I stopped following this thread several months ago after installing the program. Having looked at it again I have just learned how to get the calendar working, I was under the impression it was not available, and that there is a build 98, which I have just updated to without problems.

My reason for posting is to ask if anyone can help me solve a minor problem:-
When I open the calendar it appears 20 pixels above the taskbar and 20 pixels in from the right of the screen, I have tried moving it into the corner but it always reverts to its original position. Is there any way of getting it to stay in the corner permanently?

Being unaware that the built-in calendar was working I recently discovered QuickMonth Calendar which is very similar but has a slightly different appearance depending on the theme in use.



This does open in the corner.

[cmpm]

That is a windows setting.
The default windows clock - calendar displays a bit above the taskbar and away from the edge as well.

[pilgrim]

That is a windows setting.
The default windows clock - calendar displays a bit above the taskbar and away from the edge as well.

-cmpm (December 12, 2012, 08:45 AM)

Thanks for that I'll stick with the one I'm using, by default it opens in the corner and you have options to put it where you want.

[Stoic Joker]

That is a windows setting.
The default windows clock - calendar displays a bit above the taskbar and away from the edge as well.

-cmpm (December 12, 2012, 08:45 AM)

Correct(ish), The calendar's position is hard-coded into T-Clock based on (mimicking) the behavior/position of the default Windows pop-up calendar.

[TheMen]

Hi!

Since this year I have a problem that the weeknumber displayed in my tray lags 1 week behind the week number displayed in the calender, which is correct. The years before 2013 this was ok!

Can this be fixed?

[LonelyPixel]

Since this year I have a problem that the weeknumber displayed in my tray lags 1 week behind the week number displayed in the calender, which is correct. The years before 2013 this was ok!

-TheMen (January 24, 2013, 01:30 AM)

Oh, you're right, same here. Didn't even notice, not even when the year started on Tuesday with week 0...

[pilgrim]

Although I do not use the built-in calendar have a look at T-Clock 2010\Properties\Miscellaneous - Calendar: First Week of Year (Change to 1.)
Unless I'm missing something that should put it right.

[LonelyPixel]

Although I do not use the built-in calendar have a look at T-Clock 2010\Properties\Miscellaneous - Calendar: First Week of Year (Change to 1.)

-pilgrim-online (January 24, 2013, 04:02 AM)

It doesn't change the week number displayed in the main clock. I don't use the calendar, there's other solutions for that. I just keep the current week number displayed near the date and time. Right now it says "3" but it's actually already "4".

[pilgrim]

I've just being doing some reading on this and in XP in particular it appears to be down to the regional settings in some countries, as applied by MS.
(http://zijlema.basic...ru.eu/wrongweek.html)

What I didn't find was a solution!

[LonelyPixel]

Windows 7 here.
I'm using the time format:
Wm   = ISO Numeric Week-Of-Year – Starting Monday.

[Stoic Joker]

For the calendar's week number set the (miscellaneous tab) first week of year back to 0
For the Clock use Ww to use the SWN (Simple Week Number) option

That should get both to display week 4

[TheMen]

Ww seemed to work end of last week, but now we are already in wk 5 and my T-clock still displays wk 4, see screen capture.

[K-o-k-o]

I'm experiencing the same issues as described with the weeknumber in the taskbar.
Config: Windows 7 + T-Clock 2010 x64 - build 95

- Weeknumber in the Calendar is OK when I set the first week of year back to 0 (miscellaneous tab).
- Weeknumber in the taskbar Clock is 1 week behind when using the Ws or Wm option
- Weeknumber is 1 week behind only on Monday when using the Ww option

[Stoic Joker]

Ww seemed to work end of last week...

-TheMen (January 28, 2013, 05:45 AM)

Glad you posted that, I was beginning to think I was nuts. At this point I've got no idea what is going on, and no time to poke through the code to find out.

[waiwhite]

G'day,

Nice program.

Just one suggestion. Any chance of having a restriction when the chimes will not sound like say from 10 pm to 7 am? 

[mouser]

Not a bad idea.