Recommended Posts

LClock is a Win32(64bit too now) Longhorn systray clock program. Idea came from Thrawn's .NET systray clock program.

https://www.neowin.net/forum/index.php?showtopic=151437&st=0. LClock is a modified (stripped down) version of Kazuto Sato's TClock Light.

LClock also comes with a simple but configurable popup calendar that opens when the systray clock is clicked. No more double clicking on the clock just to view the calendar in the "Date and Time Properties" dialog box. The calendar also contains reminder feature found in Rainlendar.

LClock with different skins:

lclock1.png

Some skins can be found here:

Skins

PC World Hungary review LClock, Sep 2004 (thanx Stacker!)

review

Please check back often for LClock updates.

note:

- To use a skin, unzip the skin files to where you installed LClock.

- Use "LClock Properties" to configure LClock and Calendar.

- If the background of the clock(black or flat color) or clock text(blurry) mess up after a theme change, just exit and start again.

- If you are upgrading and having problems, please uninstall previous version and delete old ini files.

- Windows x64 please install LClock first then download this: LC64.rar. Follow the instructions in readme.txt. It is alpha, so please report any bugs you find. Thank you!

Changelog:

1.62b September 19, 2004 (Download)

- Alarm popup is top most window.

- Improved calendar skin support.

1.61a September 02, 2004

- "Lowered" LClock memory usage.

- LClock tooltip option applies to clock and calendar.

- Supports 32bit button and background BMP files. When used, alpha blending will be applied.

- Default buttons bmp files are changed to 32bit.

- Changed event manager interface.

- Fixed event manager bugs(auto center, msg field).

1.60a August 27, 2004

- Fixed month buttons ignoring double clicks.

- Added basic reminder(events) feature.

- Enabled tclock's custom cmds(context menu) feature in lclock.

- More languages added to context menu.

1.51b August 13, 2004

- Fixed buffer overrun bug with month or weekday name.

- Better spacing when using extra long month names.

- Disabled 4-clicks to exit LClock.

Must use right context menu or control panel tool to exit.

1.50b August 10, 2004

- Merged 1.2x and 1.3x(1.4x) together. Calendar is now an optional component of

LClock. LClock will work fine without calendar feature.

- Fixed clock hour problem: 12pm shown as 0pm when "Show 00:xx when 12:xx" is checked.

- Context menu when clock is right clicked.

- Auto hide calendar after 5 seconds.

- Calendar animates if "Animate Windows" is checked in WinXP's "Visual Effects" and

Calendar Transparency is off.

- Improved installer.

1.44a Augest 07, 2004

- Fixed LClock not starting with windows bug: windows just opens an explorer window.

1.43a Augest 06, 2004

- Fixed calendar grid.

- Unicode support in calendar!

Converted the default clock.ini and calendar.ini file to unicode.

To get unicode support, you must convert your calendar.ini file

to unicode(e.g. notepad.exe)

- Option to use shadow text in calendar.

- Option to use bitmap as calendar background.

- Option to turn on and off calendar border.

- Option to disable calendar navigation buttons.

- Option to hide Year in calendar.

- Option to display Day of Month in place of AM/PM.

- Also comes with blue buttons(normal sized). Thanks to MrE!

- Some name changes in calendar.ini.

e.g. MonthTextColor changed to DayTextColor

1.42a Augest 04, 2004

- LClock will start on most machines that used to get the following error message:

"failed to start LClock: 3" or "failed to find default systray Clock".

1.41a August 03, 2004

- Option to change Day of Week symbols of clock: "SU/MO/TU/WE/TH/FR/SA".

- Fixed invalid button bitmap problem. Calendar can be configured without buttons.

- Changed Calendar default look.

- Refined LClock Control Panel interface.

1.40a August 02, 2004

- Calendar configurable in LClock Control Panel tool!

- Calendar position control(Temporary fix for position problem).

- Fixed week header and day horizontal stretch problem.

- Transparent calendar window support.

- More calendar control!

1.32a July 31, 2004

- Changed error message "failed to start LClock: 3" to "failed to find default systray Clock".

- Calendar will close when clock is double clicked.

- Option to disable double click in control panel tool.

- Calendar interface change again. Thanks to Stacker!

- Year and month navigation using arrow keys.

- Moved all calendar related settings to Calendar.ini.

- Installer will add shortcut to control panel tool in Start Menu.

1.31a July 28, 2004

- Refined Calendar interface.

- Single click on the clock to toggle the calendar.

1.30a July 27, 2004

- Simple popup calendar.

- Interface change for control panel tool.

1.22a July 09, 2004

- Horizontal offset for AM/PM.

- When in 24hour mode, AM/PM changes to Day of the Week: SU/MO/TU/WE/TH/FR/SA

1.21a July 01, 2004

- Auto-hide taskbar bug fixed.

- Check for ObjectBar before starting LClock.

- Changed "Auto Start" label to "Start with Windows" in control panel tool.

1.20a April 21, 2004

- Control Panel tool!

- Custom AM/PM symbols.

- Hide start menu and Start Menu from LClock.

- Text style support: text/shadow color, shadow type, shadow offset.

- Auto start LClock.

- AM/PM position control.

- Fixed AM/PM and Minute alignment issue when not using ClearType.

1.12a April 17, 2004

- Improved text alignment.

- Improved installer.

- Added Tooltip style option in lclock.ini: Classic or Balloon style.

- LClock icon! Much thanks to jbo for making the great icon.

1.11a April 15, 2004

- LClock2 is renamed to LClock.

- LClock comes with an installer.

1.10a April 15, 2004

- Added an optional LClock2.ini file. Lots of control now!

All documented in LClock2.ini. :)

- Added simple Start Button customization in LClock2.ini.

- Fixed taskbar not updating after clock exit bug.

1.05a April 15, 2004

- 1 pixel of space added between hour and minutes.

- Supports both SINGLE and CONTINUOUS text shadow types.

Single text shadow tested with "Azure" theme.

Continuous text shadow tested using "Reluna" theme.

1.04a April 14, 2004

- Offset the clock by -1 pixel on the y-axle.

1.03a April 14, 2004

- Supports text shadow. Tested using OpusOS theme.

1.02a April 13, 2004

- Fixed hour bug again! Clock width does not update when hour changes from

single digit to double digits or vice versa.

1.01a April 13, 2004

- Fixed time change bug. Clock does not update size when hour changes from

single digit to double digits.

1.00a April 13, 2004

- Released alpha on Neowin.

Edited by RCube
Link to comment
https://www.neowin.net/forum/topic/157465-longhorn-systray-clock/
Share on other sites

err well it looks like i already found a problem

top: what happens when it hides (me thinks it has something to do with tray icon autohide although i havent turned that off to verifiy thats what it is)

bottom what happend the last time i "poped out" the tray to see all the icons (it was coming back fine when i would do this but this last time it ended up like this)

Edit: whish i would read the whole post before i type away and i would know that the background problem is a known issue :pinch:

post-34-1081922072.jpg

Edited by divertom15
this is nice will be testing it out!

suggestion: make some way you can exit the clock with a mouse clicks (maybe the same way the other does with a double click?)

4 clicks to exit...because I wanted the clock to be like the orginal winxp clock as possible. So 2 clicks is still "date and time properties".

As for the autohide problem...I don't use autohide, but I am testing it now.

Thank you all for trying it out! :D

Great work. I really like this clock replacement.

Could a future version have the option of changing font styles?

Everything seems stable for me. The only weird thing is when LC first starts up, there is a narrow band (the same color as the taskbar) that briefly appears when the Windows clock is replaced by LC. It seems that the taskbar briefly shows through when the systray resizes. Just a cosmetic issue that fixes itself once LC fully loads.

Anyway, keep it up.

RW

Finally got text shadow to work!

So please update to 1.03a if you use themes that use text shadows. :)

Text shadow support is the only change between 1.02a and 1.03a.

Everything seems stable for me. The only weird thing is when LC first starts up, there is a narrow band (the same color as the taskbar) that briefly appears when the Windows clock is replaced by LC. It seems that the taskbar briefly shows through when the systray resizes. Just a cosmetic issue that fixes itself once LC fully loads.

Which side of the clock do you get that narrow band?

fix the bug when you close Lclock.exe from taskmanager, it crashes explorer.exe

Yeah it will crash explorer.exe when you exit like that. :p Try clicking on the program really fast 4 times in a row...it should exit much nicer. ;)

is there a way to center the clock in thinner taskbars? i'm using milk 2 vs with the taskbar at the top and the clock is low on the taskbar (see screenshot):

Hmm, I notice this on mine too now that I look at it closer. It's just 1 or 2 pixels too low on my thin taskbar.

This topic is now closed to further replies.
  • Recently Browsing   0 members

    • No registered users viewing this page.
  • Posts

    • WhatsApp is getting usernames, and you can reserve your preferred one now by Fiza Ali Sharing your phone number isn't always something you want to do, especially with people you've just met. Whether it's someone from a class, a local community group, or a sports team chat, handing over your number can feel like giving away more personal information than necessary. That's exactly the problem WhatsApp is trying to solve with its upcoming usernames feature. The company has announced that users can now reserve a unique WhatsApp username ahead of the feature's wider rollout later this year. Once usernames become available, they'll let people connect without revealing their phone numbers. It's a change that makes a lot of sense for group chats. Right now, everyone in the group can see your phone number. With usernames enabled, that won't necessarily be the case when someone contacts you for the first time. WhatsApp says it's opening username reservations early because more than three billion people use the app, meaning plenty of people are likely to want the same usernames. Reserving one now gives users a better chance of securing the name they actually want before the feature launches more broadly. If your preferred username is already taken, WhatsApp will also offer a built-in username generator to suggest available alternatives. The feature isn't only aimed at individual users. Creators, businesses, and organisations will be able to claim the same username they already use on Instagram or Facebook, making it easier to keep a consistent identity across Meta's apps. Furthermore, privacy is a big part of how WhatsApp is introducing usernames. There won't be a public directory where people can browse or search for usernames. Instead, people will need to know your exact username before they can start a conversation with you. Additionally, users can also choose to enable a username key, which adds another layer of control by requiring people to enter that key before sending a message. Once the feature rolls out, people who choose to use a username will no longer have their phone number shown when messaging a person or business for the first time. If you want to reserve a username, make sure you're running the latest version of WhatsApp, then head to Settings > Account > Username. The tech giant says usernames will roll out gradually over the coming months, and users will receive an in-app notification when the feature becomes available in their country.
    • When I think about a network, there are really two aspects, the hardware and the wiring. So here is what I would do for both. Wiring: Use Cat6A for the patch panel, outlets, and all structured cables (cables installed in walls). Run plenty of Wireless Access Point (WAP) cables, as a general rule, assume a signal can only pass through 2-3 walls and can't pass through a floor (that is conservative, but trust me on this if you want strong WiFi)  Cat6 patch cables are fine for now if you don't plan to run 10gig, those are easy to replace later if needed. Run OS2 single-mode fiber to anywhere you think you may have a server or sub-switch. (yes, single-mode for everything on a small network, don't mess with multimode unless you have entire racks of servers and that minor module cost and power savings will matter). If you really want to future proof, also run fiber to any high density WAP locations, it is likely that WiFi 8 WAPs will push the limits of 10g. Run 6-12 pairs of single-mode fiber between your MDF and the building's MDF, even if you only need 1 or 2 pairs now, those extra pairs will pay off down the road. Hardware: (its easy to say "get all the features incase you need them", so instead of futureproofing, I am going to take approach of suggesting areas worth investing in, and areas you can save money). Don't overspend thinking you need every feature on every port. You don't need 10g on every port, you don't need PoE on every port. Don't overspend on redundancy either, unless you are ready to buy two of everything, don't waste money buying two of some things and not others. Dual power supplies are worthwhile, but probably not HA or multi-path redundancy.  Get 1 "distribution layer" switch that your router/firewall will connect to as well as all your access layer switches below. This should be a 10g switch with a combination of copper and SPF ports and should be a fully managed switch. Given that you said it is a small network, I suggest also using that distribution layer switch for servers and WAPs, meaning it will need PoE. Speaking of wireless, get good professional tri-band WAPs, and either turn on the band stirring options, or limit 2.4 to an IoT only SSID. This will provide a solid WiFi capable nearly everything but the highest of bandwidth clients...you could even consider skipping wiring workstations depending on usage. Access layer switch for workstations and printers can be cheaper switches, 2.5g is a good sweet spot between price and future proofing, but even 1g is fine for most individual clients (the kind that could probably be fine on WiFi). You can consider saving a little on access layer switches by only getting 1 PoE switch for whatever needs it (remember your WAPs are connecting to the distribution switch, not here), and non-PoE for your workstations, because desk phones are falling out of favor. You can also save money here by not buying managed switches if you don't need them--but really do some soul searching there, if you go this route, then anything that isn't on your workstation VLAN would either need to be connected to the distribution switch, or its own access layer switch. Also, don't feel like you need a fancy fabric stacking switches for your access layer, that is the point of the higher-end distribution layer, to remove the need for things like that at this level. Home Hardware: I'm realizing the above assumed an office setting, if this if for your house and home lab then the above still applies, but you'll probably want everything managed and PoE, just because, but you probably also don't need multiple access layer switches. If your total port count is below 24, just skip separating distribution layer and access layer and just get one nice switch with the features you want. If you are at the point of considering a 48-port switch, I would instead get a nice high-end distribution switch for things that need it, and cheaper access layer switches with specs based on the needs of connected devices. For home use, don't worry about home running every device to the main switch, there is nothing wrong with running sub-switches for your media areas and office, those essentially become your access layer, just look for sub-switches with a 10g uplink so sharing bandwidth isn't an issue.
    • Google Meet brings Gemini note-taking to AI Pro and Ultra subscribers by Karthik Mudaliar Google's Gemini-powered "Take notes for me" feature inside Google Meet is now available to Google AI Pro and Ultra subscribers. The features work on Google Meet for web as well as on mobile, and Google says that subscribers can use it for meetings they host in many supported languages. As the name suggests, "Take notes for me" allows Gemini to listen to a meeting, generate a summary, identify action items, and save the notes as a Google Doc in the user’s Drive. After the meeting, the organizer receives an email recap with the summary and action items, while the notes can also be attached to the related Calendar event depending on the meeting setup and sharing settings. The feature isn't automatically turned on for everyone, though. Google says that all meeting participants are notified when note-taking is turned on, and users can start it from the pencil icon in Meet or enable it for future calls through Meet’s meeting records settings. For work or school accounts, administrators can also control whether the feature is available and may require explicit participant consent for note-taking, recording, or transcription features. The feature first launched back in 2024, when it was available just for selected Workspace users. Over the years, Google added refinements and more options, including the ability to enable it when scheduling meetings via Google Calendar. Google's support docs say that the feature currently supports English, French, German, Italian, Japanese, Korean, Portuguese, and Spanish, but only one language at a time. Meetings with multiple spoken languages are not currently supported, and Google recommends using the tool for meetings between 15 minutes and eight hours. The new feature makes Google Meet closer to its rivals that have AI tools already built in. Microsoft Teams has recently started offering Copilot and intelligent recap features that summarize meetings, surface highlights, and help with follow-ups, while Zoom’s AI Companion can also generate meeting summaries from desktop and mobile meetings.
    • GnuCash 5.16 by Razvan Serea GnuCash is a personal and small business finance application, freely licensed under the GNU GPL and available for GNU/Linux, BSD, Solaris, Mac OS X and Microsoft Windows. It’s designed to be easy to use, yet powerful and flexible. GnuCash allows you to track your income and expenses, reconcile bank accounts, monitor stock portfolios and manage your small business finances. It is based on professional accounting principles to ensure balanced books and accurate reports. GnuCash can keep track of your personal finances in as much detail as you prefer. If you are just starting out, use GnuCash to keep track of your checkbook. You may then decide to track cash as well as credit card purchases to better determine where your money is being spent. When you start investing, you can use GnuCash to help monitor your portfolio. Buying a vehicle or a home? GnuCash will help you plan the investment and track loan payments. If your financial records span the globe, GnuCash provides all the multiple-currency support you need. Between 5.15 and 5.16, the following bugfixes were accomplished: Bug 421610 - RFE: Include logical dates for View->Filter by "date range"The Select Range section of the Date tab of the register's Filter By dialog box is changed to provide relative, specific date, or days ago options for the start and end of the filter range. The Show number of days item label is changed to Show from days ago to better reflect what it does. Bug 436105 - esc key not working as expected in register: Enable the escape key to cancel a field edit. Bug 797384 - Gnucash doesn't handle commodity prices with big numerator/denominator properly. Bug 798004 - Next gen UI for stock transactions Bug 799314 - Add "enter now" option in scheduled transaction editor. tab to allow users to select the scheduled transactions to be included in a “Since Last Run…” window. If there are no instances of a selected transaction triggered by today’s date, the next instance is triggered. Bug 799751 - autocomplete crash Bug 799759 - Users can't Enable entries via Checkboxes on Scheduled Transactions PageAllow the Enabled box in the list of scheduled transactions to be operated instead of having to open the transaction editor dialog and change the Enabled checkbox. Also added use of the Name column as the secondary column sort for all the other columns. Bug 799762 - Poor handling of cases where hidden/placeholder accounts are used in the account register Bug 799766 - Double line preference not respected in search register Bug 799767 - POST /accounts in bindings/python/example_scripts/rest-api is broken Bug 799777 - `xaccSplitSetParent`: reparenting a committed split silently drops its KVP slots (online_id, cap-gains links) Other changes & improvements: Numeric values may now be selected to copy in the Accounts page. Add new Finance::Quote source Finnhub.io: Free API key (personal/non-professional use) available at https://finnhub.io. Set FINNHUB_API_KEY environment variable to API key to use this source. As of June 2026, free tier API limit is 60 API calls/minute. The Investment Lots report has new optional columns for Computed Annual Growth Rate. Python Bindings: Improved translation of primary object (Account, Transaction, Split, etc.) so that they can be treated as normal Python objects. This is accomplished with SWIG magic so no existing code is obsoleted. Python Bindings: Better conversion of GLists to Python lists. Python Bindings: Destroy the QofSession in the Python Session dtor to prevent leaving the database locked. [engine] Add first-class online_id accessors for Split and Account and make them available to Python bindings, removing the unused Transaction online_id property. Improve C++ implementation of QofBook. Correct the Doxygen doc for qof_instance_get/set_kvp. [gnc-log-replay.cpp] fix incorrect guid dump Add some Boost library requirements needed by libgnucash-guile to CMakeLists.txt so that missing feature will fail at configure time. Use Compile-time Regular Expressions instead of std::regex in gnc-filepath-utils.cpp and instead of boost::regex in the CSV importer, with the CTRE v3.11.1 header added to borrowed [gnc-filepath-utils.cpp] null check char* arguments Add ChartJS licenses. Removed AEX from list of commodities. euronext.com is now using JS based anti-webscraping. [report-core] always offer options summary in reports. This is useful to debug reports. The Add options summary option is removed because it's no longer optional. Remove remaining obsolete IMContext from sheet Fix blurry text in HiDPI offscreen-rendered widgets Add port field to database connection dialog: The convention of appending the port number after the host isn't obvious. When editing a split in the register treat the account as being changed only if it isn't the one selected before editing instead of if the user performed an edit Return immediately from qof_book_destroy if hash_of_collections is null. If qof_book_destroy is called on a QofBook* freshly created with qof_book_new (usually because it was used to create a session that now must be destroyed) it would try to empty the non-existent hash tables, crashing. Clean up Flathub metadata to solve warnings at flatpak build time. Be consistent in naming GncPluginPage and GncPluginPageRegister HTML: Remove unimplemented function declarations. [gnc-html.cpp] remove unused buggy string conversion functions Convert libgnc-html to C++ Apply -Wall -Werr -Wmissing-prototypes to C++ compilation on Windows and fix the resulting errors. New and Updated Translations: Arabic, Croatian, Danish, Dutch, German, Finnish, Hungarian, Korean, Norwegian-Bokmal, Spanish Download: GnuCash 5.16 | 176.0 MB (Open Source) Links: GnuCash Home page | Other Operating Systems | Screenshot Get alerted to all of our Software updates on Twitter at @NeowinSoftware
    • Microsoft finally launches WSL Containers in public preview by David Uzondu Microsoft has announced that WSL containers, a feature that allows developers to run Linux containers natively inside Windows without the need for Docker Desktop, is now available in public preview several weeks after Microsoft previewed it at Build 2026. To use the new container feature, you first have to install the latest pre-release version of the Windows Subsystem for Linux by running a quick update command in your terminal: wsl --update --pre-release After installing, you'd get access to the new Linux container CLI (wslc.exe) and the programmable API. Microsoft said that the CLI has a "familiar format" that matches the toolsets developers already use every day. If you know standard Docker commands, your muscle memory will translate directly to wslc.exe, which even features a built-in alias called container.exe. You can quickly run a full Ubuntu KDE desktop container by exposing ports, or pass your graphics card straight into a machine learning environment to run PyTorch workloads. Passing the --gpus all flag inside the run command instantly links your hardware. Image via Microsoft As for the API, developers can now embed Linux container operations directly inside native Windows applications without exposing the command line to users. The team integrated the API directly into MSBuild and CMake, so developers can define container steps directly in project files. Apart from bringing the CLI and API into public preview, Microsoft also said that it's working on a new default file system called virtiofs to speed up file transfer rates between Windows and Linux. Microsoft also introduced an experimental networking mode named consomme, which resolves compatibility issues with corporate VPNs by routing Linux network traffic straight through Windows. One thing to note about WSL containers is that they don't run in your standard WSL distributions; instead, every application and CLI session spawns its own lightweight Hyper-V utility VM in the background. This basically reduces the chances of one app snooping on the container of another app.
  • Recent Achievements

    • Reacting Well
      NovaEdgeX earned a badge
      Reacting Well
    • Week One Done
      NovaEdgeX earned a badge
      Week One Done
    • One Year In
      BA the Curmudgeon earned a badge
      One Year In
    • Conversation Starter
      rosiecharles earned a badge
      Conversation Starter
    • First Post
      KMilenkoski1202 earned a badge
      First Post
  • Popular Contributors

    1. 1
      +primortal
      534
    2. 2
      +Edouard
      269
    3. 3
      PsYcHoKiLLa
      150
    4. 4
      Steven P.
      98
    5. 5
      macoman
      66
  • Tell a friend

    Love Neowin? Tell a friend!