SkinStudio dialog hook

from Stardock Forums

Didn't see a better place for this so I figured I'd toss it in here.  It's not a major issue or anything but opening SkinStudio and bringing up one of the edit dialog's for instance "Edit per pixel frames" pulls up the dialog without a parent HWND set which ties hotkeys to the desktop instead of the application.  The side effect of this is that windows related hotkeys such as F5 that handles refreshing windows get hooked into the dialog regardless of SkinStudio being in the background, inactive, etc.  Using F5 such as in a browser to refresh the page merely end up switching the active window back to SkinStudio instead.

I wasn't sure if this was intentional or not since normal dialog's do this to interrupt all input to the screen until they're dismissed although in this case it only affects Windows default hotkeys since TOPMOST is not set.  Setting the parent to the existing dialog should correct it assuming there wasn't a specific reason preventing it.

windowblinds
4,107 views 2 replies
Reply #1 from WinCustomize Forums Top

If you're looking for quirks in a program, skinstudio is a good place to look. I doubt that they are intentional but there are many and they probably will not ever get fixed (they haven't so far). Think workaround.

A workaround for this is to use the refresh button in the browser rather than the F5 key.

Reply #2 from Stardock Forums Top

I'm actually not that worried about it for the most part.  If it really got to me, I'd just patch the window style out myself since it wouldn't take but a few minutes at most.  I just felt it was better to post things on here rather than fixing them for myself silently since not everyone has that luxury.

The refresh key was just an example though and even with that, it's used to pull up my web debugging tools in Firefox.  I haven't taken the time to go through all the hotkeys affected.  These are all the result of Windows finding the WS_POPUP style on that window without having a parent window set on it so it's just Windows doing what it does and we'd have to go through the list of default ones to know which of them all are affected.  Setting the parent to the original window doesn't really change much except fix that particular problem so that it could only interrupt input to the program and not the entire desktop interface.

I'd be interesting in hearing about some of the other's though so I know which are known already in case I run across them if you have a few minutes to type up some of the one's you're aware of down.

Curtains - Customize Windows with additional styles