As of Groupy's beta 1.02, the above scripts is probably not needed anymore. At least on my Finnish keyboard layout the new versions seems to work properly! :)
htalvitie
Neil, thanks - wasn't aware of the backwards option with Ctrl modifier! Until the new version comes out, this modified AutoHotkey workaround-script gives the feature to those that can not produce the required keyboard combination yet. (Numpad1 switches to the previous tab, Numpad3 to the next one): #InstallKeybdHook ; Groupy, Go to previous tab Numpad1 Up:: Send {vkA2sc01D Down} &nbs
Same problem here, but I found a solution (or at least a workaround) that might work: Using the AutoHotkey utility and this script, I was able to get the keyboard shortcut to work even on my Finnish layout: #InstallKeybdHook Numpad1 Up:: Send {vk5Bsc15B Down} Send {vkC0sc029 Down} Send {vkC0sc029 Up} Send {vk5Bsc15B Up}<br
Yes, I'm familiar with the history file (shows up on the Stardock Central UI). I was actually studying it last weekend, when I attempted to figure how much progress there has been within the last 12 months or so. Can you tell based on that file? I couldn't. The revision file doesn't provide any references to issues reported or requested by users. It has even stopped reporting dates for the releases (I can only guess why). I would appreciate, if the revision fi
waiting for WB6 who maybe (or the clean install) will fix it Speaking of fixes and versions... I haven't found a issue tracking system anywhere. It's difficult (if not impossible -- without testing each patch) to find out, what fixes are included in each release.
Just my additional 5 euro cents: On a Terminal Services connection, identical double-clicking closes window always. I'm using rdesktop v1.5.0 on a Gentoo Linux (IBM TP770ED) and a rdp5 connection to my Windows Server 2003 box. Interesting (and also quite nice), that my WB-themed desktop works better on a remote desktop connection to a Linux box than natively. Just slower. :-/ And as somebody mentioned here earlier, it's not consistent from app to app. There seems to b
did you try to change the speed of the double click occurs in less or more? The 200 ms speed detection quote was from the Autohotkey script, not built-in Windows value. That script is a kludge, and doesn't provide a real solution. Just in case you are interested in the built-in values, I have experimented the different double-click timeout and pixel thresholds. I have modified HKCU\Control Panel\Mouse\DoubleClickWidth and HKCU\Control Panel\Mouse\Dou
Since people have misinterpreted my description of the problem repeatedly, I will once again add a visual aid. This time with an animated GIF, since some commenters haven't clearly analyzed the Flash versions. I'll try to keep it simple this time.
And you have a global override to make double-clicking the Titlebar "always" close the window. I do not want to make double-clicking the title bar close the window..
Some on this thread have blamed the skin author of the leaving the double-click action non-defined for the system icon on the top-left side in a window frame. I'm using a Stardock-provided skin and checked the customization on system icon: As far as I can tell, it's properly defined.
[I don't have the energy to do a proper grammar anymore. Sorry for my ESL, try to decipher...] Thank you Jafo for the (yet another) not-so-interesting infomercial about what skinning is all about. Oh well. I should just stop commenting these post's since it's clearly becoming a sad troll fest, but maybe there is still somebody who is able to discuss the technology and not childish OS advocay. Just to recap: I'm came here to report a bug to the WB manufacturer. Yes, on
You want the steering wheel on the right instead of the left? Gotta order it that way. Does that help? No, it doesn't. According to the product description, WindowBlinds by itself should "give the user freedom to completely change all aspects of the GUI of WindowsXP." I'm not feeling the freedom here. I'm simply asking for the manufacturer to stop interfering (randomly, as shown in my screencast) with my existing "steering wheel" by <
I've always thought WindowBlinds is the right tool for making run-time selections like these - not SkinStudio.
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" a
Apologies to those offended regarding the harsh tone of my initial posting. Maybe I simply had too high hopes after waiting for over a year for WB to mature, and then let down because small things have not been taken care of.
Sounds like Wb may just not be for you Harri Oh come on now. I understand everybody's different and everybody has personal preferences. If you are happy with your WB, fine. Maybe I'm picky, but when software I purchased has flaws, I expect the vendor to fix them - within reasonable limits - and not accept any guidance about changing my working habits. Pardon for my ESL, Harri
I save the second click and use a Single Click on the end button on the right. It's usually got and X on it (for Exit) but not always. In some cases if you hover your pointer over it you may see a tooltip that says "Close" I, on the other hand, try to avoid any repetitive strain injury and really dislike moving over 3000 pixels worth of LCD real-estate just to close one window. <img src="http://images.stardock.com/wc/smiles/Smile.gif" border=0 align="abs
My theory is that the overhead from WindowBlinds message-hooking and/or manipulation changes the order in which messages are processed. Since the double-click detection involves timing and threshold checking, this would sound logical. Maybe WindowBlinds causes the drop-down menu processing hook to override the double-click timer before it gets enough time to expire? Haven't check my Petzold Bible since the Windows 95 era, so don't take it for granted <img src="http://
Aren't there skins you can use that have left oriented buttons? a la mac? why not just add a close button on left to the skins you prefer? That could work, if all applications were themed. Gets pretty confusing when some apps close from the left corner and others from the right. Of course I could always do a double-click, so depending on the app either the first or the second click closes. Unfortunate
I'm not saying it wouldn't work. For some. Sometimes. I'm just saying it doesn't work for me. Most of the time. I don't know what the cause is. I've tried removing everything suspicious, changed the hardware configuration etc. Couple of weeks ago I was in a simliar situation ("Works for me" vs. "Crashes on me") when Safari 3.0 Beta just didn't work . Later I found out why, as you ca
I've always found double clicking on the left corner more time consuming than single clicking the close button I've double clicked the left corner to close Windows almost 20 years. Maybe it's because I'm left-handed Also find the Mac OS X / Finder UI difficult to use because of the cumbersome button placement.. <br
Dear Stardock, Early last year I purchased Object Desktop and ran WindowBlinds 5.0 on my Windows XP. Soon I noticed that most (if not all) skins break the close functionality on the system menu, e.g. double-clicking the icon on the left side of the title bar doesn't close the window as it should. I struggled for a while and then finally uninstalled WB. I was unable to change my Windows habits. Today, I was brave enough to give WindowBlinds another run. I insta