Ok, let's wrap this up:
As he said, the action on double-click for the System Button can be set to "close" in the skin - Windows' inherent functionality isn't "broken" at all, just amplified.
Yes, one could fix or modify the skin - with proper tools etc. But in my mind there's a better and simpler solution (see below).
In addition, you can set a skin-specific double-click action for the Titlebar itself to "close" as well, so double-clicking anywhere on the Titlebar (other than on control buttons) will close the window
But wouldn’t this conflict with the existing standard action Maximize/Restore window in place?
Doesn't seem logical nor practical, since I (like most?) have to work between different computers, and functional consistency is nice.
Maybe it's the developer in me who likes solving stuff and making things better, but when I see a bug (or "a missing feature causing problems" -- call it what you want), my mind tries to come up with a way to make it just work.
And this shouldn't be so difficult, after all.
Just in case, here's the summary of WB behavior as far as I have observed and interpreted - and please let me know if it contains any errors:
Three separate and closely related GUI actions can by modified by the WindowBlinds skin author. However, only two of them can be overridden by the user:
1. Double-clicking the title bar (Restore/Maximize window)
2. Right-clicking the title bar (Open the system menu)
3. Double-clicking on the program icon on the left side of title bar area (Close window)
Please let me know if I'm missing something (maybe a hidden option added to 5.51 or something similar), but if not, then how about a simple solution:
All we need is a third check-box to the settings, so the user could override the skin-supplied behavior of the program icon!
Or not?
Rgds,
Harri
I got a new Xp 64 bit disc from MS with my last PC purchase.. guess what.. Photoshop CS2 menus are screwed.. can't use it. [...] You think adobe is going to accomodate every request and suggestion and pet peave of everyone who is dis-satisfied?
PS. Photoshop compatibility in WinXP x64 isn't a "pet peeve from customers".
Also, I don't understand how your comment is related to this topic.
Microsoft released Windows XP Pro x64 in April 2005 shortly after Adobe released Adobe Creative Suite 2. All CS2's are 32-bit programs, so they have to run on x64 with the help from heavy WOW64 "middleware" plumbing etc.
FYI, Adobe has not certified any of their CS2 products to run on WinXP x86.
(My theory your menu corruption might be related to video drivers.. but then again.. just a theory.. and also getting *really off topic* ...)