If you click only once, you get the system cursor. If he's getting no cursor, there'd seem to be a problem with the file. User should state which cursor is his favorite, so others can test for problems.
srdiamond
Sinter by Essorant. The wallpaper is "Purple Passion" by Richard Moehler for contrast with Sinter.
Just to make a record in case anyone else gets this problem - The source of the problem was a conflict with CodeSectors DirectFolders. Turning off DF for Windowblinds solves the problem. It was not necessary to turn it off for anything else.
No. I don't even know how to do that. Are you saying that StyleXP removes something that WB 5.5 needs, although the native Windows XP (Luna) ard Classic appearances work fine? Even though Windowblinds 5.5 itself works fine, except for the problem with its own interface?
Adjusting window size would be nice, but I would not complain about its absence. That's not my problem. Using a utility called DM2 (freeware)to expand the window failed to resolved the problem. And if the window were merely too small, I could at least access the settings that are inaccessible. The window appears normally after I install or clean reinstall Windowblinds 5.5. After I reboot a second time, something goes wrong, some file is corrupted or some file conflicts with something el
Can the user expand the Configuration Window in the usual Windows fashion, by dragging edges - or by any other means. On my initial installation, the size is OK, but on the next reboot and thereafter, it contracts to maybe one-half its proper size. There is no way to reach the controls, although of course there are workarounds, such as the "Advanced" window. Can you suggest either how the window size can be altered or what could cause this contraction? Subsequently, I used a u
Even if someone chose not to user Windowblinds skins, WB 5's wallpaper changeover would be worth product's price. It produces near instantaneous changes, while the Windows XP mechanism using the Display control panel and the StyleXP mechanism, which seems to depend on the Windows mechanism. The Windowblinds 5 wallpaper function also lets the user access all the locations where wallpaper is stored, unlike the Windows mechanism that accesses only one loc
How come it doesn't compress the saved files?
With WB 5 (beta 11) installed and Visual Mind 8 (Business Edition) NOT excluded, opening and/or closing the NotePane View:Note Pane after first doing some work in the diagram crashes Visual Mind. ( http://www.visual-mind.com )
Super Wizop, I really had no reason to visit Stardock Central after I had been told that I would not be able to download what I needed. I'm a licensed user of WB 4 and WB 5, and I was responsible for bringing two separate conflicts between WB and third party programs to Neil's attention, one of these a longstanding conflict. So what you're saying is that it would be be OK, if I were unable to use these corrections to WB immediately, becau
In a MS Style skin that I made WB5-compatible with Skin Studio Standard, there's an anomaly in the 'OK' buttons. This skin uses buttons that sometimes change colors when "pressed," the colors being blue, green, and yellow/orange. But the OK button is supposed to be yellow/orange. But when transformed using Skin Studio and applied with WB5, the orange color in the OK button drifts to blue and then back again, repeatedly, each drift taking only a few sec
Neil, You did a great job of correcting this problem. But I would be interested in knowing whether the issue resided in WB or in the tree component. In other words, did you correct a mistake in WB, or did you compensate for a mistake in UR?
I have heard that registered WB users can also use SDC to download the beta builds of WB, though I have never tried that myself so I may be wrong. You are quite right. So I got the downloads--the improvements are impressive. The UR problem wasn't a WB5 problem; it was long standing. You have resolve
Are you an Object Desktop subscriber? If not, you'll have no access to beta/pre-release versions. With all due respect, Super Wizop, you are wrong . With considerable effort, I was able to discover not only the nature of this mysterious entity, 'Stardock Central,' but also that I am
Citizen srdiamond ....the fault here lies with you....as stated, you have not set SDC to show 'pre-release versions'...which currently shows a .010 ver available 5.00[b].010 to be precise. Compatibility issues are constantly addressed, hence all those zeros and ones in the version number. Remember, every d
Regarding the Clipmate issue, Neil posted on December 2, "This is now resolved. Additionally I have set it so clipmates menus are ignored by WB as clipmate is self skinned & its menus look wrong with WB skinning them as well. "There will be a 5.01 update either later today, or most likely early next week." This was most encouraging, but now almost two months have passed, and each time I check, the current version remains 5.0.00.0 (or however that goes). And the Clipmate is
Mention is made of downloading the latest build of WB 5. Yet I find that the download remains static, version 5.0.0.0. Since there is talk about of a later version, something like version 5.0 (b), I'm wondering, is there a public beta of later builds that I've missed?
I guess I'm a gambler; I took the "risk." Actually, I had intended to alter only a single not WB5-compatible single skin, and it wasn't a WB 5 one--bearing as it did a copyright date 2003. The best year for skins! But once I got into it, I modified others, for one other element besides page color. Someone just reported you could resolve an incompatibility with the free form datbase UltraRecall (Kinook Software) by means of a small
My bad. I assumed that Skin Studio was an expensive designer's suite. A post in another forum alerted me to the fact that certain changes one could make in the free program actually are as simple as changing the registry. I'm not that cheap or anything; I just didn't really want to spend a couple hundred dollars and learn a new program in order to change a single skin' page coloration. Could you answer two more questions? 1) To change the
I'm licensed to use WB5, and I am currently using it. I am not a subscriber to Object Desktop; I don't have skin studio. Thanks for your help, but this becomes too complicated. I'll just have to reset it each time I restart, or perhaps just this as an opportunity to get acquainted with macro programs. I would guess it's easy to define a macro that would reset certain controls each restart. On the other hand, I find that a compe
Is that a hard thing to do, requiring a special application or is it akin to editing the Windows registry? If it's reasonbaly simple, do you have a link where the procedure is explained?
If you set the page coloration in the standard Windows Display Properties dialog (Advanced/More Advanced Properties), Windowblinds will allow this change to occur. However, the page coloration reverts to that set by the WB theme on the next restart. Is there a way to maintain this change through restarts of the computer. PS Sorry, I sent this to the wrong location previously.
If you set the page coloration in the standard Windows Display Properties dialog (Advanced/More Advanced Properties), Windowblinds will allow this change to occur. However, the page coloration reverts to that set by the WB theme on the next restart. Is there a way to maintain this change through restarts of the computer.
If you set the page coloration in the standard Windows Display Properties dialog (Advanced/More Advanced Properties), Windowblinds will allow this change to occur. However, the page coloration reverts to that set by the WB theme on the next restart. Is there a way to maintain this change through restarts of the computer.
Thank you for your responsiveness. I have to say I'm very pleasantly surprised. For some reason I've assumed that compatibility problems were deeply rooted.Consequently, I have never reported them, except for now, because this is a beta. So I'm now wondering if long-standing compatibility issues could be resolved, if only you knew about them. Here's one that existed in Windowblinds 4 and continues. Most--but not all-schemes are incompatibl