Oh goody. Another thread discussing Jesus, God, and other Bronze-Age superstitions.
digital_trucker
Any transparency in the borders appears to extend to anything on top of it (buttons, text, etc.).
Nope, defining a specific graphic doesn't fix it here either. Also, I've duplicated the problem in another app (3DGameStudio) as well as PSP8. If you remove SKS' exclusion, it does it there too. Link to this thread posted to WindowBlinds newsgroup. [Message Edited]
I'm not talking about the small window (I know that has to do with margins)...I'm referring to the fact that when a small MDI window is MINIMIZED, the minimized graphic is cut off (along with the buttons). The minimized window skinning is new to WB, btw. Names are not the problem, either (I always use unique names).
Although giving Jafo a handful of shiny objects will help.
http://pws.chartermi.net/~digital_trucker/test_gauges/MDIerror.jpg Only does this with WB skins, not XP skins. Minimized MDI windows appear to 'inherit' transparency from the normal window...despite having set an image for minimized MDI windows. Also, if the MDI window being minimized is exceptionally small, the size of the minimized graphic is clipped, cutting off some buttons
Skin-O-Mat
Both of the skins you mentioned have large enough top borders to keep from clipping the text on the bottom. For instance, if your top border is only 3 pixels wide, the text on the bottom would only show as a 3-pixel strip. So text backgrounds still wouldn't work for that (I've tried it).
No doubt about it. Either 'ScriptActivate' and ScriptDeactivate' are broken or the documentation on it is in error.
I've almost got it... Anyone know of a way to script a button so that the script runs independently of mouse events? According to the documentation, I should be able to call a script on window activation or deactivation. However, there is no setting for that in SKS, and adding it manually doesn't appear to work. [Message Edited]
TIP: Be careful with transparency use in top window borders. Apps with MDI windows have problems. When you minimize an MDI window, it 'inherits' any transparency from the normal amximized window. Also, if the MDI window is exceptionally small to begin with, the resulting minimized bar will be clipped, chopping buttons. Possible bug? Clipping problem does not appear when WB is unloaded.
Button Type = Text Layer (still have to specifiy an image for the text to be visible - even though you won't see the image) In the text buttons section, you have to specify all the parameters. Doesn't appear to use defaults.
Okay, I got the text button to actually display text. New problem: getting the button to change it's width according to the width of the window. Obviously this has to be done with a scripted button. I admit it...scripting has me stumped. Anyone familiar with scripting buttons want to step up to the plate?
According to Brad, the text can also be put on the bottom of the window by using a text button. I'm having trouble getting it to work though. Anyone care to reveal how to get a text button to work?
Putting the text on the bottom is impossible (for now) without a corresponding wide top bar. That'll prevent the text from getting clipped. As far as the button thing, meet me in IRC on the #stardock channel and I'll hok you up with the button thing.
iirc, if you want to put buttons anywhere other than the top bar, you have to use the UIS2 format. I'm not completely certain about this either, but I believe that in order for anything to show up on top of the borders (buttons, text, etc)...the border behind it can't be transparent. So if you're using UIS2 and have an opaque border, you *should* be able to put the buttons anywhere you like.
I finally got the straight dope on this. It apparently has to do with the way WB renders the windows in memory before drawing. It's going to require quite a complicated fix, it appears...so it looks like it'll be a while. Y'know...it's amazing how much hate and discontent can be avoided by answering a question in a timely manner. <img src="http://images.stardock.com/images/smiles/notsure.gif" bor
Thank all that's good and holy! I'm not alone anymore!
Well, here we are 4 months later and the bug still goes unfixed (and unacknowledged). Even though it's been independently verified. Here's a quick SIMULATED screenshot of something along the lines of what I'd like to do, which is unfortunately impossible without the bugfix... http://pws.chartermi.net/~digital_trucker/test_gauges/WishlistWBA.jpg I hear through the grapevine that the bug is known about and being ignored because I'm the only one running into it. It's interestin
Might see more originality if more of the dud settings in SKS actually worked correctly...and were supported by WB.
I've got a couple of mail zoomers I'll let you have for $600. I could use a pro copy of Photoshop.
There's a place for both styles. Minimalist tend to be better for everyday working skins, and the wizzbang are more for fun. Which isn't to say that that line can't be crossed. I think you'll see a return to more creativity in skins...styles come and styles go.
I certainly won't miss you, after your repeated rufusals to accede to requests from many of the users that night...but I'm not going to debate you here or anywhere else on this. I'm simply going to have a drink to celebrate your decision to never return. Cheers!
While we're on the subject, please note that the same rules apply to the irc.stardock.com channels as well...(no names, you know who you are)
You're absolutely correct, the majority of images used in WB can be reduced to 256 colors without any real loss of detail. TGA images on the other hand, which are used for some transparencies, have to be full color, although most of them are quite small and shouldn't impact performance.