RightClick with WindowBlinds Skins Isn't Accurate

from Stardock Forums
Hello,

I loaded RightClick, but for some reason the RightClick window interface and the right-click menus themselves look quite odd. The text is cut off half-way in the interface. Also, in the right-click menus, if I choose to use the current WindowBlinds skin, the font seems to be the "System" font instead of the font that was specified in the skin. The icons and the text don't seem to be aligned correctly to the skin. This makes the menu look very scrappy... take a look:



(I added the red boxes to highlight the errors)

What would be the cause of this problem?

Thanks,
Electo
13,824 views 21 replies
Reply #1 from Stardock Forums Top
By the way, that is the OldRepublic skin, if that's any help, even though I've tried several skins and they all have the same scrappy look.

Electo
Reply #2 from WinCustomize Forums Top
You didn't specify if you were using Vista or XP.

The RightClick program no longer functions correctly on XP after the last 2 updates.

After the first update to make RC Vista compatible you could still import a windowblind skin. But...all of the skins had the same strange Italics font which was hard to see.

The last update caused the program to no longer import from any windowblind. Ive checked with several others and even in WB 6 RightClick no longer imports any wb skin. If you look in the RightClick Editor skin list window the skin will appear there but is blank...no text is displayed at all. The only skins that work are the installed skins in the skin folder of RC. Which is all I use anyway. But the program is supposed to import the windowblind.

I assume all is working in Vista so thats why its been left this way.

This is what all imported skins look like in menu editor now. When you try to Rightclick on your desktop you get nothing..no menu displayed when selecting "Use windowblind skin "



If you open the folder in RC Skin folder ( see below ) the folder holding the ' current windowblind skin " If you open ini pad of the skin your trying to import you will see the font listed on ini pad is all in symbols and unreadable on XP.



Anyway...after last update there was a drastic drop in RC skin downloads. Im sure it was because the majority of the users that updated lost their entire RC Menus in the process. The update never specified in SDC that you must leave RightClick program running during update. If you closed program you lost all your menu configurations which is time consuming to set up again.

I have mentioned these problems before.
CursorFX - Customize your Windows cursor
Reply #3 from Stardock Forums Top
Oh, sorry. I do use Windows XP. So I guess that would be the problem then. I bought ObjectDesktop just several days ago, so I didn't get to buy the XP compatible version. That's pretty disappointing...

So you suggest just making a new RightClick skin to correspond my WindowBlinds skins, instead of using the built-in function that doesn't quite work in XP?

Thanks for the advice,
Electo
Reply #4 from WinCustomize Forums Top
The last update caused the program to no longer import from any windowblind. Ive checked with several others and even in WB 6 RightClick no longer imports any wb skin.


I assume all is working in Vista so thats why its been left this way.
End of quote



Thanks for the info Fairy~. Exactly the same problem exists in Vista (64bit here). I always thought it was just me, and I actually had a go on it today.

I uninstalled using the ODN-Zapper, rebooted, run a registry cleaner to remove everything related to RightClick, rebooted, reinstalled from SDC and still it doesn't import WB-skins.

Have you already opened a Ticket at SD-Support for this problem or are they already aware of it?.
Reply #5 from WinCustomize Forums Top
Oh, sorry. I do use Windows XP. So I guess that would be the problem then. I bought ObjectDesktop just several days ago, so I didn't get to buy the XP compatible version. That's pretty disappointing...

So you suggest just making a new RightClick skin to correspond my WindowBlinds skins, instead of using the built-in function that doesn't quite work in XP?

Thanks for the advice,
Electo
End of quote


Have you tried any of the skins that come with the RightClick program ?
They should work fine - or go to RC gallery and download some of the pre-made skins ( unzip to the RightClick skin folder.

See if those skins work ok first...most of the problems have been with the importing from windowblinds.

There isnt an XP version or a Vista version. They are trying to make one version suitable for all. Im not sure if the vista version has no problems at this point.
Reply #6 from WinCustomize Forums Top
Thanks for the info Fairy~. Exactly the same problem exists in Vista (64bit here). I always thought it was just me, and I actually had a go on it today.

I uninstalled using the ODN-Zapper, rebooted, run a registry cleaner to remove everything related to RightClick, rebooted, reinstalled from SDC and still it doesn't import WB-skins.

Have you already opened a Ticket at SD-Support for this problem or are they already aware of it?.
End of quote


Thanks aufisch - that answered my question. And no I didnt open a ticket - I had mentioned this on several threads but I received no response so I gave up. I have trouble even getting forum to load anymore unless I come here at odd hours ( its 2 am )
Perhaps you can direct them to this thread..im not sure they are aware of this or not.

Reply #7 from WinCustomize Forums Top
Perhaps you can direct them to this thread..im not sure they are aware of this or not.
End of quote


Will do :)
Reply #8 from WinCustomize Forums Top
Will do
End of quote


See..it took me a few hours to get back to respond to you. Im not sure why forum will not always load at certain times but..that is life .

Hopefully there will be a next update. I know I can roll back to the version before the update that was to make this Vista compatible.

One thing I also forgot to mention ...another bug that might seem minor but is quite annoying..

Since RC was updated I can no longer use CursorXp.

I disable CursorXp for now because if you put your RightClick menu up and put cursor near the menu your cursor changes to the " Busy " or " Working in background " state.

Before the RC update your cursor remained in the normal state. This might not bother most people but it depends on what cursor you use. I see enough Hourglasses as it is ...I like my cursor to stay normal.
Reply #9 from WinCustomize Forums Top
I disable CursorXp for now because if you put your RightClick menu up and put cursor near the menu your cursor changes to the " Busy " or " Working in background " state.
End of quote


I don't see that on my system, but I have seen it mentioned elsewhere on the forums.
Reply #10 from WinCustomize Forums Top
I don't see that on my system, but I have seen it mentioned elsewhere on the forums.
End of quote


Ok , that must be just an XP bug , at least we narrowed down which bugs go where.

I miss a lot these days not getting forum to load. I hadn't seen it mentioned but I did check with several XP users that confirmed same bug after update. Im sure its not a problem for most but if you make RC skins when you do a preview you like to use a cursor to show mouseover. The cursor just didnt look right at that point.
Reply #11 from WinCustomize Forums Top
After the first update to make RC Vista compatible you could still import a windowblind skin. But...all of the skins had the same strange Italics font which was hard to see.
End of quote


I don't think that was an issue on Vista either, at least I didn't notice it. It might have been that they used a standard font which didn't occur in XP.

Anyway, I just launched a ticked with Support explaining both the WB-import and the CursorXP bug, and I provided them with a link to this thread.

I guess I will hear from them by either Monday-evening or Tuesday (Central Europe time). I will keep you updated. :)
Reply #12 from Stardock Forums Top
Have you tried any of the skins that come with the RightClick program ?
They should work fine - or go to RC gallery and download some of the pre-made skins ( unzip to the RightClick skin folder.

See if those skins work ok first...most of the problems have been with the importing from windowblinds.

There isnt an XP version or a Vista version. They are trying to make one version suitable for all. Im not sure if the vista version has no problems at this point.
End of quote


Yeah, the RightClick skins work perfectly. It's just the import from WindowBlinds that doesn't work very well. Thanks for the info. Just hope that the next update has better functionality.

Electo
Reply #13 from WinCustomize Forums Top
if you put your RightClick menu up and put cursor near the menu your cursor changes to the " Busy " or " Working in background " state.
End of quote


Same here, Fairyy~

I, also, finally gave up on RightClick importing WB skins correctly and just make them manually to match the WB I happen to be using at the time.

Hopefully, some Stardock people will take notice and fix what they broke?  :LOL: 
Reply #14 from WinCustomize Forums Top
Same issue with Objectbar.  So very sad.

Jeff is aware of both issues but I believe is focusing on other apps.  I may give him a poke about this later.  :)
Reply #15 from WinCustomize Forums Top
This is the reason I make my own RightClick skins. Give it a go, they are not that difficult ;)
Reply #16 from WinCustomize Forums Top
This is the reason I make my own RightClick skins. Give it a go, they are not that difficult
End of quote


I prefer to use my own also. But the program is suppose to import the windowblind and it doesn't. And there has been a drastic decrease in downloads of RightClick skins since the update which Im sure is because most cant figure out what is wrong and they think they stuffed up the download so they just delete it and forget it. Those of us that use this program like it..plus it is for sale as a stand alone application.

It should at least work, somewhat...
Reply #17 from WinCustomize Forums Top
It should at least work, somewhat...
End of quote


Doesn't seem to be any kind of priority at all with RC does there...  :NOTSURE: 
Reply #18 from WinCustomize Forums Top
This is the reason I make my own RightClick skins. Give it a go, they are not that difficult
End of quote


If only I weren't so hopelessly lazy...... :p
Reply #19 from WinCustomize Forums Top

If Jeff is aware of the problems then there's little to add. He'll get to a fix when he's given the opportunity. It's not the answer you want to hear, but it is an answer.

RC isn't being given the priority people would like, it's a very important app for Vista users. The reality is there's a lot of development work going on right now and folks at Stardock are busy. The occasional nudge does help though ;)

If only I weren't so hopelessly lazy......
End of quote

You know I don't believe that... ;)

Reply #20 from WinCustomize Forums Top
RC isn't being given the priority people would like, it's a very important app for Vista users. The reality is there's a lot of development work going on right now and folks at Stardock are busy. The occasional nudge does help though
End of quote


We all realize that they are working on 100's of things at once. But like you..I rely on this application. I'm used to it and I cant function without it. I hate to see the decrease in downloads in the RC skin gallery. Its a warning that most are losing interest in a program that may look simple and insignificant but is one of the best ways to access all your ' stuff' with a simple RightClick.

All this program needs is to have png support and a way to save configurations so people do not lose their menus. And of course, to import the windowblind skins again.



Reply #21 from WinCustomize Forums Top
I have just (un)-successfully restored to the previous version 1.24c, or at least I tried to.

At first I tried a direct restore, but that didn't work. Then I tried to uninstall, reboot and restore, but that didn't work either. No matter what I did, that darn version 1.24d just didn't want to go away (or rather kept on coming back).

So I got frustrated and kept on uninstalling, restoring, uninstalling, restoring..... until suddenly SDC claimed that it needed to reboot in order to uninstall. After the reboot I restored again version 1.24c but I got an error log.

I now have version 1.24 and three quarter installed. The error log clearly shows me restoring from 1.24c, but SDC stills shows 1.24d. WB import still didn't work, but at least it changed to a "neutral"-looking skin.

I then tried to restore to 1.24b (that was the version that didn't handle transparency on the flyouts). That went similar; now it showed 1.24c installed, but I had clearly the version with the transparency issues running. Strange thing there; WB import didn't work either!

I know for sure that the two previous version were capable of importing WB skins and I am at an absolute loss as to why restoring a previous version shouldn't fix this problem. :NOTSURE:

You know I don't believe that...
End of quote


OK I admit, I lack the talent... :LOL: