jorge my roommate just did a reinstall of windows and finally got to installing and running xtreme again. he went to add a new folder tab to workshelf and it used the name he wanted, but showed the contents in the folder tab to the right of it. i went in and deleted the new tab, recreated it and got the same thing. regardless of using insert new tab or add new tab it does the same thing. i tried it twice more with the same results. he went ahead and uninstalled xtreme and removed the registry keys and reinstalled. while he was doing that i made a new folder tab on my shelf and it does the same thing. after his reinstall he no change.

both running win 7 64 bit
the current release of winstep xtreme

There's a bug in the tab dialog of v12.2 that always sets folder tabs to C:\. You must create the new folder tab from the Contents tab of the Shelf Properties dialog instead.

jorge thanks for the quick reply as always, and the temporary workaround. but like i said above the new tabs created by rightclicking the shelf don't just set to c:\. if i add one to the left of "downloads"(a folder tab) and then mouse over it it will show the contents of the downloads tab. now if i rightclick on or to the left of any other type of tab and inert/add a new tab then the new tab will default to c:\.

jorge from what you posted i get the impression you have known about this for awhile. if that is the case you should of posted the fact. after all it's a bug in the major feature of the shelf.

Yes, the existence of this bug was pointed out the *very next day* after the official release. Had someone spotted it the day before, it would have been fixed in time for the official release.

Anyway, there have already been two or three posts about this, you probably missed them. It's a bad bug, but the good news is that a work-around does exist.

v12.2 was such a monster release that a bug or two going un-spotted was almost inevitable.

winstep wroe:


you care to link to he threads / post here? i'm not seeing them.

Here is one.

ok yeah i did see that. for some reason it just didn't click when i did, but still you should of created a thread of your own considering the nature of the bug. i'll assume oversight.