[quote who="Neil Banfield" reply="15" id="2245947"] What build of Windows 7 do you have installed? [/quote] Official Release Candidate, build 7100
jmontesi4
While hovering over the windows button, the button is cut. If clicked or if I move out, the button is drawn complete Edit: Tested with "Aero Metal" and "Diamond". With "Leo" the button is always drawn correctly Your computer has a Windows Experience Index base score of 3.4 Your Windows Graphics Exp
Technically a bug but I'd rather see as an enhancement request: If you try to save a read-only file you should get a message telling you that (Or the option to "override" the read-only flag). Right now OE defaults to the "save as" dialog, which is fine if you are aware of this behavior. At best this can be confusing. Another nice and related feature: A "read-only file" visual flag (Easy stuff: just append "[Read-Only]" to the filename at the title bar!)
1. A custom context menu with the available custom coloring profiles (quick color profile change) from the WB bar icon 2. Support for Windows Theme Packs
That MAY NOT BE true in most cases, but I'd be better on the safe side than risk a 1 millionth chance of getting his/her pc locked. You are also asumming s/he is using Windows XP. BTW, I have seen computers locked at boot time because they didn't have enough page file. Kernel mode files (aka drivers) are loaded before the user interface goes up skipping (or failing to load software components) will not. An out of page file before loading the interface prevents loading the interface.
Citizen uglycow (Reply #47): I beta tested Vista, but I did not get all the info... or maybe I did receive it and ignored because it didn't affect me or maybe I ignored some of the info because MS sent a lot of newsletters and emails. Regardless, if MS do attempt to lease Windows it will backfire to them with negative PR and possibly class action suits against them. IT IS A BAD IDEA by definition and if EXECUTED IT WILL BE THE WORST IDEA OF THE CENTURY. Not to offend bean counte
Charge you for using your computer?? Where in blazes did you find out about that? Seriously, I don't know all the fuzz about Vista being bad, wrong and whatever you say. Most of the "bad things" (WGA, Validation, DRM, etc.) from "big brother" is their attempt to secure their stuff from being pirated. Their DRM schema is basically a "I don't trust people because people lie, cheat and lie" statement. If you pay for the stuff you will not have any trouble at all (I haven't g
Warning! If you do not have enough RAM (or lots of programs/utilities that load system/kernel mode/driver files such as antivirus, firewalls, etc.) you'll be unable to boot again with no page file unless you select safe mode at the boot menu. If you have more than one disk/partition clear the page file and set another in the other disk/partition. Reboot and defrag your disk, then reverse the page file change (or not). Or buy (or "try before you buy") a fully featured defrag pro
It happens while debugging with Delphi 6, using the "XP Charcoal II" skin (Maybe others). If I put the cursor over the titlebar buttons (Close, Minimize, Maximize) I get an exception: "Access violation at address 6605CB9D in module 'wblinds.dll'. Read of address BAADF0?D" Where ? depends on the button (0 for close, 2 for maximize, 4 for minimize and 6 for restore) The programs runs without a glitch if run outside the debugger (or with another skin). <b
Or create a 1 by 1 pixel bitmap on paintbrush with your favorite color, save it and use it as background stretched (Or use your desktop size and do not stretch it)
Thats correct.
Ok, after updating to the latest beta... Still crashing Explorer, but this time it gets worse. I end with a darkened desktop, and the desktop is barely usable and some times freezes. More info (including crash dump file) available on request
Don't get it here either - neither "Tools->Check for App Updates" nor "Tools->View App Updates" reports anything new... Currently running: 2.24a[b].182 build 113 Same happened to me, but I Redownloaded SD Central from www.stardock.com and the update was detected. Now I'm running
Sorry for double posting here, the other post was misplaced and I think you should know about this bug. WindowFX's feature Task Switcher causes a Division by zero error when you try to access it through its combination keys if you dont have any applications minimized or shown on screen. I have reproduced this bug several times. I rebooted my machine and changed the combination keys but the problem persists. You may reproduce it pressing the combination twic
Couldn't edit my post (webpage error). Forgot WindowFX's version: WindowFX 2.89[b].003 Edit: I've been cheking the crash data. The crash is caused by a Division by Zero error on wfx.dll... hmmm Zero Apps on task bar?
I tried several times and every time the effect was the same. I tried to 'switch' with no applications on the taskbar (apps were minimized on the system tray), Explorer crashes. I used different key-combos but the problem remains. In addition, I get 5 'screens' on the switcher, with dupled windows. (ie: If I had Notepad open once its shown 5 times), is this behavior expected or something is not working right? Sys:
Thanks, That "works", well sort of I get video but disabling overlays causes flicking. Oh well, nevermind. I'll disable WB while using VLC I'll tell the folks at videolan, maybe they can do something... <img src="http://images.stardock.com/wc/icons/wc.gif" border=0 alt="Posted via WinCustomize Br
Somehow the video is not rendered; all I get is a nice gray area (the sound plays normally). I tried loading different media formats (MPEG, WMV and AVI) with the same results. I had an old version (0.8.2) of VLC (www.videolan.org) and tried updating it (to version 0.8.4a, latest available) but nothing changed. I also tried adding per application exclusions (even disabling skinning on VLC) but they don't work. All I can do is to unload WB
Just to say thanks for a work well done. I have a lot of problems on Win64, but WB works flawlessly I just want more x64 software available (and more drivers too ) Keep up the good work
A few things I noticed Note: Opaque skins (Without transparency) do not have this problem If you use CursorXP, the cursor is drawn behind the title bar buttons. If you use Object Dock, the Always on top setting is not working. Sometimes getting back from full screen Direct3D mode causes the process to fail specially if paging occurs. The tray icon does not close if you unload WB from the configuration window. Windo