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

    • You've tried DuckDuckGo and Brave Search, now get serious with SearXNG by Paul Hill Over the last decade, it has become quite trendy to dump Google Search in favor of privacy-preserving alternatives such as DuckDuckGo, Startpage, and Brave Search. These search engines have done a very good job at highlighting dodgy practices by Google, such as adjusting search results based on what it thinks you’ll like (filter bubble) and stalking you around the web to advertise to you. While these search engines are good starting points when compared to non-private services like Google, there are still quite a few issues with them. For example, both DuckDuckGo and Brave Search require running non-free JavaScript in your web browser, which is comparable to running proprietary software on your computer, meaning you can be sure about what it’s actually doing in the background. Another issue is that these search engines are hosted on the respective companies’ servers, and you are using a service that you don’t control. Finally, DuckDuckGo, while offering privacy features, relies heavily on Microsoft’s infrastructure for its results and, in the past, has permitted Microsoft tracking scripts. If you are looking for a more private search solution than DuckDuckGo, Brave Search, and Startpage, then I recommend taking a look at SearXNG. It is a privacy-respecting metasearch engine that can be used via different public instances, which is useful for mobile users, or you can install it on your computer or server and run it locally with maximum control. Unlike Google, Bing, or Brave Search, which crawl the web and have their own search indexes, SearXNG is a metasearch engine, meaning it taps other search engines, stripping your identifying data, such as IP address, user agent, and cookies, in the process. Your search query is sent to the other search engines you enable before aggregating the results. SearXNG has deployment flexibility. If you are a casual user or a mobile user and don’t want to run SearXNG locally, you can use a public instance that is hosted by someone else. The main problem with this is that you are putting trust in the maintainer of the instance regarding stuff like logs that they may keep; good hosts should have a privacy policy explaining their policies. If you are trying to use SearXNG, you can also install the software on your device and then head to 127.0.0.1:8080 in your browser and search from there. While you don’t have to worry about a third-party admin like the public instances, search engines could ultimately block your IP address if they frown on you pulling in their search results locally. If you want to run it locally, it’s a good idea to use proxies or VPNs to hide your actual IP. You don’t have to worry about this with a public instance, as search engines never see your IP address. The main privacy benefit of using SearXNG is that it isolates your identity from the underlying engines that it’s capable of searching, such as Google and Bing. These search engines will only see requests coming from a generic server, so they can’t profile you and create a bubble filter that influences what results you see. This also ensures that your search engine doesn’t turn into an echo chamber that prevents you from reading alternative points of view. As a free software project, you are allowed to inspect SearXNG to make sure there are no negative features bundled inside. This sets it apart from the privacy search engines mentioned earlier because you can’t check their source code. As a meta search engine, you are not restricted to getting results from one source. Due to the fact that it scrapes content from other websites, your SearXNG instance will periodically get blocked from different providers, so it’s good to select a range of sources as a backup. While enabling all of the services will give you great results, this can make searching slower. I am personally happy with slower searches for the best results, but you can always check which providers are slowing down your search from the search results page and disable them to speed things up. If you want decent results quickly, enable the main search providers such as Google, Brave, DuckDuckGo, Qwant, Bing, and Yahoo. This way, you get wide coverage without the latency. On the Engines tab in Preferences, do note that there are different tabs, such as General, Images, and Videos, with their own providers that can be toggled and are not covered by "Enable all" while on the General tab, so be sure to dig into each. Just a note, if you want to enable everything, press "Enable all" in one tab, then hit save at the bottom of the page, then do the next tab, and so on. If you press "Enable all", then do that in each tab, and then save, nothing will stick. When I had just some of the search engines enabled, I searched “define nefarious” and results came back with the definition of “define” - obviously that was a sucky result. However, when I had everything enabled, it found dictionary pages for the word “nefarious” and even had an inline definition on the sidebar, which is quite nice too - that was delivered by WolframAlpha for anyone wondering! Probably the worst thing about this meta search engine is that the engines you select are saved with a cookie, so you must enable them on every new device you use SearXNG on, including if you decide to go into incognito mode with your web browser. Honestly, I would say this is the most annoying aspect, and perhaps if your browser lets you choose a separate private browsing search engine, then it would be best to use DuckDuckGo for this portion of your browsing. Another weakness of SearXNG is the random blocking of it by search providers. When you are on the results page, expand the “Response time” box, and it will show things like “Suspended: too many requests” or “access denied”. This is why it is good to enable several providers so that there is always a fallback to get results from. I won’t pretend SearXNG will be for everyone, however, if you enable all of the providers and put up with the slower response time, the results can be really amazing. Even if you don’t want to use it as your daily driver, keeping a bookmark handy that links to it is a good idea if you ever feel like doing a deep dive into a niche topic where other search engines are just failing to bring up any good result, due to the amount of sources it looks on. If you’re interested in radical user control over the software you use, installing SearXNG locally can also be a good idea, but be prepared to be temporarily blocked from sites if you trigger bot sensors without a VPN. Personally, I’ve opted to use a public instance, rather than install it myself. If you want to use it via a public instance, head over to searx.space to find a provider. Let us know in the comments if you have used SearXNG or its predecessor, Searx. What do you think about the quality of the results?
    • Dear Neowin, If it is not too much trouble, can you start using the new-ish designations for Insider Preview? "Experimental" is different than "former Dev" as it can apply to different models, eg 26H1 or 26H2 etc, right? No need to seed confusion IMHO. And, please "finally" update your graphics. OK?
    • Did you see their FAQ, its quite good. Have a look in the Advanced section. https://delta.chat/en/help
    • Just install Linux Mint that is a real blessing and many times cheaper because you can continue using your old Windows computer/laptop with the latest Linux updates.
    • Interesting share -- however it does not make sense: Email messages get stored somewhere, so how is Delta Chat "based on email" and decentralized without actually storing anything? By Web3 standard practices, the various Relays would require dedicated storage to make messages available to the recipients (like a large series of message queue channels, akin to racks of traditional post office boxes)... and Contacts must be two-way confirmed in order for encryption keys to be exchanged (ostensibly every key-pair is uniquely bound between sender and recipient) and the Relays would preserve the public keys in order to facilitate message carriage... or every device stores all sorts of keys and contact info. All of this to say, decentralized messaging is like running Bluesky nodes except instead of discovering/browsing public feeds by various posters (at the given node) these Delta Chats would be relaying encrypted messages (via Relays) that only trusted recipients would have the appropriate decryption key (their own private key) to read it. But this doesn't solve the "it's like email" sales pitch. The only way it's like email is that there's encrypted binary stuff being transported from your app into the federated ether of Delta Chat Relays for others to decrypt (hopefully only the intended recipient)... but outside of this federated relays framework, it is absolutely nothing like email.
  • Recent Achievements

    • Week One Done
      Woland13 earned a badge
      Week One Done
    • One Month Later
      Woland13 earned a badge
      One Month Later
    • One Year In
      bernmeister earned a badge
      One Year In
    • Week One Done
      Scoobystu earned a badge
      Week One Done
    • Week One Done
      tuben earned a badge
      Week One Done
  • Popular Contributors

    1. 1
      +primortal
      503
    2. 2
      +Edouard
      226
    3. 3
      PsYcHoKiLLa
      158
    4. 4
      Steven P.
      75
    5. 5
      FloatingFatMan
      71
  • Tell a friend

    Love Neowin? Tell a friend!