Brad....this will kill me. Say it ain't so!!! 

Oh, I remember the first few ObjectBar betas. Those were "special" .

I personally don't care about crashes and problems in betas. What I think was lacking was more communication when the betas were made available, to explain what the aim for those was. Something like: "Here is the first DX 4.0 beta, we did a lot of work on internals to bring the codebase up to Vista/7 standards and deal with UAC. Our plan is to test those changes and then proceed to fix script/UI bugs and add features either in further betas or in 4.1" would have gone a long way.

Now, I know why this didn't happen, but it might explain why there are so many complains.

Here is the list of bugs I reported in the past which I re-tested against the first beta. The full details and repro-steps should already be in your bug tracker. You can also find a list of old problems on thomthom website.

I'm no expert on this but, why make it backwards compatable then? Make it work in Windows 7 and maybe Vista and be done with XP. By the time it comes out if beta, there will be even fewer XP users. Move forward with it, not backwards.

I, for one, and I suspect many others, keep UAC turned off anyway, just because it's a pain in the ass. I realize you can't expect that of everyone, but UAC is crap.

Littleboy: Thank you!

You're welcome . Good to know all these test objects and bug reports will end up being useful.

Not if he retires it at 3.5!!!

Whether it makes any difference remains to be seen, but at least I did something about it (that and writing plugins to add missing functionality that was needed). Most people on this thread did the same at some point, it's just that there aren't many of us

I appreciate the more in depth explanation, it makes all the difference and it does change the outward appearance of what is going on.

My issues at the moment are centered around the broken built-in performance meters. Even the widget included doesn't work properly. Memory reads 100 all the time and CPU is highly overstated compared to the windows performance monitor.

I reported my bugs (so far) in reply #3 of this thread. I've not tested further but will be happy to continue and report if I know someone is actually paying attention. It did seem that no one cared and that was the biggest bug of all.

I would hate to see DX die, it is the only think out there like it.  I would love to see DX used in schools to teach students programming, can you imagine the influx of gadgets?  But im also a realist, i know that the market isnt there like it was years ago, and i know that Win7 has added a lot of problems for DX. If there were easier ways to make some more complex thing, i think DX could sell a lot more, but again, who knows. 

whohoo! someone has noticed my bug reports!

It would be nice if there would be any feedback on these bug reports that I, and others has mentioned. My biggest frustation with SD the past years is that I've not heard anything in return to my bug and issue reports. As for my frustration with DX - I could not find any info on what was fixed, and what was planned to be fixed. Which is why I felt lost and disapointed when I tried the DX4 beta - I found no issues addressed.

I can understand that the UAC and Windows infrastucture is causing pain for the SD developers. But, can't we, the users get some feedback? I have given my spesific issues - a number of times, over several years, in any channel I've found -besides calling up SD support on the phone.

Phoon: The big problem is that when DesktopX was created, it was assumed the community would create the plugins, not Stardock.

In the "old days" of skinning, the skinning community made this kind of stuff.

But now, it's largely end users who expect us to make all this stuff.  I can tell you right now, there's no economic justification for us to make new plugins for DesktopX to deal with Windows 7.

I can happily open source as much of our plugins as possible so others can start playing with it but the idea of hiring a full time C++ developer to work on DesktopX plugins is just not economically viable.

If we had that kind of budget, we'd still have Zubaz here full-time which, as you have seen in this thread, the consumer desktop enhancement market isn't large enough to sustain that kind of thing anymore.

I've talked about this in the past -- the evolution of the skinning community from being skinners to consumers.

It was never sustainable for us to be making all the plugins and such for these programs, that's why they were plugins and not native to the core program -- the idea was the community would do it.

I don't really have an answer to this because you were supposed to be getting feedback from us.

What I can tell you is that I'll be posting in the Object Desktop Blog with status updates.

I did not realize that these plugins were developed by third parties and/or end users.

as the idea was surely that it would be the community who have to find most of buggies in any Stardock programs by testing all the beta's (well, in fact all programs are always in beta's   )

As soon as Impulse began i was sure that Stardock will turn his back to the Customization software ...