Recommended Posts

Ok as some of you know I am back at school right now. Trying to finish up my degree. So development won't be as active as before. It will mostly be bug fixes. As for new features, I have plans. But I can't commit to any dates as of right now:

1. New LClock control panel interface. (multilingual)

2. Better reminder notifier with snooze feature. (Stacker's mockup)

Here comes the maybes:

- more flexable way to skin calendar.

- png support.

- "skin" support for the clock itself. (this is like what akidd suggested...but you can make it look anyway you want. And Longhorn Clock will be the default skin)

Thank you all for supporting LClock, I'll try my best to make development time for LClock. ;)

Has it been suggested for an option to add seconds to the clock? Also to make it look like the regular time/date format...all aligned horizontally like so....(MON - SEPT 13, 2004 - 12:00:36 AM)? I know it is supposed to look like the Longhorn clock, but those options would be nice.

Keep up the good work...it's an excellent clock!

Hey ciaran, nice Calendar layout!

I like it already :)

Is it an actual shot?

If yes, could you share your .ini files and button and other bitmaps as well (in a zip pack)?

I was wondering that too. Start off of that, and fix it so it goes with my vs.

MAybe he'll get on soon.

Ok as some of you know I am back at school right now. Trying to finish up my degree. So development won't be as active as before. It will mostly be bug fixes. As for new features, I have plans. But I can't commit to any dates as of right now:

1. New LClock control panel interface. (multilingual)

2. Better reminder notifier with snooze feature. (Stacker's mockup)

Here comes the maybes:

- more flexable way to skin calendar.

- png support.

- "skin" support for the clock itself. (this is like what akidd suggested...but you can make it look anyway you want. And Longhorn Clock will be the default skin)

Thank you all for supporting LClock, I'll try my best to make development time for LClock. ;)

Good luck with school! I too am at school again, knee deep in graduate studies, so I can empathize with you ;)

I would like to put a request to raise the priority for .png support. I think that this would greatly skinning capabilities and would allow us to create some very slick background. Just my two cents, keep up the awesome work! :D

Good luck with school!  I too am at school again, knee deep in graduate studies, so I can empathize with you ;) 

I would like to put a request to raise the priority for .png support.  I think that this would greatly skinning capabilities and would allow us to create some very slick background.  Just my two cents, keep up the awesome work!  :D

Thank you! Good luck with your school too. :)

What do you mean by this? I have enabled 32bit bmp, it is the same as PNG(has an alpha channel). The only thing I see with PNG is it will allow us to use much smaller files.

Here is the demo again if some of you missed it, all done with alpha channel:

lcprev.png

Thank you! Good luck with your school too. :)

What do you mean by this? I have enabled 32bit bmp, it is the same as PNG(has an alpha channel). The only thing I see with PNG is it will allow us to use much smaller files.

Here is the demo again if some of you missed it, all done with alpha channel:

http://www3.telus.net/croso/media/small/lcprev.png

Sorry about that, I must have missed that.:blush: I didn't realize 32bit did transparencey... Thanks for letting me know!

I'm having trouble creating a transparent effect, can you point me in the right direction?

Had a question about the LClock reminders. So LClock doesn't really remind you if your computer was off and an event goes off. Any chance of changing this so that it reminds you if the reminder hasn't previously gone off?

And good luck with school, RCube. I am in my final semester of graduating here...

ciaran

orliville, you have to create an alpha channel in photoshop.

psac.png

example:

lcprev.png

This is what the alpha channel looks like in photoshop:

ac.jpg

You can also look at the new button bmp files. They are 32bit bmp.

btw: if you use 32bit bmp, you don't need to set the transparency color in lclock.

ciaran00, I like your layout too. Can you send it to me too or just post it here? thanx! :)

Yes that is one of the limitations of the reminder. I have it on my todo list. ;)

Me messing around with ciaran00's design:

http://www.sfu.ca/~yhana/lclock/skins/skin1.png

skin1.zip

It isn't perfect...since the current lclock wasn't made to be skinned with drop shadows. So the solution is not to use them for now. :p

Yes. That is what I wanted mine to look like. How did you do the round corners?

Nice clock, many thanks for it. Also thanks for all guys posting nice skins keeping me busy trying all of them...

Somebody already requested an option for showing also week numbers in the calender ? And maybe showing weekends or some customizable days (saturdays, sundays in my case) in different colors ?

Also, is it just me who thinks there's too much free space on the left an right side of the clock, making the tray unnecessarily big ? I couldn't find a setting in metrics that makes the overall width of the clock smaller.

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

    • No registered users viewing this page.
  • Posts

    • I sort of agree with you on that. I had a telescope - a real hefty thing, although only around 500CHF - that got me so fascinated about the stars and planets. I would stare for hours, amazed that I could see the craters of the moon or the rings of Saturn in "realtime" (quotations because, y'know, speed of light and whatnot). A friend of mine has a telescope like the one mentioned in the review, and the pictures are amazing to look at. But there is something missing for me. I may as well just go to NASA's website and look through their gallery.
    • As opposed to catching bad press because it's the engine's fault? The engine has all the tools a dev needs to optimize their game, Epic isn't gonna hold their hand to make sure they use them. Also, Epic isn't forcing anyone to use Lumen, Nanite or super high resolution meshes and textures. Just because Nanite can render meshes with millions of polygons doesn't mean you should use it like that, in fact, Epic recommends you avoid doing that. Most of the stuttering can easily be fixed by cutting down on unique shaders by using master materials and generating a PSO cache and compiling every shader before loading the game and also managing what must be loaded and unloaded at runtime, it's up to the developer to set all that up properly.
    • I think it depends on what you're looking for to do, and the time you have to spare. With my Dwarf 3, I easily spend 3-4 hour sessions; half an hour driving to an un-light polluted place, another half hour unpacking and setting up the smart scope + tripod for equatorial tracking, then 15 more minutes mucking around with settings and shooting calibration frames, spending a few hours shooting, merging with past photo sessions, etc. It's crazy how time flies and I often get home later than I expected. It's something I still need to set aside a good part of an evening to do, all in all. For one session, where you often need like four for best results when it comes to deep space objects. Even with a smart scope like Dwarf 3, regular non-astro photography is still way more approachable to people getting into photography. I find this is a time consuming niche no matter how I go about it. With practice, I can probably begin cutting time here but I think where smart scopes find their home is among people who love to shoot the night sky but don't have the spare time to go deep with the "navigator level" attunement to the night sky itself in addition to everything else. Having said this, _if_ you have even more time to spend on this hobby, it will probably be even more rewarding to do it more by hand and learn the skies and the details of how it all works.
    • I misread the title and thought Teams itself would be redesigned. Imagine having this one as a native WinUI app.
    • Dell, HP PCs ran into endless reboot, BitLocker recovery loops but Windows 11 isn't to blame by Sayan Sen Last month Neowin reported on a major issue on Dell systems wherein a bug in its official support tool was leading to endless blue screen of death (BSOD) and restarts. Following our report, Dell officially acknowledged its SupportAssist-related crash issue, confirming that the culprit is not Microsoft's operating system but rather a faulty version of its own remediation software. In a newly published support advisory, Dell stated that version 5.5.16.0 of Dell SupportAssist Remediation and Alienware SupportAssist Remediation can trigger blue screen errors and unexpected system restarts. The company notes that the problematic component operates independently of the main SupportAssist application, meaning users should not remove the primary SupportAssist software when troubleshooting the issue. According to Dell, the crashes are linked specifically to the SupportAssist Remediation service, which is bundled with SupportAssist OS Recovery Tools, and as such it has since released an updated version, 5.5.16.1, which is said to resolve the problem. Affected users are advised to first verify whether version 5.5.16.0 is installed by checking the Installed Apps section in Windows Settings. If so, Dell recommends updating SupportAssist OS Recovery Tools through either SupportAssist's "Update Software" feature or Dell Command Update. Dell also advises users to back up important data before performing the update and to ensure systems remain connected to power throughout the installation process. If you are still having issues though make sure to report to the Dell support forum. As it turns out though Dell is not the only PC maker currently dealing with update-related headaches as HP is also facing a separate but probably equally frustrating issue involving recent Windows Secure Boot updates that were released with recent Windows 11 Patch Tuesdays. Similar to Dell, HP also put up its own support article where it explains the issue. The company says that affected devices could hit a brick wall when booting as they run into a BitLocker recovery loop after the April 2026 updates. The problem appears to affect systems wherein the new UEFI Secure Boot CA 2023 certificates fail to apply properly. As such affected users will find themselves entering their recovery key over and over again despite the system otherwise functioning normally. HP says such PCs should be updated to the latest available BIOS version and configured with the necessary Secure Boot certificates before installing Microsoft's Windows 11 Patch Tuesday updates. Systems that are already experiencing the problem may require BIOS configuration changes to restore normal boot behavior. Admins can find information regarding that in the support article here on HP's official website.
  • Recent Achievements

    • One Month Later
      DJC50PLUS earned a badge
      One Month Later
    • Week One Done
      DJC50PLUS earned a badge
      Week One Done
    • Proficient
      Eric Biran went up a rank
      Proficient
    • Dedicated
      Conjor earned a badge
      Dedicated
    • Week One Done
      Windows Guy earned a badge
      Week One Done
  • Popular Contributors

    1. 1
      +primortal
      493
    2. 2
      PsYcHoKiLLa
      246
    3. 3
      Steven P.
      72
    4. 4
      +Edouard
      69
    5. 5
      neufuse
      68
  • Tell a friend

    Love Neowin? Tell a friend!