I think Jafo's answers speak volumes about Stardock attitude toward its paying customers.
Start10 works fine with Windows 10. Many, many other programs far larger and more complex than ObjectDock work also fine with Windows 10. Clearly it is not Windows 10 causing the problems ObjectDock has. It is ObjectDock which is sold as "compatible with Windows 10" when IT"S NOT.
I opened a support ticket with Stardock Support a month ago: did I obtain any help with my "particular issue"? NOT AT ALL. Once they get your money you are on your own. Great company, great support. And if you get mad, they call you names instead to solve the problems.
I don’t know if it was one of yours, but there has been one comment here at the end of last year that was similar to yours that seems to have been deleted from the conversation about the fact that OD stopped working properly long before Windows 10, starting with 64bit, with no fix or even a statement provided up to date. My memory was a bit dull, but yes, my problems started long before Windows 10 as well, they only became more when Windows 10 arrived (and clearly I am not the only one with problems).
Since Stardock began telling me I was trolling them and I should open up support tickets for issues existing since years (x64 problems) and already being widely covered here (while I believe in general direct support is really more helpful than posting on forums, especially when Stardock staff does not cover all the threads and issues reported here), I just moved forward to the only one real alternative to ObjectDock that has a yearly subscription, but one guy eager to care for his customers AND his product. I encountered a few minor bugs with it and had some suggestions and got the bugs fixed within days (!), without him whining about Windows 10 or, in one matter being the culprit, Google Chrome. Plus he enganged in a small discussion about usability of features and personal preferences. No dreadful hanging of docks, no ghost icons, no forgetting about screen positions or taskbar hiding settings, (and no accusing of trolling,) it just basically works.
This only goes to say: Through a product as seemingly minor to you as ObjectDock and your non-forthcoming way of handling communications about missing bug fixes for the bespoke, you just lost a once more or less satisfied customer who had bought from you quite some licenses and license upgrades in the past, and I would not be so sure to assume I would still recommend you to friends and colleagues. Possibly you don’t care as much.
If you feel that a product isn’t worth much effort anymore, you should rather discontinue it than handle it this way. If you think you don’t need paying customers, offer your software for free, so no-one can complain .
PS: If you would accuse me of once again not being relevant to solving the problem, my post has two distinctively practical tips to help out:
- Use another software
- Save time and effort spent on Stardock (not) solving long-known and new problems and invest a few bucks for peace of mind.
I would believe this is as practical and goal-oriented as it gets .