Will ObjectDock be continued or not ?

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

Successfully updated karma reason!

Chasbo

Join Date 01/2005

+853

Quoting WOM,

reply 26

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

Me too. 64bit Win7. No problems.

Successfully updated karma reason!

c242

Join Date 03/2001

+380

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

Successfully updated karma reason!

Uvah

Join Date 05/2006

+874

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

Successfully updated karma reason!

Quoting bodadog,

reply 22

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.

Successfully updated karma reason!

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

Successfully updated karma reason!

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.

Successfully updated karma reason!

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.

Successfully updated karma reason!

Quoting gevansmd,

reply 33

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.

Successfully updated karma reason!

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.

Successfully updated karma reason!

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

Successfully updated karma reason!

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.

Successfully updated karma reason!

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.

+2

Successfully updated karma reason!

Quoting Wizard1956,

reply 38

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!

Successfully updated karma reason!

c242

Join Date 03/2001

+380

Quoting -TiM-,

reply 35

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.

Successfully updated karma reason!

Quoting c242,

reply 40

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

Thanks c242!

However – and just to be clear – this is not meant as some "Stardock-bashing" or anything (even while it seems that nobody by now has seen it as such). I like the Stardock products a lot. I would not complain about something i don't care about. And in most other cases (at least those i also use like Start8, WindowBlinds and Fences), everything is fine (for me) so far. But the faulty one here seems to be still ObjectDock, as it ever was, as long as i use Stardock software.

And to be honest: i don't get it, really. -.- If they would at least tell us what the problem is! To less sales? Technically to complicated (come on; it's a dock and you guys are programmers, doing well with every other product i use), the all time favorite: "Microsoft is to be blamed" ? It could be even "no time because of higher priorities on other products" ... but for SO long again and again while other products are udpated sometimes as fast as one can report bugs!?

I would shake my head a little more in missunderstanding but at the end it will fall of thanks to this case ... However, how about using this thread as a "bug-collection thread" then to be more productive and helpful? If c242 agrees, of course (didn't mean to hijack you thread, man! ). Maybe we even can help each other out where Stardock doesn't care?

(Off-topic: Does anyone know is StarDOCK has some meaning? Was that their first product or such? Even sader, if. They even do docks for other companies, like the Dell dock, and don't care! Back then, with the Impulse struggles, i thought something else. I never wanted or used that way of distribution and in the end it failed. And support was, what was short at hand also – especially for ObjectDock, again! -.- Yet, then they had a good reason while trying to get rid of Impulse.)

Successfully updated karma reason!

Full of nonsenses........likes kids kept asking for attentions to disrupt what adult have been doing on the work.

Successfully updated karma reason!

Quoting Gaspershooters,

reply 42

Full of nonsenses........likes kids kept asking for attentions to disrupt what adult have been doing on the work.

The only "nonsense" in this thread (which IS a support thread) is your remark. Did you have anything relevant to the discussion to add? If not......

Successfully updated karma reason!

(1) The first time with a custom blind, it works correctly.

(2) The second and subsequent times it's invoked I get the partial menu.

(3) Every time with a standard Aero blind works correctly.

It does work correctly with non custom blinds every time as you can see, and the first time with a custom blind.

Successfully updated karma reason!

This post intentionally left blank.

Successfully updated karma reason!

Quoting Gaspershooters,

reply 42

Full of nonsenses........likes kids kept asking for attentions to disrupt what adult have been doing on the work.

Probably i would agree if we would ask for updates to a product that was released yesterday. But if you would have read all the posts, you should have understood the history of this special case – even Stardock has, they just say nothing at all. I also see several honorable, experienced and long time members of the board on this thread agreeing, so this cannot be as false as you put it, right? Asides that, Wizard1956 again has said everything important in quite fewer words than i could have done.

So let us ignore the "kids" and get back to topic, adults! (Some day this will mean trouble for me, hm? ^^) @gevansmd: As you describe your problem, it seems that it really is one of all the problems i found myself with WindowBlinds. However, are you maybe using some of this Aero tools for tuning transparency or theme patchers to allow customized themes? They often cause the same problems. Besides that, you are not using Start8 on your system (of course since you cannot on Windows 7 as far as the website here says), but it fixes several of this problems and also works in co-op with WindowBlinds and recognizes it is installed as synchronizes some options between the two applications.

So my guess would be, if you where on Windows 8 with Stat8, your problem most likely would dissappear by itself. Besides that, Start8 also draws the start menu somewhere else instead of its default position bottom left of the screen and directly above the task bar (wich is greatly annoying as you cannot change that, by the way) and it does so well. It also skins correctly. But i have found several WindowBlinds skins that cause errors especially with the start menu and especially when using transparency (and, yes, transparency is possible even on Windows 8 with WindowBlinds installed). Maybe somehing of this is helpfull to you? (Funny you are orientating your menu to the right side as you are most likely right-handed; thought that was just me with some menu set-ups. ^^)

Last guess would be asking some of the good sites that answer questions like www.askvg.com or www.howtogeek.com . The friendly guys over there are really good at what they do and normally answer as they can.

+1

Successfully updated karma reason!

See post #34

Successfully updated karma reason!

I read most post here but not everyone so I may be lacking a little info from other post. I will say that I am using Windows 8.1 64bit and use ObjectDock. I just did a test to determine if |I suffer from the same fate and added 2 different 64bit program shortcuts to the dock from Start 8. Both shortcuts worked fine. I also use the start menu docklet with no problem and I also use the system tray icon feature with no problem. I am not saying that there are no issues with Objectdock but it is strange that the issues are not consistent with every user. I have always used ObjectDock and was never a fan of Fences.

Successfully updated karma reason!

Quoting JuniorCrooks,

reply 48

I read most post here but not everyone so I may be lacking a little info from other post. I will say that I am using Windows 8.1 64bit and use ObjectDock. I just did a test to determine if |I suffer from the same fate and added 2 different 64bit program shortcuts to the dock from Start 8. Both shortcuts worked fine. I also use the start menu docklet with no problem and I also use the system tray icon feature with no problem. I am not saying that there are no issues with Objectdock but it is strange that the issues are not consistent with every user. I have always used ObjectDock and was never a fan of Fences.

I agree with that. I will try to figure out with c242 when he reponds to my offering for help but i'm also not affected by the mentioned x64-plattform bug myself. However, that means nothing in the end since it may be a bug simply not occuring on my systems as you put it right already. Most of the bugs i personally found on my systems weren't even mentioned on the forums at all (as far as i know) but support staff reproduced and reported them to the developers.

I guess the trick is to find out what is a bug and what is a local problem on someones system. Therefore i suggested using this thread as a self-helping group. I'm really experienced and may have the one or other solution found already or give some directions maybe – depends on what the problem is. As far as Stardock does nothing, that may be our best guess.

Successfully updated karma reason!

Right on Tim.

Successfully updated karma reason!