WACUP

Preview Build Discussion => Preview Build Discussion => Topic started by: mltgames on March 09, 2025, 11:25:57 PM

Title: Bugs - Docked Toolbar issue with high resolution monitor
Post by: mltgames on March 09, 2025, 11:25:57 PM
Hi,


I'm using WACUP 1.99.27.21136 [Mar 9 2025] @ Windows 11 Pro 10.0.26100.3323 64 bits.

I have an issue with WACUP  - Toolbar Docking, I want to set the WACUP on my 3rd top right screen. Instead of going up like it was supposed, it is going in the middle.

If I lower the resolution to 1920x1080 on the 3 screen everything works, it seems that there is a bug with high resolution monitor and the docking.


Here are my screens resolution :
1st screen : 3840x2160x144hz
2nd screen : 2560x1440x75hz​
3rd screen : 2560x1440x75hz


Windows Setup : ​

​(https://masseware-temp.s3.ca-central-1.amazonaws.com/wacup/1.png)

My 3rd screen :

You can see that it is docking right in the middle of the screen :

(https://masseware-temp.s3.ca-central-1.amazonaws.com/wacup/2.png)


In green I have added where I want WACUP to be dock

(https://masseware-temp.s3.ca-central-1.amazonaws.com/wacup/3.png)


The bug is also there in the original winamp 5.666 Build 3516 and Winamp 5.9.2 [Apr 26 2023].

Thank you for your help!

Best,


Jonathan​
Title: Re: Bugs - Docked Toolbar issue with high resolution monitor
Post by: dro on March 10, 2025, 08:31:31 AM
It's an age old issue with the re-used gen_ff (modern skins engine) plug-in & it's been on my todo list for an age to get around to trying to figure out what that plug-in is doing & if there's anything I can do to try to patch out what it's using to figure out window placement though I think I'm at the point where that time would be better spent on just making the replacement plug-in instead of putting more time into something that needs to be removed from being used by wacup. As such I don't have a solution or workaround for your issue, sorry.
Title: Re: Bugs - Docked Toolbar issue with high resolution monitor
Post by: mltgames on March 10, 2025, 12:36:33 PM
No problem, I understand that it is not an easy bug fix

Thank you @dro for the quick response