Ok, read some other stuff and found out problem. Gotta get into "builder", then edit stuff. Glad that's fixed!
Maggot
I am unable to look at object properties in Desktop X 3.0. When I click on DesktopX Configure, there are no areas for wallpaper selection anymore either, nor can I right click an object within a theme and view its properties any more. No choice to save as, save or any of the other options either. What happened? Do I have to turn something on or something????
I'd recommend you do what I had to do. Take your themes you wanna keep and put them somewhere else on you system. Then uninstall WB. When it says it's done, go to explorer where the WB directory was supposed to be and make sure it's gone. If it's not, delete it, then reboot or shutdown and restart (better). Go to Stardock again and do a MANUAL install of WB latest version (in other words do not use the Automatic Install window which will pop up as soon as SDC is online. Same thing happened
Make sure at the bottom of Stardock Central window that you have view betas checked on. I think!?!
Vetto, I have SP2 installed as well as OD suite of apps. Appears all working. Did see a problem using Tiggz's Widget "K-Display" and Sysmetrix. When midnight comes, my Sysmetrix stopped and sent me a "runtime error 97, can't call object when object .......". Happened two days in a row, so stopped using Sysmetrix and sent email to Xymantix about it. I think it's a SP2 problem/caused error as it never happened in SP1. Secondly, used K-Display. At midnight tonight, the DAY OF THE WEEK displa
I've always experienced your Cursor XP problem, even with SP1. As long as it changes back to your selected Cursor XP theme after login, things are okay. It's Microsoft XP problem. Only runs "system" cursors prior to Starting Windows/Login. At least that's been my experience with both XP Home and XP Pro and SP1 and SP2. <A HREF="https://www.wincustomize.com/index.asp?Cmd=full&NewsID=
Ok EVERYBODY, or at least anybody who cares. If you're having problems with the "new" 2.20.024, try this, it worked for me. First, move any themes you wanna keep somewhere else on your 'puter. Then, go to Stardock Central and UNINSTALL your current version of DX, no matter what it is I guess. After the uninstall is complete, reboot your machine. After that, go back to Stardock Central, and INSTALL (really a re-install) DX 2.20.024 (file is 11.84mb). After it says it's installed, it will ask
Kris Kwilas. Forgot, will forward you the install\dx file after I try to run DX and my themes again. Also, forgot to mention that after installing DX2.20.024 the SECOND time, I rebooted. Ok, off to give it a try and will be forwarding you email and the attached file ifn necessary. If no word from me, then the uninstall, reboot, re-install, reboot worked I guess. Time will tell, eh?
Kris Kwilas, a.k.a. NakorDon't know if problem is solved for sure but, as a precautionary step, I uninstalled DX, rebooted, then re-installed 2.20.024. Noticed on the reinstall that the download was about 1.5 mb larger than the first time when it did the auto upgrade via stardock central control tray. Dunno if that means anything. Anyway, haven't had a chance to see if the themes now work or not but, wanted to let you know what I've done so far. Also, looked at the install\dx file and it SAY
Desktop X 2.20.024! Upgraded automatically using my Stardock Central Tray. After it installed, I get an error message stating that the theme I'm trying to load was "BUILT WITH A NEWER VERSION"!!! What the hell? I had 2.19q (003)and IT had problems but, this is unbelievable!!! 2.20 won't load my previous themes correctly!!!! Guess 2.20.024 really ISN'T the RELEASE version I'M PAYING FOR!!!! They need to FIX this!!!! <img src="http://images.stardock.com/images/smiles/hot.gif" border=0 AL
Jafo, thank you for the info. I hope he is just updating and will return it. I think it's preety neet!!! Has to be one of my favorites to include Antares, Universe Metal, Copper Deck II, and Airlock! Crystal is close behind those......Thanks again <img src="http://images.stardock.com/images/smiles/sb.gif" border=0 ALIGN
Was just wondering if anyone knew why the DX theme "HITMAN" by 'fiveballs' (I believe that's who the author was) was removed?? <img src="http://images.stardock.com/images/smiles/sb.gif" border=0 ALIGN="absmiddle" ALT="Powered by
Just wanted to update. Thanks to Kris Kwilas, WB 4.29i[rc]002 now available and it fixes my problems. Working on the bootskin 1.04/1.03 problems still though.
Night Train, thanks for your input. No biggie here either, just frustrating. This version (h) acting same as (g) in other words, new iteration, nothing fixed! Have sent email to Stardock with my specifics but as it's the weekend, don't expect to hear anything for a couple days....thanks anyway for your info. It's good to know I'm not alone, bad to know for WB users...... <A HREF="https://
Just got the newest WB (4.29h[rc]002). Still have problem when editing a skin in Skin Studio. Changes are made but, the skin does not repaint when applied, until, I click on the show/hide system tray icons button, then the changes kind of "morph" into existence. Additionally, using the Window Blinds Config window to change a skin, sometimes the change is "morphed" completely but, sometimes, a skin will NOT change/morph entirely, until, again, I hit the systray hide/show icons button. Also, d
Koasati, thanks for the info, that clarifies it a lot....
Sput, thanks for the info and I DO get the morphing effect. Like it better than redrawing all the portions of a skin. It DOES NOT work when I try to change a skin using Windows/Display Properties/Appearance tab though! Oh well, like I said b 4, Microsoft stuff always reluctant to change....... <img src="http://images.sta
Sput, thanks and I take no exception to the "paying for things....". I guess I didn't state it the best way but, frustration will do that to ya. As for the "morphing" effect, I'm not real sure I even understand what that means but, when I changed the skin using the WB config, I did notice that the newly assigned skin just kind of all changed at once, unlike previously when you could tell it was re-painting the parts, so I guess maybe that's the "morphing" effect. If so, I can understand why it
Hippy, Sput, Koasati.....Have a bit more info on this. I just changed a WB skin but this time I used the WB config window vice the display properties/appearance method which I usually use. The skin changed with no draw problems! Yay! I did notice that my cursorxp cursor did not change. Also, I went back to the default bootskin, rebooted the computer and DID NOT get a Black Screen of Death/system halt! So, looks like WB problem only occurs when using the display properties/appearance tab an
Hippy and Sput, thanks again for the input. Hippy, I didn't know about the bootskin problem (I have version 1.03 I think, anyway, latest iteration of it). Will revert to the default WinXP boot and see what happens. Additionally, I emailed Stardock and got a response from JAKE and sent a follow-up to him with my system specifics. Waitin on an answer. I can understand the bootskin thingie but, it doesn't explain why WB is not repainting changed skins, either seperately or during use with Skin
Sput and Koasati, thanks for commenting. I know what you're saying but, in this particular case, doesn't the [rc] mean "release candidate"?? If so, my feeling is that it ought to work correctly and should be checked out BEFORE releasing it to folks to "experiment" with. It just seems like changes are rapidly occuring and not being qc'd too well before releasing. Anyways, I hope this gets some attention and is rectified as quickly as the problems with DX and WB not too long ago! I've been a
I dunno about morphing but, with the latest iteration of WB4 (4.29f[rc]002), when I change WB skins, the new skin doesn't show until I mouseover portions of a window!! Additionally, after changing a WB skin, then rebooting my system, I get a BLACK SCREEN and system halts right after bootskin runs. When I restart a second time, I get a message saying Windows experienced a major problem and halted the system to protect my files. Following the 25 second delay, I just let windows restart and wa l
Koasati, thanks for ur input but, there IS a problem with Window Blinds latest release. System halts after bootskin runs. Second restart and all's well! I didn't have this problem with the WB iteration prior to this latest release, so.......I figure if I'm paying for software, then it better work properly, EVERY TIME. Seems like with the last updates of Object Desktop programs, there have been more problems than additional capabilities. This is fine with freeware but, I think it's pretty sl
There appear to be several problems I need to address. First, there must be a problem with Stardock's servers. I cannot get discussion updates! Second, connecting to Wincustomize is taking forever (I'm a paid subscriber!). Third, believe the last iteration of Skin Studio is not coded correctly. Twice now I have used it to edit some Window Blinds. When I tell it to apply the changes, I lose my WB skin but, when I mouse over parts of the skin, they come back. Not only that but, when I reboo
Ok, the last DX update has indeed fixed my probs of previous posts. Thank you Stardock!