Small Mouse Cursor in v1_99_45_23528_x64

[Galleleo]

Hi!

I freshly installed Wacup, had some issues while still having Winamp installed and after uninstalling both and reinstalling the newest Wacup x64 Version, I noticed that the mouse cursor in the classic skin is still super tiny. Is there a fix or some settings that I have to change?

Keep up the good work!

[wd9895]

Hi Galleleo,

I didn't notice a change of the mouse cursor in size or design in both versions of WACUP.
I use the classic skin for the testing, too.

[Galleleo]

Forgot to mention: I'm using a 4K TV. Here's a recorded video when I move my mouse in and out of Wacup.

[dro]

I've not looked into what can be done to try to scale the cursors that the skins are providing with most being in the 32x32px range iirc. Turning off the option to use the skin cursors (prefs -> skins -> classic skins) would make it use the OS default cursor (though it looks like the skinned listview header controls aren't following that setting) or it'd involve manually making a skin folder & putting up-scaled cursor ico files into it if still wanting to have it use the default skinned cursors otherwise there's nothing else I can suggest at the moment.

What I am a bit bemused by is the comment about having a winamp install also messing up with wacup present. There shouldn't be any interactions going on between them especially with the x64 build of wacup unless using the same program folder install name had been used causing it to point to the same settings folder (which the wacup installer avoids doing by default nowadays & wasn't something the x64 install did anyway to avoid problems with mixing unrelated x64 & x86 exe / dlls within the same folder).

[Galleleo]

Thanks for your reply Dro!
Yeah it's a bit weird because after installing Wacup for the first time I had the problem of Wacup not opening immediately after double clicking a file - or just clicking on the Wacup shortcut. It took about 20-30 seconds for the window to show up but after that it was fine. Googled the problem and tried reinstalling Wacup - I even used both x86 and x64 versions. Still, after a restart, the window would only open very late on the first run. After that it was fine.

Then I decided to uninstall both and reinstalled Wacup like I mentioned earlier and voilà, the Wacup window popped up instantly. Very weird indeed.

[dro]

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.