digital_trucker

digital_trucker

Joined Member # 405640
0 Posts 3 Replies 732 Reputation

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]

9 Replies 5,745 Views

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).

9 Replies 5,745 Views

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

9 Replies 5,745 Views

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).

19 Replies 7,369 Views

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]

19 Replies 7,369 Views

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.

81 Replies 24,564 Views

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.

19 Replies 7,369 Views

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?

19 Replies 7,369 Views

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?

19 Replies 7,369 Views

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.

19 Replies 7,369 Views

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.

19 Replies 7,369 Views

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

19 Replies 7,369 Views

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

19 Replies 7,369 Views

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!

80 Replies 15,615 Views

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.

3 Replies 1,397 Views