future of objectbar

from WinCustomize Forums
I read that stardock was planning a release of objectbar 2.0 on 2003. What happened to the project? has it been abandoned?
objectbar
776 views 4 replies
Reply #1 from Stardock Forums Top
The new beta was put up yesterday.
Reply #2 from WinCustomize Forums Top
Not to offend or anything, but have you seen the new beta? It seems no progress has been done since december, actually its worse since backgrounds are now all white, and the auto-hide bars don't want to seem to come back.

Stick with 1.65 for now, this beta is NOT ready for use yet.
DeskScapes - Bring your desktop background to life.
Reply #3 from Stardock Forums Top
Well without feedback from its users, don't count on it making much progress. It's working pretty well here.
Reply #4 from WinCustomize Forums Top
Quite right, my appologies. I am just frustrated as my object bar seems to have gotten worse since the last beta, the auto-hide is going slightly crazy (it will be fine, then stop activating until i hit the windows key), and the backgrounds have turned white (though sometimes the come back, then disappear again). I've posted an image here.
http://webpages.charter.net/samus42/WhiteObjectBar.jpg

I also left a lot of feedback in december, which I have reposted below with my comments on if anything has improved since then. I do realize that some of the bottom items are somewhat subjective, but judging from the newsgroup I'm not alone.

Please realize I'm not trying to be a troll or to put it bluntly a dick, I just love this program and want to see it really shine. I do realize my object bar theme might not have survived the transition from 1.65 to 1.99, but I haven't figured out how to fix it yet. Which means I won't be the only having problems. Anyway, as I stated in december, I'm willing to do anything to help, if you need my current theme, or need me to install some sort of debug feedback, I am quite willing. This is my #1 productive tool.

BTW, can we get an ObjectBar section of the forums? And are the newsgroups still read?

Here are my notes repeated from my december newsgroup posting with my current comments.
-Scott MacDonald

>This was found using my Developer theme on wincustomize. Though this is highly >critical, its only because I love this application and use it every day, and hey, its a >beta! And also, if I mention something not working correctly, I actually tried to fix >it (checking bar properties, expermenting with different options). So either it >doesn't work, it doesn't work under certain conditions, or its not nearly obvious at >all and that option needs to be re-thought.

>1) The working directory problem is still there. This absolutely must be fixed since >it breaks windows shortcut rules.
>To see the problem, create some random text file, then create a batch file in the same >directory that calls notepad for that
>file (i.e. notepad random.txt). I recommend putting a 'pause' in there as well so you >can see the working directory. Drag the >batch file to your bar, then click on it.
>
>The command prompt will show the working directory being the Object Bar bin directory.
>
>However, if instead of drag & drop, you add it through the theme editor, this will >work. Good, but then remove the shortcut from the object bar, move your bat & txt file >to a new directory, and drag it to the bar. Now you'll notice the command prompt
>uses the OLD working directory from when you set up the file through the editor. >Something is getting cached that shouldn't.
>If you're going to use object bar to launch things, the working directory problem MUST >be fixed. It has existed too long as it is.

Still a problem in the latest beta.


> 2) The icon tray sizing is acting very weird. I use bar that docks to the left part >of the screen for my task list & system tray. The system tray has always been at the >bottom. But all of a sudden the space used for the task list has snapped to
> only be as tall as the number of tasks shown, and the icon tray is now right below it >instead of the bottom left. Even though the resizing mouse cursor appears when I hover >over the seperator between the task list & system tray, I cannot resize
> it like I could in 1.6. It might have something to do with an 'Extra Space' item that >keeps getting put below the system tray, I remove it but it keeps coming back!

The resizing cursor no longer appears, and this is still broken.

> 3) The left bar has also widened without my asking it too, and I cannot shrink it >back.

I can't even grab it, when I click when the resize horizontal cursor appears if the bar is on autohide. I can grab it if I turn autohide off, but I cannot shrink it. Which means my bar width is at the mercy of the longest program currently being run.

> 4) It turns out I can't resize any group, even the items on my top bar will now allow >me to re-space them.

This is still true, even with the "Allow This Container To Be Resized" clicked.

>5) The properties context menu action for a bar is terrible. 2 of the items you can do >without launching the properties. So you go straight to Bar Name, which you probably >wont' change much, and always on top. Merge the Properties / Skin tab at least
>to make this worth going to as an option. Or remove the Menu Editor option and have >properties go straight to that since that is what the user will be messing with. Or >even put the stuff on the properties item on the same page as the Content tab at
>the bottom or something.

This is still true.

>6) Insert New Popup Menu Item needs to have its name changed to New Menu, or New Menu >Bar.

Still true, but subjective. This is a personal preference.

> 7) On the theme editor, for the Available Elements, when right clicking add a 'What's >This?' action that gives a brief description, or even a tooltip. While I know what >everything is, new users won't.

I still believe this.

>8) I understand while people are grumbling about removing the advanced editor. It >really makes it a pain to jump in and out of bars by double clicking on a popup menu >item (I still hate that name), and the hitting that button that appears well away
>from the list to go back to the parent. First, that back to parent button should be >right next to, or above Edit Submenu/configure. Putting it far away is very confusing.

Nothing appears to be different here. Again, subjective

>Second, the Edit Menu Title should be where the Bar To Edit: is. Make the Bar To Edit >a menu item between File and Help. (View Bar or something like that).

Still the same. Again, subjective

>You might think of widening the dialog and putting a 3rd list which could be a tree >view of the bars in the system. You're absoletely right in not wanting to see Docked >Bars and Floating Bars like the advanced editor shows. But you could easilly
>show a tree view, and if a bar is reused in multiple places, so be it, since i'm sure >your code is pointing to references of bars instead of copies of them So if you >change a shared bar in one area, the same changes are in their other places.
>
>Basically the navigation through the theme editor needs a lot of work. While I >understand the need to go to something more simple, at the same time you need to make >sure you don't slow down people like myself who create the themes and do a lot of
>editing over time. Currenting going through the bars is a pain.

Again, subjective, but looking at the newsgroups, people do not like the current editor, so you might want to try SOMETHING.

>9) Don't use the red exclamation mark for Various-Function Item. When I launched my >theme, I thought it was reporting errors!.

Red exclaimation mark still there.

>10) If you double click on an item in Available Elements to add it, then hit cancel on >the items configuration dialog, the item should not be added to the bar.

Well the cancel button has dissappeared, so I guess it isn't confusing anymore. Not sure it's right though.

>11) You need to be able to drag and drop Available Elements to the correct place on the >Active Elements list. Adding then using the arrows to move is a pain.

Still true.

>12) Need to drag and drop items within the Active Elements list.

Still true.

>13) Need to be able to multiselect ActiveElements and group.

Still true.

>14) Navigating directories through ObjectBar can still be slow (i.e. You have folder >shortcut on your bar/menuitem, show folder in a menu). I say can be slow, it isn't >always slow. I haven't figured out when it is or isn't yet. Probably some
>caching going on that speeds it up after initial slowness. Its never the initial >level, but 2 or 3 directories in it will usually pause for a little bit.
>

This is still a problem, though I think you've made progress. The My Docs folder works really quickly now, but my downloads directory link seems to take forever.