MS-DOS Prompt

I want my freaking MS-DOS Prompt to get skinned.  I know the details behind this not working in WB5 so save your breath if you're just going to state that SD disabled this in WB5.  I know this already.  My gripe is that... I WANT IT TO WORK AGAIN!!!  I didn't buy WB5 as a downgrade.  Fix this on the next beta build please.  This is getting old.  F your PerPixel abilities... if you want to impress me skin the shell prompt and make the window transparent capable... like Linux has done for years.
6,115 views 13 replies
Reply #1 Top

Try eConsole ....that'll tide you over till Cmd is skinned again in WB....

Even 'freaking' command windows will be skinned with eConsole ....been using that for years.....it's a Litestepper's thing....

Reply #2 Top

That's not the point, but thanks for the suggestion.  WB4.6 skinned the prompt all day long and if you had a skin that would do window tranparency that would work as well.  Taking that feature away from WB5 just to implement PP is just stupid to me.  I'm sorry, but I just don't see what the big deal about PP is.  At first I was exited to see all the transparent frames and such, but now it's just anoying... people designing skins just aren't using it to full effect and that to me is a waste of a feature at the cost of others.  SD, are you listening?

Reply #3 Top
I'm sorry, but I just don't see what the big deal about PP is. At first I was exited to see all the transparent frames and such, but now it's just anoying


That's the exact problem: Per-pixel isn't just to get transparent frames and those of you that think it is ONLY just for that purpose aren't ever going to see the other effects of it (unless you actually MAKE and DESIGN a skin). Why not read up on the other things that Per Pixel can do then come back and whine some more.
DD


Posted via WinCustomize Browser/Stardock Central
Reply #4 Top
Smooth window frames, transparencies, glassy effects of bars, unlimited start button icon support... k, still whining... still want my command prompt skinned.  So far I haven't seen a single skin that uses all of the PP capabilities and those that do still don't look all that.  Maybe you can list all the wonderful features we aren't seeing yet....
Reply #5 Top

 JRSCCivic98 ....Windowblinds is a program that NEEDS its skinners.  They are important to it, as much as the general user/customer is.

Skinners wanted this functionality, and, as with anything new, it takes time to adopt/adapt implement.

If the per-pixel advance meant stopping the Cmd skinning.....it's not a real 'loss'....most people do very little with the Cmd, anyway, and those who do probably don't use skins at all.

Me, I miss not having it skinned...[and I don't often use a pp skin]...but it's hardly a disaster of biblical proportions.

I'm not even sure if it's one of those things that will or can be re-implimented...

Reply #6 Top
My main gripe is... if you can't have a skinning app that skins EVERYTHING, then it's not all that.  SD and WB is supposed to be the best... and it was until WB5 came out.  The proof is in the puddin'... 11 beta builds after first release and it's still buggy as hell.
Reply #7 Top
11 beta builds after first release and it's still buggy as hell


I think that's indicative af a huge user base with lots of application interactions and a responsive company. WB5 works for most people . . . Stardock could have said "screw you lone user, here's your 75% refund". Instead they release patches.

I spend a lot of time in the command line and wish it was skinned. While I wait for a build that skins it I try to sqeeze my eyes shut real hard to make the console kinda blurry. That helps.


Posted via WinCustomize Browser/Stardock Central
Reply #8 Top

11 beta builds after first release and it's still buggy as hell.

Beta builds, by definition, will be buggy.

What Stardock does is have an on-going regimen of amendments/updates, often chasing some obscure 'issue' that no-one could even perceive or replicate until the product goes public.

If you want a real on-going 'skinnable' try Litestep....it's never made it to a genuine 'full' release yet....and it was originally for Win95.....yes, pre 98.

Functionality/specification/requirements/OS updates/revisions all demand this on-going effort....something that Notepad.exe doesn't need to contend with.

If you are dealing with something that works so CLOSELY with your OS, such as a complete Shell, or in the case of Windowblinds a GUI adaptation/mechanism capable of more than the OS maker had imagined possible then you have to expect that much about skinning is a W.I.P.

It's a fact of life, as anyone in the Skinning 'community' for any length of time can attest to....

Reply #9 Top
I ought to point out that the non skinning of the command prompts is not a bug.  Likewise the non updating of taskmanager while you drag it with per pixel skins is also not a bug.  Its working as designed.
Reply #10 Top
I ought to point out that the non skinning of the command prompts is not a bug. Likewise the non updating of taskmanager while you drag it with per pixel skins is also not a bug


Changes/loss of features between versions might be documented. Throw it in the readme for registered users? Add it to the help file (wb.chm) [Where do you access that from within WB config?].


Posted via WinCustomize Browser/Stardock Central
Reply #11 Top

I ought to point out that the non skinning of the command prompts is not a bug. Likewise the non updating of taskmanager while you drag it with per pixel skins is also not a bug. Its working as designed.


You keep stating that and I'm sure we get it already... here's a question...  Care you elaborate as to why it's this way?  The quote above in bold really reminds me of the old... "It's not a bug... it's a feature." statement.

Reply #12 Top
Care you elaborate as to why it's this way?


You've asked, they haven't answered. Done deal, right?
It's not like you have the right because you paid your $20.

Relax, they'll get to it. It's been stated (I think. Can't find the thread) that is on the list of things to do.


Posted via WinCustomize Browser/Stardock Central