Jump to content
MSFN is made available via donations, subscriptions and advertising revenue. The use of ad-blocking software hurts the site. Please disable ad-blocking software or set an exception for MSFN. ×

TClock3 0.3.5


Recommended Posts

Well, I'm not sure what I want to do re: WB importing so I decided to upload what I have at the moment. This has some internal registry changes and WILL be somewhat incompatible with current installations (meaning you have to go in and set some things). Overall, though, it's a much better program internally and will enable some more features in the future.

Known bugs:

- Quitting TClock3 can crash some programs. My Palm HotSync Manager doesn't like it when I quit TClock3, for instance.

- Halos do NOT work correctly. If you import a skin that uses them, make sure to turn halos off.

I edited the top post with the new download link (0.3.3).

Edited by WildBill
Link to comment
Share on other sites

well first of all, i think going with selfmade skins is much better then wb skins, imho.

The wbskins come with more then tclock needs, so its big, when there is no need really...

i will look at this new release, thanx again man.

oh btw, did you see you got a sticky now?

i thought it was appropriate so i asked for it! hahaha

now i dont have to search anymore for your posts.


Link to comment
Share on other sites

Limited tests on my Win98SE quickly revealed two major issues, that weren't present in previous builds:

- 100% CPU usage all the time

- quicklaunch icons were all shifted to a clickable menu, while their original taskbar space was empty and not skinned, except for incidental bitmap overlaps.

Systray icons still hidden, still crashes on exit.

I reapplied the BoostMauve theme, as some elements were not skinned anymore due to changes between versions. No start menu skinning, no advanced skinning like halos, etc.

Currently I'm sick, can't test more thoroughly, sorry.

Link to comment
Share on other sites

Well, WildBill, if you're creating TClock for community, and not just for yourself, then i have an advice...

drop all features and code you don't need or want!

That's how i usually do. Don't listen to anyone whining.

Release really stipped down version which is stable and only then start adding features.

As a programmer, i can say that your TClock3.dll code is insanely **** overfilled with features and API which:

0) Don't have sense under Win2000.

1) Duplicate functionality is already present in Win32 API.

2) Don't make sense at all. Let me explain:

ReleaseDC (hwnd,hDC)

How can this code fail? If NT user32.dll is trowing exception at GetDC(), it means your process is extremely badly corrupted and you should just fail hard. If you're tough, check it for <>0 and that's it.

Personally, i believe object-oriented code is harder and worser to manage when you're dealing with hooks.

Wrapping everything in try..except is a bad idea (in all means), better, rewrite main things in flat non-object code, you'll gain speed and simplicity.

I'll suggest you rewriting your code and splitting it into several pieces:

- TClock3Test.exe: why 2,6 MB has to be loaded always? You need just hook loader and icon in system tray (or clock hooked). Split them into TClock3Loader and TClock3Settings.

- TClock3.dll: well, split it at least into 2 dlls: one which gets loaded into explorer.exe only and other into all processes.

Get rid of hooks if you can safely hook API.

Some boasting maybe, but that's how LameSkin is used:

- 30 KB for skin loader, loads bitmaps into shared memory(only startup process);

- 60 KB for shell hooking (30% of its code is actually for taskbar skinning);

- 32 KB for process hooking (15% of its code is actually for window skinning);

- 52 KB skin metrics/drawing API for every process;

- 24 KB for 32-bit icons (consider this as an equivalent for font smoothing) for every process;

So, it is 32+52+24=108KB and PB compiler sucks. Usually with loaded skin memory usage increase is under 2MB.

You can do the same! If you don't want WB skins, use Windows XP msstyles format (it is FAR better than WB ones in terms of simplicity and standartization, and i believe it can't be restricted to Windows XP) or extracted bitmaps with ini file like i do.

You can read a bit of LameSkin skin format if you like:


Note it does not contain advanced taskbar skinning features :(

Link to comment
Share on other sites

well, i think i have to agree with tihiy on this, not that i know anything about this stuff, but hee...

it sounds like reason.

and i do think there are to many features in tclock3.

cut it down, really man do that


Link to comment
Share on other sites

  • 3 weeks later...
  • 2 weeks later...

Uploaded version 0.3.4 and updated the download link. There is nothing new for Win9x users yet. I've started looking into shared memory but I haven't yet settled on an appropriate architecture.

Link to comment
Share on other sites

  • 3 weeks later...

This looks like a very nice thing to add :) I'm wondering if you have any ideas how close/far you are to an non-beta release? Do I need to do much configuring or is this simple plug and play? Does it play nice with games? ;)

Link to comment
Share on other sites

well, listen up man, the option to run with the inifile as cmdlne option does not work any more.

this is because you must set the full skinning option before it takes all the settings.

cant you fix that?


Link to comment
Share on other sites

  • 1 month later...
Hee-hee. It appears to be another fork of TClock2, like mine is. It will be interesting to see where it leads. I'm not sure if I've seen it before or not. I think the author asked me if we wanted to collaborate, but I'm not sure. I don't spend nearly as much time on this as I'd like so my memory is hazy.

It's not that hazy! :)

Yes it's (yet another) fork of Two_toNe's TClock2, development on it has been stagnant for over a year as I've been tied up with work. It's still written in C and comes with both 32 & 64bit versions.

I don't recall what it was that I'd offered to help with either ... but I do vaguely remember doing it.


Link to comment
Share on other sites

  • 1 month later...
  • 4 weeks later...

I've been using tclock2 on my win2k install for years now, feels wrong without it.

Was looking at this one, and I wanted to suggest a feature that would make me upgrade:

tclock should be able to track multiple timezones like FoxClocks:


It feels silly to have a plugin inside firefox just so I can mouse-over the corner and see what time it is for my friends around the world. Makes much more sense to be able to do it via a mouse-over of the system clock, no?


Thanks for considering!

Link to comment
Share on other sites

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now

  • Recently Browsing   0 members

    No registered users viewing this page.

  • Create New...