There used to be a way of applying sections per-app, not sure if it's still in. But it wouldn't be able to do that. You could use a per-app skin, and set it to skin them and then use another as the main skin.
GreenReaper
Press the Winkey to get the start menu up, then press alt+space. Then try sizing the menu. You may also be able to move it to another edge of the screen.
Yes. Yes, we do. *eg*
"This coke's gone bad . . ."
Hmm. I posted here, but it seems it didn't work. I'm not sure how CursorXP works. It might be using the IAccessible interface to retrieve the name of the mouse cursor object which changes according to the cursor state. I do develop some software, but not for Stardock. Some is at www.greenreaper.co.uk If you want to change the background of an XP themable app there are APIs to do it (but you need to be set up as the thing doing the skinning, don't know how that works),
Also, UIS1 offers the choice of using additional frames in the border images to specify different images for those windows to the regular ones, so make sure to check that out.
Carlitus means toolwindows. They will normally only be skinned by UIS1 skins like Blackcomb, since UIS2 does not have specific support for them. However, you *can* force WB to skin them using a UIS2 skin by adding SkinToolWindows=1 to the [Global] section of wb.ini in your Windows directory. It is not guaranteed to work correctly, but does in the majority of cases. If you are looking to make a skin that includes native skinning for them I would recommend using the UIS1 (basic) format.
Excellent . . . *cackles*
Because WBLoad.exe doesn't do the work. It's all done in WBlind.dll. WBLoad just stores the bitmaps (AFAIK, perhaps not even that) and hooks the DLL into each app's message chain. It loads the bitmaps into shared memory and then lets the DLL instances blt from there. WB code runs in the process of every skinned app via WBlind.dll.
No, I'm just an interested hanger-on. I can't speak much for the specifics of implementation, although I do believe WB uses normal BitBlt/StretchBlt calls to paint the images. Personally I think the slowdown is partially because you're using VB (and I get to say that - I'm a VB programmer . But using a timer and repainting is probably a problem as well - you really only want to repaint when you have
This has been worked on for WindowFX 2.0. Not sure if registered users of 1.2 get a free upgrade, but you might. Currently due out August, although it does tend to slide and depends a bit on when NVIDIA gets it's act together driver-wise.
This has been worked on for WindowFX 2.0. Not sure if registered users of 1.2 get a free upgrade, but you might. Currently due out August, although it does tend to slide and depends a bit on when NVIDIA gets it's act together driver-wise.
You may be able to get a free upgrade depending on when you bought it. https://www.stardock.com/support/ will send you the latest version you are entitled to. If you do want to upgrade, you might want to consider an OD subscription - any WB registered user can get it at only $34.95.
I have a nice 19" monitor, but I all I feel comfortable with is 1152x864. I try and make my skins compatible with most resolutions, but sometimes it's just not possible to cater to extremes.
Oh, and then you have to paint that text onto the control with DrawText or something.
You use GetWindowText if it's in your application, otherwise you have to send a WM_GETTEXT message via SendMessage(hwnd, WM_GETTEXT, maxnumofcharstocopy, textbuffer). For VB, all should be long values, maxnumofcharstocopy should be, say, 255 and textbuffer should be = string(255, " "). SendMessage should be defined as: Declare Function SendMessage Lib "user32" Alias "SendMessageA" (ByVal hwnd As Long, ByVal wMsg As Long, ByVal wParam As Long, lParam As Any) As Long Good luck getting
This is in win 98/ME, right? Don't think you can do it in 2k/XP. Anyway, I don't think WindowBlinds has ever skinned it in that situation - I'll ask the programmer about it and get back to you if there's a way.
Stardock HQ is down, probably due to power blackouts (there was a 5-hour long one earlier today). WC is hosted separately so remains up.
See, this is why we want comments with the ratings.
To get in, use Ctrl-alt-del at the logon screen (you may have to be in safe or VGA mode - to get these options press F8 on booting Windows XP). Go into your windows/system32 directory. Look for logonuix.exe. Rename it to logonuix.bak, then copy logonui.exe to logonuix.exe. That should restore the default logon.
I like WindowBlinds! *g* Well, I can't really comment on the "compelling enough to pay" bit, but for me it's the control WB (and OD) gives over my environment. I live on my computer, and I think it's fair to say a lot of those here (though not all) do so to. I want to live somewhere comfortable. Stardock products let me do that.
Yeah, it's mostly resources, but if even 1% of it is MS stuff, it's illegal. Also, WB skins don't need to get any bigger because they're carting unnecessary gunk around - for example, check out the size of logonui.exe files vs .logonxp logons.
Well, you could package up your computer and send it over to Stardock HQ . . . not sure if they'd send it back, though. *g*
As I understand it, WB hooks into the message loop of each app and intercepts the paint messages. So if X is told to paint a combo box control, WB steps in and paints it itself.
Yes, Stardock is trying to figure out how to do it legally, without redistributing MS's stuff (as using .msstyles does). Possibly 3.5? Not going to be in 3.4.