10
« Last post by dro on January 20, 2026, 07:25:09 PM »
Oh that. I vaguely remember some reports about it but never really got to the bottom of it other than it seemingly being related to how winamp registered itself for file associations (not something wacup does in its preview state) which could for some installs then conflict with the OLE handling that is needed on my side to allow for some of the external drag+drop handling to work correctly. It however shouldn't have affected things when just starting the wacup process & is a shame I didn't know about it beforehand as it might've been possible to capture more of the wacup instance within that state vs what I had in place when it was last reported but if wacup is loading ok now then I'm not going to worry as much about it.
With the cursor handling, I've had a quick play around after fixing the non-skinned issue I saw as mentioned in the prior reply & if I change how the cursors are loaded it's possible to have the OS scale it up based on the screen dpi settings which might be enough for what's wanted.
The only obvious downside is that the scaling applied can be a bit crude making the cursors look a bit blocky depending on the size it's starting out with to begin with but that might not be an issue depending on the screen & how good the user's eyes are.
I'm still debating if I turn this change into something that can be controlled via the preferences (e.g. turning the use skinned cursors checkbox into a drop-down so it can be off, as-is, OS scaled) but that might not be needed so will need to see what it's like in use for others. Alternatively I might have to look at trying to scale the cursor image elements myself using a different solution & then passing that onto the OS to use but that also might not be needed.