My WB6 WishList

I don't know how many of these issues are technically "fixable" but here are the things I was hoping WB6 would fix/address/work around (on XP):

Titlebar Text Backgrounds (sizing margins, painting method)

Groupbox Header Text alignment (Content Margins seem to have no effect)

All Programs Menu Item painting (alignment so All Programs Menu doesn't open offset by XXX pixels)

Simplifying StartPanel/BottomBar/Logoff Button painting

Start Panel Programs/Places Item Text skinning

System Button Content Margins/Text Alignment/Offset (to allow for placement of small icons) - some apps "obey" the settings, most don't

Dialog background skinning



There are also a few things that worked fine on all my machines before, but are now broken on some of them:

Skinning of certain menus on certain machines (worked fine in 5.49 but not since - I've posted about this before, SD can't duplicate it & assume it is a driver issue - but it worked before.)

Taskbar Sizing Bar painting (transparent now on vertical Taskbars - at least on all my machines)


That's it for the moment.
989 views 15 replies
Reply #1 Top

We think your menu issue has been tracked down thanks to a post from another user.

Basically the issue is when your gamma is set to anything other than default.  This is due to WB reading the gamma setting from two different places.  6.0 resolves this.

The other requests are too late for 6.0. 

Reply #2 Top
Thanks, Neil. That's good news, but I have not had gamma adjustment enabled here.

I've noticed a pattern recently, however, that seems odd but has been consistent - the menus I've posted about skin partially when I'm logged on to the local machine, but are completely unskinned when I'm logged on to a domain. I've tried unchecking "Use Vista UI guidelines when painting menus" but that's had no effect.

As for the other stuff, its taken awhile to "discover" these - 6.1 will be just fine, thanks.
Reply #3 Top
I'd like my Vista Ultimate to show my CMD prompt skinned with WB6 loaded and skinning. Aero can do it, you'd think WB6 could. What's the excuse now guys? Last time under XP it was that the OS didn't natively do it and you removed it under 5.x because you wanted to do transparancy or some junk. Well, Vista CAN do it natively... what's the freaking problem with WB's abilities?

You guys can get upset about my posts all you want, but I think I have a very valid complaint here. It was awesome in 4.x, then it went away in 5.x due to everyone wanting some "non-xp capable advanced functions"... ok, I'll accept that, now... but Vista, you guys just cut the balls off on this one. Admit it.

Now, if you had to do it because you had to make WB6 XP compatible with blur trans, then shame on you. You should not be docking us "new age adoptors" of the new OS because the old guys wanted "Vista capabilities" in XP. They should have just lived with transparency and been happy with that. You want more, update to Vista and then get WB6 to do more. You don't see MS releasing SP3 for XP with Aero enhancements for XP do you? That's what I thought....

BTW, guess what skin I'm running at the moment... yep, Vista's native Aero because of a Start Menu bug with text cutoff and the command skinning issue. Kinda feels like I wasted 15, but I'm trying to be optimistic..... trying.....

:rant over:
Reply #4 Top
I've noticed a pattern recently, however, that seems odd but has been consistent - the menus I've posted about skin partially when I'm logged on to the local machine, but are completely unskinned when I'm logged on to a domain. I've tried unchecking "Use Vista UI guidelines when painting menus" but that's had no effect.


Neil -

I just updated to the release version & the menu painting issue is fixed. I never touched any gamma settings, FWIW, however.

THANKS!!

SD, & you in particular, do more to resolve issues affecting small numbers of customers than any company I've ever dealt with. Props to you & SD. Can't compliment you enough.
Reply #5 Top

You should not be docking us "new age adoptors" of the new OS because the old guys wanted "Vista capabilities" in XP. They should have just lived with transparency and been happy with that. You want more, update to Vista and then get WB6 to do more.

Ah...so it's OK for the majority [XP users] to be 'happy with that' [diminished capabilities] just as long as the minority gets the command prompt skinned?

This is getting to be a bit of a broken record.

If I want my command prompt skinned I drag out 'econsole' ...works a treat...

...and it's skinned with WB6 [or any other].

Reply #6 Top

JSRCCivic98: Ok, thats enough.

You have complained on our forums for almost 2 years about command prompt skinning and enough is enough. 

We have been clear that command prompt skinning would compromise other WB features and I am sorry but you will have to take my word for that as I am not about to get into a discussion about how WB works.

We are perfectly happy for bug reports and suggestions to be posted here, but if we say no to your suggestion then repeating the suggestion while at the same time insulting the developers is unlikely to achieve results.

Reply #7 Top
^^^ I think it's a SERIOUS shortcoming. Especially for Vista users because Aero can skin it just fine. Bad move on your part with the decision to NOT find a solution to this. I may keep harping on it, but it's anoying to constantly find bugs and shortcoming on releases that you guys supposedly tested on countless systems before release. I will give you props on the release going smoothly through SDC for a change... the last few releases of something through SDC had a few hickups due to messed up XMLs and whatnot.

Anyway, please find a way to skin that silly prompt. If MS can do it, so can you. Maybe you can release a WB version for Vista users that has this capability and one for the old schoolers still running XP that does not. I dunno man, I just cringe each time I need to work in the console and 3rd party cmd apps should not be my solution to this.
Reply #8 Top
Why is this such a serious shortcoming JRSCCivic98? Does it affect WB functionality or cause system problems? I bet it doesn't.  
Reply #9 Top
And the MDI buttons are also painting correctly again on all my rigs - presumably due to the gamma fix in the release version. Once again, thanks very much.
Reply #10 Top
Why is this such a serious shortcoming JRSCCivic98? Does it affect WB functionality or cause system problems? I bet it doesn't.


Because it takes away a capability that Vista HAS natively. This is the one thing I was hoping 6 would have BACK in it.
Reply #11 Top
It appears your disappointment will be longlasting if not permanent. Time to deal with it & move on.
Reply #12 Top
It appears your disappointment will be longlasting if not permanent. Time to deal with it & move on.


Kinda like the programmer's inability to get past this one little hurdle in the skinning process. What's funny is I remember the devs saying that once WB was made specifically for Vista because it would use the same skinning techniques that MS uses in Aero that the CMD prompt would be skinned again. I guess not. Lame!
Reply #13 Top
Kinda like the programmer's inability to get past this one little hurdle in the skinning process
Lame!
Making friends and influencing people again.

Why don't you eaither accept the limitations or use another product?

Or just install econsole and be done with it.

There is no feature that SD *has* to support and nothing they have to explain to you.  Drop it.
Reply #14 Top
I've never blacklisted anyone from replying to my posts before. I'm about ready, though.
Reply #15 Top
I just cringe each time I need to work in the console and 3rd party cmd apps should not be my solution to this.


You think ur the only one with a concern? Be happy you don't skin and quit being a pain in the rear.