Will ObjectDock be continued or not ?

Thursday, February 27, 2014 by c242 | Discussion: ObjectDock

Hi,

as a long time customer and subscriber I PLEASE want an honest answer if ObjectDock is still in development or not and if it EVER will work right on 64-bit systems (shortcuts always pointing to c:\program files (x86)) problem. I am really sadly tired of the update politics and public relations on this matter at Stardock at the moment (again). Seen too many good SD-programs going down the drain I relied on (aka DesktopX / RightClick...).

A general update-plan would be great and also a new list of dicontinued apps. Please. CursorFX (Multiplicity incompatibilities) and IconPackagers continued bugs (aka the nightmare creating and always losing changes on packages) would be also interesting.

Please, no "But it works for me !" posts here, we ALL know, there are long time reported bugs that where never fixed.

First Previous Page 2 of 5 Next Last
Gaspershooters
Reply #21 Saturday, April 12, 2014 7:54 AM

Oh,thanks for encouragements,I am really appreciated that.  

bodadog
Reply #22 Saturday, April 12, 2014 8:23 AM

Hi everyone,I see all the ruckus.I also would be very interested in knowing if OD will either be ongoing development or discontinuing the program.I am running OD on Windows7 64 bit ultimate and I have had only one problem with it. The problem is that when I bring up the user interface to change docks and tiles it stops responding for about 30 secs. then all is fine just a small annoyance,but otherwise OD runs fine on my 64bit OS.

Uvah
Reply #23 Saturday, April 12, 2014 8:41 AM

I use OD+ on Win7 64 bit. Works as it should with only the infrequent crashes where it stops working and needs to close. That happened once or twice within the last six months so no biggie. But knowing whether or not OD will get some love is a good thing.

Voqar
Reply #24 Saturday, April 12, 2014 4:07 PM

I'm not sure how you can say it "works as it should"

It works fine if you only deal with 32-bit applications and never need to use the sys tray - maybe.

 

- it doesn't create icons for 64 bit apps correctly and while it is thoroughly pathetic that 64 bit has been around for ages and software is rarely 64 bit even today, there are more and more 64 bit apps coming around

- it doesn't handle the sys tray at all (so you can't really get rid of the task bar) - could be a plug in for this but the app should do it by default since the sys tray has been in windows since the dawn of time

- it doesn't handle steam apps correctly - and granted steam isn't a part of windows but when you consider it has 65m users and Stardock themselves distribute their games thru Steam you might think it would get some consideration.  If windows itself is able to figure out what icon belongs to a Steam shortcut, then OD should be able to do so as well

Considering the absolute zero responses to this thread or the other one I posted here I would guess this product is dead, which is pretty sad.

I could probably get a response on this faster posting about it on the GalCiv III forum, which is pretty pathetic.

 

PS - Rocketdock has similar limitations and problems, which would suggest that this seemingly basic functionality is due to windows itself or something, which makes this product totally useless and is another reason to love/hate MS (I develop in C#/.net and generally love MS but they do some damn annoying things - like IE being a constant thorn in the side of web developers/designers, rendering HTML in outlook with Word, plenty of other stuff, and now this?).

 

c242
Reply #25 Sunday, April 13, 2014 4:31 AM

...

WOM
Reply #26 Sunday, April 13, 2014 12:53 PM

I use object dock from day 1 and plus from day 2.  Still use it with W7.

Chasbo
Reply #27 Sunday, April 13, 2014 1:16 PM

I use object dock from day 1 and plus from day 2. Still use it with W7.

Me too. 64bit Win7. No problems.

c242
Reply #28 Sunday, April 13, 2014 1:31 PM

You both tell me You can do shortcuts to 64-bit apps without problems ? Magic.

Uvah
Reply #29 Sunday, April 13, 2014 4:16 PM

If you mean adding shortcuts to docks for 64 bit qpps like CCleaner I've been doing that from the git go.

gevansmd
Reply #30 Sunday, April 13, 2014 8:54 PM

bodadog

Hi everyone,I see all the ruckus.I also would be very interested in knowing if OD will either be ongoing development or discontinuing the program.I am running OD on Windows7 64 bit ultimate and I have had only one problem with it. The problem is that when I bring up the user interface to change docks and tiles it stops responding for about 30 secs. then all is fine just a small annoyance,but otherwise OD runs fine on my 64bit OS.

 

I'm running on the same setup and can't get the start menu icon to work.  It paints only the left half of the start menu and the right side is invisible.  Also, sometimes it's a CPU hog, taking 25% of the total processor on a quad core CPU.  Other times, it's running but won't reveal itself when I move the mouse to where the docks are hidden.

moshi
Reply #31 Monday, April 14, 2014 4:11 PM

gevansmd


I'm running on the same setup and can't get the start menu icon to work.  It paints only the left half of the start menu and the right side is invisible.  Also, sometimes it's a CPU hog, taking 25% of the total processor on a quad core CPU.  Other times, it's running but won't reveal itself when I move the mouse to where the docks are hidden.

 

you can't really blame OD for this particular problem. opening the start menu at some random location will cause these problems on Windows 7 (and probably Vista and 8 as well).

you can only open the start menu at it's supposed location. if for some reason you don't want to press the WIN key, you can use a VBS for that:

set wShell=wscript.createobject("wscript.shell")
wShell.sendkeys "^{ESC}"
Set WshShell = Nothing

or download it here: http://yadi.sk/d/q9SSD-7fMTSXh 

sgartner
Reply #32 Monday, April 21, 2014 3:04 PM

I'm really disappointed, I just purchased ObjectDock for use with both Windows 7x64 Pro and Windows 8.1 and had no idea it had fundamental problems with 64-bit apps (which I can confirm).  As long as I "pin" a running app to the dock it works fine, but for any app created on the dock in any other way it loses its mind.  It gets the "working directory" correct, but gets the path to the EXE incorrect.  This is screwy.  I had to fix up half of my links by hand after setting up my dock.  I haven't really gotten around to setting it up on my 8.1 machine yet, sounds like it might be painful...

I had significant pain with Fences as well.

Maybe I should return Object Desktop and look elsewhere...

Thanks for raising this issue.

gevansmd
Reply #33 Monday, April 21, 2014 3:14 PM



Quoting gevansmd, reply 30

I'm running on the same setup and can't get the start menu icon to work.  It paints only the left half of the start menu and the right side is invisible.  Also, sometimes it's a CPU hog, taking 25% of the total processor on a quad core CPU.  Other times, it's running but won't reveal itself when I move the mouse to where the docks are hidden.

 

you can't really blame OD for this particular problem. opening the start menu at some random location will cause these problems on Windows 7 (and probably Vista and 8 as well).

you can only open the start menu at it's supposed location. if for some reason you don't want to press the WIN key, you can use a VBS for that:

set wShell=wscript.createobject("wscript.shell")
wShell.sendkeys "^{ESC}"
Set WshShell = Nothing

or download it here: http://yadi.sk/d/q9SSD-7fMTSXh 

 

I'm using a script to get around the problem.  It didn't exist with my vista install, it began when I installed W7.  BTW, I should have explained, the problem is a result of OD interacting with WB.  A standard Windows skin, such as Aero, works perfectly.  Only running a blind, and any blind, causes the issue.  It actually paints properly and then the right side vanishes.  If I install a new OD start menu icon it will work the first time and then do the same thing thereafter.

Neil Banfield
Reply #34 Monday, April 21, 2014 3:43 PM

gevansmd

Quoting moshi, reply 31

Quoting gevansmd, reply 30

I'm running on the same setup and can't get the start menu icon to work.  It paints only the left half of the start menu and the right side is invisible.  Also, sometimes it's a CPU hog, taking 25% of the total processor on a quad core CPU.  Other times, it's running but won't reveal itself when I move the mouse to where the docks are hidden.

 

you can't really blame OD for this particular problem. opening the start menu at some random location will cause these problems on Windows 7 (and probably Vista and 8 as well).

you can only open the start menu at it's supposed location. if for some reason you don't want to press the WIN key, you can use a VBS for that:

set wShell=wscript.createobject("wscript.shell")
wShell.sendkeys "^{ESC}"
Set WshShell = Nothing

or download it here: http://yadi.sk/d/q9SSD-7fMTSXh 


 

I'm using a script to get around the problem.  It didn't exist with my vista install, it began when I installed W7.  BTW, I should have explained, the problem is a result of OD interacting with WB.  A standard Windows skin, such as Aero, works perfectly.  Only running a blind, and any blind, causes the issue.  It actually paints properly and then the right side vanishes.  If I install a new OD start menu icon it will work the first time and then do the same thing thereafter.

I need to correct you here.

Moshi is correct, this is a known Windows 7 explorer bug.  The Start menu will not paint the right hand side correctly when the menu has been repositioned regardless of theme (well other than Windows classic).  That's with or without WB.

It is more obvious with a WB skin, but that's because WB skins tend not to have the right hand side as 99% glass colour and instead use images to provide the tint over the blur (if any).  The glass coloured bit will be rendered correctly, but the image used on top of it will not.  In the Aero skin case this image is that gradient over the glass.

Take a screenshot of the menu with Aero running and then repositioned via ObjectDock.  If you compare them you will see the difference (as with WB the same thing applies where the first paint may work correctly).  The gradient effect will be missing.

This isn't an issue on Windows 8 because with the use of Start8 the menu is provided by Start8 which does not contain this bug.

-TiM-
Reply #35 Saturday, April 26, 2014 9:14 AM

Hello everybody,

i'm new to the forums but a long time customer to Stardock. Since i was thinking about opening a thread like this on my own, i took the chance since c242 already did so.

I'm also worried about the same thing in the end. My story or experiences in a few sentences would be something like this:

01. I found a bug in ObjectDock (actually i found several by now)

02. I report it to the support guys

03. I receive an answer that most likely just tells me that the product is still supported and that i also send i a log from their support tool they link to

04. I do as asked

05. They tell me that they can reproduce the bug but that there is no fix for it and that it is reported to the developers

That's it – literally!

Once every know and then i add an complaint about why they do tell me there is support but when i try to use it, it ends in nothing more like "we reported it". The answer every time is "we do support, we gather bug reports, we deliver them to the developers and there is no more information we have for you". At least they should have a better information policy – i always thought just the support of the german companies over here i such bad. Or sad.

The real sad thing is, as i know that Stardock is not such a big company and that they have other products and other users awaiting help, this has happened before. That was in times before the Impulse disaster, when nearly the same situation occured and we waited years – until Windows 8.1 forced an update due to several incompatibilities – before something happened. Strangely, every other of my Stardock products is updated several times in between. But surely Start8 or WindowBlinds do sell better, aren't they? Funny enough, there are still bugs from back then that aren't fixed until today! And how long do we wait now since the last update shortly the few, tiny Windows 8/8.1 fixes ... ?

Actually, ObjectDock is one of the last docks wich is currently still under development and updated (okay, every few years at least; before it stops working at all  ... -.- ) besides maybe the Nexus dock. And also it's one of the last feature rich docks at all. Sales must be really worse if they thread it like this even when they nearly have no competitors left ...

I won't just start to speak about suggestions by the users, besides bugfixes.

If anyone is interrested in what bugs i found, i can do a quick list and description. Maybe someone knows the one or another solution to them. But i gave up on reporting them officially for the reasons mentioned above.

Just my humble opinion and just the facts as they are (at least for me). Anyone having more luck yet? Probably we should begin a Kickstarter campaign to collect donations for the support for our paid products? Okay, that was a mean one i gues ... No harm meant.

TheDude23112
Reply #36 Saturday, April 26, 2014 10:13 AM

So, when are we going to see an update, Stardock?    

 

 

Fuzzy Logic
Reply #37 Saturday, April 26, 2014 10:39 AM

I use Object Dock all the time. It's the best way to access my frequently used shortcuts.

The start menu thing doesn't work - I deleted it - but the other shortcuts are fine.

Wizard1956
Reply #38 Saturday, April 26, 2014 11:05 AM

ObjectDock holds a special place in my Stardock customer history.

My first exposure to Stardock software was the free version of ObjectDock.  It drew me into the trial and purchase of WindowBlinds. From there I was hooked so the logical thing to do was purchase Object Desktop,  I went to the paid version of ObjectDock 1.9 (and eventually v.2.0)  I'm a regular subscriber to ODNT now. I can't imagine ever having a PC without something from Stardock running on it and I'd like to include OD again. I don't expect all of it to be perfect or work with every OS down the road but I do want to see the value  of my purchase and consider it money well spent when I see updates and/or ongoing development of new products.

 ObjectDock can be just as useful now, if not more so, than it ever was and yet it seems to have  fallen off the planet. Something as widely used and appreciated as OD is should be on the leading edge, not sitting on the back burner for years. It can lead to further sales,or leave a bad impression on first time users, depending on how it runs on any given PC. I hang out in the forums enough to have read years of bug reports and have experienced many of the same. If the long standing issues showed signs of being addressed, myself and I think many others would gladly pay for version 3.0 if it ever sees the light of day. (The Duke Nukem of Docks) 

 Fix the bugs and take my money......please.

-TiM-
Reply #39 Saturday, April 26, 2014 11:33 AM

Wizard1956

ObjectDock holds a special place in my Stardock customer history.

My first exposure to Stardock software was the free version of ObjectDock.  It drew me into the trial and purchase of WindowBlinds. From there I was hooked so the logical thing to do was purchase Object Desktop,  I went to the paid version of ObjectDock 1.9 (and eventually v.2.0)  I'm a regular subscriber to ODNT now. I can't imagine ever having a PC without something from Stardock running on it and I'd like to include OD again. I don't expect all of it to be perfect or work with every OS down the road but I do want to see the value  of my purchase and consider it money well spent when I see updates and/or ongoing development of new products.

 ObjectDock can be just as useful now, if not more so, than it ever was and yet it seems to have  fallen off the planet. Something as widely used and appreciated as OD is should be on the leading edge, not sitting on the back burner for years. It can lead to further sales,or leave a bad impression on first time users, depending on how it runs on any given PC. I hang out in the forums enough to have read years of bug reports and have experienced many of the same. If the long standing issues showed signs of being addressed, myself and I think many others would gladly pay for version 3.0 if it ever sees the light of day. (The Duke Nukem of Docks) 

 Fix the bugs and take my money......please.

 

Very well spoken!

c242
Reply #40 Saturday, April 26, 2014 1:51 PM


Hello everybody,

i'm new to the forums but a long time customer to Stardock. Since i was thinking about opening a thread like this on my own, i took the chance since c242 already did so.

I'm also worried about the same thing in the end. My story or experiences in a few sentences would be something like this:

01. I found a bug in ObjectDock (actually i found several by now)

02. I report it to the support guys

03. I receive an answer that most likely just tells me that the product is still supported and that i also send i a log from their support tool they link to

04. I do as asked

05. They tell me that they can reproduce the bug but that there is no fix for it and that it is reported to the developers

That's it – literally!

Once every know and then i add an complaint about why they do tell me there is support but when i try to use it, it ends in nothing more like "we reported it". The answer every time is "we do support, we gather bug reports, we deliver them to the developers and there is no more information we have for you". At least they should have a better information policy – i always thought just the support of the german companies over here i such bad. Or sad.

The real sad thing is, as i know that Stardock is not such a big company and that they have other products and other users awaiting help, this has happened before. That was in times before the Impulse disaster, when nearly the same situation occured and we waited years – until Windows 8.1 forced an update due to several incompatibilities – before something happened. Strangely, every other of my Stardock products is updated several times in between. But surely Start8 or WindowBlinds do sell better, aren't they? Funny enough, there are still bugs from back then that aren't fixed until today! And how long do we wait now since the last update shortly the few, tiny Windows 8/8.1 fixes ... ?

Actually, ObjectDock is one of the last docks wich is currently still under development and updated (okay, every few years at least; before it stops working at all  ... -.- ) besides maybe the Nexus dock. And also it's one of the last feature rich docks at all. Sales must be really worse if they thread it like this even when they nearly have no competitors left ...

I won't just start to speak about suggestions by the users, besides bugfixes.

If anyone is interrested in what bugs i found, i can do a quick list and description. Maybe someone knows the one or another solution to them. But i gave up on reporting them officially for the reasons mentioned above.

Just my humble opinion and just the facts as they are (at least for me). Anyone having more luck yet? Probably we should begin a Kickstarter campaign to collect donations for the support for our paid products? Okay, that was a mean one i gues ... No harm meant.

 

This expresses all I ever intended to write about the Stardock Experience.

Please login to comment and/or vote for this skin.

Welcome Guest! Please take the time to register with us.
There are many great features available to you once you register, including:

  • Richer content, access to many features that are disabled for guests like commenting on the forums and downloading skins.
  • Access to a great community, with a massive database of many, many areas of interest.
  • Access to contests & subscription offers like exclusive emails.
  • It's simple, and FREE!



web-wc01