[Cursors] Alpha Blended Bluecurve & xFree Cursors


Recommended Posts

The standard windows cursors that I found of these weren't alpha blended and the alpha blended ones were CursorXP. So here are some alpha blended windows XP .cur cursors.

Preview 1:

BluecurveCursors1.png

Preview 2:

BluecurveCursors2.png

Download

I can't for the life of me remember if the cursors were animated when I had Redhat installed, if anyone has the original animated images from Redhat itself, hook me up so I can make some animated cursors :rofl:

xFree preview:

xFree.png

Download

The xFree are animated, if anyone can supply the original Bluecurve cursors that would be sweet!

The vertical resize cursor is a bit screwed up. It is missing some pixels on the left side for example.

Anyways there is a reason why I never supply alpha blended cursors with anything.

The thing is that Windows doesn't handle alpha blended cursors very well.

As soon as you start dragging an icon for example the alpha blended part turns in to an ugly black border.

This is what I mean:

post-67-1062285971.jpg

Nope running on 32bit color depth here.......

Maybe it is the Radeon driver, dunno, it happens with any alpha blended cursors.

Schmoove, altough few bugs, alpha blended curs. are much better...

No, if it didn't have bugs (i'm not saying it is the cursor... it is probably XP that is screwing up here) I'd use it, but this way it is totally useless for me.

I drag a lot of icons from place to place and if that means I have to face an ugly black border everytime it will not be usable for me.

Nevertheless, great cursors (if they work)!!!

The R200 dammit. I have a 9000 Pro... which is a R200 too. Might be a hardware bug then. I remember the R200 having some problems with Per Pixel Alphablending in hardware.

Damn ATi  :crazy:

i'm on a 9000 pro... don't have that problem...

I'm on a 8500... and having that problem.

Someone from ATI has to fix this... angry.gif

Some xFree ones as well, I'm not sure on how I'd go about releasing them, there's a copy of the GPL inside the archive but I'm not entirely familiar with it.

Preview:

http://homepage.ntlworld.com/sherry.pontin...Files/xFree.png

Download

Ah, I love these ones. :D

Some xFree ones as well, I'm not sure on how I'd go about releasing them, there's a copy of the GPL inside the archive but I'm not entirely familiar with it.

Preview:

http://homepage.ntlworld.com/sherry.pontin...Files/xFree.png

Download

yeah Jimmac's xfree cursors are the best cursor set in existence.....period.

i remember when i first got it from someone who converted them to cursorxp...

but dazzla i already have the alphablended cursors so someone must have done it before.... not sure who

anyhow... for all you people out there who haven't used these cursors... use them now.......

EDIT: nm it was just a cursor conversion of the cursorxp theme... which doesn't really work well with cursors since cxp has those added resize ones... but now i can use them w/out cxp! yay dazzla =)

EDIT2: the cxp ones were animated.. can u change yours to be animated dazzla?

Edited by eRad
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!