nazcalito

I have been using windowblinds since version 3,I think. I used to write skins but when the skin language changed to include perpixel window frames I began to get lost. How do you set the active titlebar height or size in a uis file? Here is the problem. When I start up my computer, the windowblinds skin I am using sets the height of the active titlebar to something like 22 pixels. This makes the taskbar at the bottom of the screen also 22 pixels high -- apparently t

Deskscapes does not work on dual monitors for me, where the second monitor is being run in composite mode. The second monitor ends up with a blank screen. This is funny because plain old static wallpaper easily displays on the second monitor. I was using a laptop, running the second monitor out of the HDMI port into an HDMI to composite conversion box, and then out to a composite input on a switch box that outputs to an LCD TV. I have to convert the signal to composite becau

update on this-- when I first invoke Firefox (4.0b13pre) I get no title bar, and then when I click on it, I get the bar with the big plain buttons, and then if I minimize and maximize it, I get the bar back with the skinned buttons. I sent the about windows for my desktoop, my laptop (where I notice the problems) has the following about windows info: WindowBlinds version : WindowBlinds 7.2 (build 95 x86) WindowBlinds is installed correctly on this PC Wi

OK WindowBlinds version : WindowBlinds 7.2 (build 95 x86) WindowBlinds is installed correctly on this PC WindowBlinds appears to be activated on this PC Your machine supports per pixel borders on WindowBlinds skins. (BenQ E2400HD (Digital)) 1 is attached to NVIDIA GeForce GTS 250 Wblind.dll 2010/11/29 13:40:20 Wbsrv.dll 2010/04/01 10:44:

I have WindowBlinds 7.2 (build 95 x86) running on Win XP Pro. I recently noticed that I cannot make a window any narrower than a certain size. On this monitor, which is 1920 pixels wide, the minimum window width is about 860 pixels. I first noticed this when I was using WordPad to display lists of items on-screen and wanted the WordPad window to be narrow. When I close out of windowblinds and view the window in Classic, I see very wide versions of the the maxim

ran the latest update of windowblinds 6.3 on impulse, rebooted and got the message that WB was missing a core dll and I had to reinstall it. I'm going to be reinstalling 6.0 because 6.3 still won't display the material in what used to be called the xpstuff.xp file with older skins. WB 6.0 won't work with Firefox 3 but no matter, the last time I installed Firefox 3 it crashed anyway -- toolbar didn't have a back arrow in it and when I tried to put one in via customize, CRASH!

Could someone remind me what settings in the .uis file determine the taskbar height / thickness? In unskinned Windows, I know the taskbar is the same height as the titlebar or caption buttons, so I can adjust the taskbar height temporarily using Windows display properties. (The functions "small taskbar size" and "large taskbar size" in the WindowBlinds configuration panel are unsatisfactory -- selecting "large" stretches the quicklaunch buttons vertically, making them tall

I wish someone would tell me what changed between WB 6.0 and the later versions so I could fix the skin where the taskbar / start menu doesn't skin. Do I have to update the skin to put in the per pixel window frame information, or are the newer versions still backward compatible? It must be something with the .uis file, because pointing the uis to another skin's taskbar and start menu doesn't work. Any gurus here?

I have kept at it with no luck. The skin displays correctly in the viewer window (with sample taskbar and start panel) but when I select it, the start panel and taskbar are unskinned. The standard skins included with 6.3 work correctly. 6.0 works. The problem arose in the upgrade from 6.0 to 6.2. I have tried an upgrade install from 6.0 and an uninstall and reinstall of 6.3 with no luck. If I change the uis file to point to one of the xpstuff.xp files from a

I tried uninstalling and installing 6.2 again and that time none of the skins were skinning the task bar and start menu. This is what the trial versions of WB do isn't it? Sounds like something is not right with the upgrade process and it turns off skinning of the task bar and start menu.

I'm back to 6.0 reinstalled. I haven't updated WB via stardock bewcause I'm afraid the same problem will happen. I tried directly installing 6.0 after uninstalling but I got the same problems that I had with that skin. During one of the uninstalls and reinstalls I found that none of the skin files had .uis files! (Luckily I had backed them up.) Nice to see you're still with Stardock, Neil. I remember you from version 4 days

after uninstalling and reinstalling WB to try to solve the problem, I am now getting a message saying "Maximum activations reached" when trying to reinstall.

I uninstalled and reinstalled the skin and it started drawing the magic purple color in the transparent zones. I deleted the .wb4 files and reloaded the skin and the magic purple was gone, but the partial skinning problem remains. WB 6.3 also does the same thing with a modified version of that skin I was working on. are there deprecated commands that were done away with in 6.3? I've had Window Blinds since version 4 or maybe even 3, before WinXP came out.

I'll bet if I uninstalled WB and reinstalled version 6.2 there would be no problem. I think the change is between 6.2 and 6.3.

The OS is WinXP Pro with Service Pack 3 and all updates.

it's an old skin called infernal machine that I wrote. It worked fine up until 6.2 I tried uninstalling, downloading WB 6.2, reinstalling, and then upgrading using stardock central but it still doesn't display the taskbar and start menu and the toolbar buttons are also not skinned. The only items skinned are the window frames, menu elements, and scroll bars.

after upgrading to WB 6.3, the taskbar and start menu are not skinned in the skin I use, but skinned in the skins that come with WB 6.3. My skin's uis file refers to xpstuff.xp as the source for the taskbar and start menu skins but not to any other .xp file and not to an .xps file. PS. WB 6.3 now works properly with Firefox 3 including the latest nightly build.

This is an age-old problem in Windowblinds that seems to be getting worse as WB progresses. I have used WB since version 3 or 4. There is a setting in Windows display properties that you can check (under appearance) where you can elect not to use the skin defined font size -- but it doesn't seem to work right, at least for me. Make a backup copy of the .uis file of the skin you are using and then edit the .uis file with something like notepad. Find the font sizes and increase

Has Stardock ever thought of creating a feature where all of the features of a skin would stretch and shrink depending on the resolution of the monitor? I have the familiar problem of running a monitor at high resolution and having to constantly tinker with the display and font sizes in the uis files in order to keep the text readable but not annoyingly large.

The portions of Firefox 3 menus that are over the toolbars at the top don't disappear in Firefox 3 when the windows is skinned. FF3 has to be excluded. This is not a windowblinds site issue -- this happens everywhere.

I got it working

okay that's interesting -- I switched to one of the stock skins (diamond) and the taskbar got fatter when I increased the size of the caption buttons. So there must be something in that skin that my skin doesn't have.

When I installed WB 6.1 build 51 via stardock central, the taskbar, buttons, and quicklaunch buttons became considerably smaller. Changing the caption button size in Windows display properties no longer has any effect. I'm using Windows XP with Service Pack 3 RC and the latest patches.

the WB configuration dialog used to work just fine -- now it doesn't adjust properly for DPI configuration. Some stuff is off screen including the dialog for excluding applications from windowblinds. Can't Stardock at least make the configuration dialog window resizeable?

Programs that don't work with WB 5.49(d)(b), even if excluded: Gimp 2.2 Limewire Frostwire IAS viewer (a program for viewing Jpeg2000 images.) These programs all seem to be multi-platform ports from Linux. I know that the last three rely on Java, so the incompatibility is probably between some installation of Java and WB. Others have said that their installation of Gimp 2.2 works fine with WB, so I suspect the Java component, which can vary from machine to machine