Night Train: Not always...

Sometimes bitching and moaning will get one thing fixed, but the long term cost may be more than expected.

The forums really shouldn't be the place for rants like this.  Emails to support and private emails to stardock are the place for this type of thing.

The forums are for community support and friendship.  It's worth the investment.

While I agree wholeheartedly with this one other thing is also true. If people complain directly to a company in "private" correspondence about a problem it will more then likely stay that way... quiet and unresolved. It's been my experience that when something is voiced "loudly" in general public it tends to get resolved a lot quicker then if it was approached in a much more professional manner.

With that said, each situation is different and one must always pick the right way to approach things, but in the end contrary to popular belief sometimes voicing your opinions loudly for the world to see gets things done quicker.

A prime example of this is when someone tries to come to a resolution to something with a company (usually a large corporation) and they cannot, but when that individual takes it to the media... oh, the corporation is more then happy to make things right to avoid the public scrutiny.

Keep in mind, that's not the case here, but you get the idea. It's the old "Customer is always right.", "Let's just make them happy to keep them quiet." routine.

Anyway, we've gone way past the point of this thread now... especially since the problem is "finally" resolved. What everyone should get from this thread is an understanding of how quickly things can get escalated and blown out of proportion, even when something as simple as a "wrong keystroke" (i.e. 5 instead of a 1) mistake is made. I still don't believe that's the case here... after all, why release an update to 5.1 so close to the timed release of 5.5? Just doesn't make sense. I believe it more like... 5.5.017 release didn't go as planned because of some server hooha, so we'll change it to 5.1.017 to try and "quick bandaid" fix the server distro issues. We'll worry about the 5.5 upgrades next week instead of on a Friday because if something else goes wrong all hell will break loose... and over a weekend at that.

That's my guess anyway.

Your guess is wrong.

On enabling access to 5.5 RC for standalone WB customers, the server software updated the version number of the release build as well.

On the subject of complaining loudly, I will personally put minor issues / feature requests reported to me nicely higher in the to look at list than minor issues / feature requests reported in a loud / rude manner.

Obviously major issues are a different matter.

Ok, if you say so. RC and BETA versions so far have been 5.49(x)b. The version available for download was clearly 5.5.x.x. Even so, the file the server was handing out wasn't even a mislabled 5.49 (RC or BETA)... it was the 5.1 download.

Whatever, I'm not going to keep arguing about it...

BTW, is command prompt skinning in XP a "major issue" as you put it?

LMAO

Asked and answered a LONG time ago.

Most people don't use CMD.  Most people dig per-pixel windows.  There was a conflict.  Per-pixel won.
It's not a major issue.

(But good try [again])   

I keep getting the feeling that the more that CMD skinning is yelled about, the longer we will have to wait for its resolution.

The harder the push the higher the resistance...

RE:REPLY 71 Hello,

This threat: Wrong version after the update of WindowBlinds 5.50.017.

Before in SDC...
WindowBlinds 5.50.017 = 5.10.017
WindowBlinds 5.49t

Now in SCD...
WindowBlinds 5.10.017 = 5.10.017
WindowBlinds 5.49t

If you have installed wB 5.50.017 (5.10.017), impossible to downgrade without uninstalling the wrong build. But now, the problem is gone.







YOU FEEL BETTER NOW, YOU SAID YOU LOST ALOT OF WASTED TIME WAITING FOR IT TO BE FIXED BUT YET HERE YOU STILL ARE POSTING, YOU [edited - admin]...       


PS: WHAT THE HLL IS IT WITH YOUR HELLO! YOUR NOT ON THE PHONE [and again]

Something is definitely messed up.  I see where things are borked.  I'm trying hard to be nice, dont push your luck.  Your post will be edited.

CerebroJD sets thread mode to +Patience

Ok. Thanks for the nice comments.  

Don't pay any attention to him Darken, I'm sure that not-so-appropriate comment will be dealt with.

Okay.  

re #83 Fuzzy taps fingers on desk...

Typing in all caps is considered rude and is not encouraged....but may be endured.

Personal attack upon your fellow site member is neither 'endured' nor endorsed...

I dunno...I'm not having "any" issues AT ALL! WB works beautifully as do all my apps.
When I ask...boom...everybody is right there. Helped solve a problem I had with Logon Studio and other things. I even used previous betas, at one time when I first started with Object Desktop I had 8,EIGHT, betas on my machine. Everyone worked without so much as a hiccup. I do not understand why some people are having all these problems. My machine is four years old. Everything works. Some have rigs that make mine look ancient. How come?!?

It's not a major issue in terms of functionality. It IS a major issue with it comes to "completeness" of skinning. Not skinning an app is like "half-assing" something. It just shows a shortcomming. I just don't understand why it's so difficult to skin the command prompt, but not any other app known to man. Crap, Vista does it all day long. (Granted vista's GUI is differently coded, but still. Next we're going to hear that WB5.5 won't be able to do per-pixle or command prompt skinning in Vista Home Basic "Because it's not a native feature of Vista HB to begin with". What the blazes?

I wish more people would understand what my point it. It just looks ugly when I open up a command prompt to do stuff (ever hear of tracert... yes, network admins need the command prompt) and the thing looks ugly not being skinned. IT LOOKS INCOMPLETE. How about skinning it without per-pixel... I don't care, just make the window match the current skin. I don't care if the bar is transparent or not.... for now anyway.   

Why is that you can't accept the judgment of those who do understand? Sure, it would be nice if the command prompt could be reliably skinned. It would also be nice if we could levitate but wishing it so isn't gonna make it happen. When it can be skinned without issues, I expect it will be. This horse has been dead so long there's nothin' but bones left.

Even a statement as mild as this is stomped on by the stardock fanboys.

I guess negative feedback is totally ignored here, except to persecute the bearer of such feedback. See:

https://forums.stardock.com/?forumid=166&aid=144365
and
https://forums.stardock.com/?forumid=166&aid=144620

Dan Dunn

Unless the attacked person has something negative to say about stardock; then you can call them a liar, a thief and a fool with impunity.

see:
https://forums.stardock.com/?forumid=166&aid=144365
and
https://forums.stardock.com/?forumid=166&aid=144620

Aw, poor fella. Playing the victim isn't going to get you anywhere, either. Getting help was never on your agenda, anyway.

I'm not looking for any sympathy; I'm just pointing out the hypocrisy of Jafo (a manager at stardock I'm told)

Dan Dunn

Zubaz ignores all your links . . . . you've proven yourself unreliable.

I'll wait until you start being a positive contributor before I give you too much effort.

Vista's Aero skins the command prompt. WB should too.

Dan,

Unless you have something to actually contribute to this thread beyond trolling over your dissatisfaction with Stardock, say it and move on.

Additionally, Jafo is not a manager at Stardock, he's a community volunteer who has given his free time for years to help us in administering this site.

I accidently went and installed this version, and now trying to install 5.49t it tells me Activation Limit Reached.