Protection against accidental click & drag movement of modern skin windows

[Aminifu]

Hi dro,

Can you add protection against accidental click & drag movement of modern skin windows like you did for classic skin windows?

[dro]

Not in a manner that currently would be of any use based on what I can try doing. For classic skins as I've got full control over the window handling I can determine what is being clicked on so it can still allow for things to work like clicking on the buttons & all of that whilst blocking titlebars allowing moving. Whereas I'm not aware of a way that'd allow me to block just interactions on titlebars due to how gen_ff does its windows along with not being able to determine what that part of the window might actually be. I can put in something so you can try out what I can do but the experiencing from a quick re-test of code I'd previously tried isn't nice as nothing can properly react to the mouse.

[etsaman]

I was looking for a similar feature

https://getwacup.com/community/index.php?topic=1775.msg10457#msg10457

Reply #2 second item.

Ended up locking studio.xnf as a workaround.
At least a restart brings back your original windows layout.

[Aminifu]

Not in a manner that currently would be of any use based on what I can try doing. ...

Ok, I understand the difficulty.

Thank you for replying to this again. I don't remember etsaman's request from last year. I don't want to make studio.xnf read only. I do make regular backups, in case I screw things up really badly. I'll stay with that.

[dro]

Making the file read-only only helps avoid the change being saved out but from an interaction stance you can still mess around with things so that wouldn't be doing what you're wanting. If there was a way to know what's a title bar area (though there's the issue of the skins with interactive elements within that area) then something more useful could be attempted but I'm not aware of how to do that against the gen_ff dll as I'm re-using.

With the next dev build if you enable the feature on the classic skin prefs page & then go into winamp.ini & change freeze=1 to freeze=2 then you'll see the crude mode that can be done by it generically blocking the mouse click interactions from being passed on to gen_ff.

[Aminifu]

Sometimes I just want to activate a window to bring it to the top, which what you suggest would help with. Other times I want to initiate a command, so blocking the mouse click in that case would not help.

I'll try harder to keep the mouse steady and/or finally learn some keyboard shortcuts.