DesktopX and Widget problem

All Core Widgets no longer function

~ Up until the last update of desktopX in Stardock Central I had no problem..Now All Core Widgets no longer function. The core picture frame ( That I used daily ) will not accept any picture no matter what size. only the left and top half of frame is viewable. The Core clock will appear in its large mode but cannot be resized. The To do list cant be found and the weather object same...I have uninstalled DesktopX-Reinstalled...still cant use them. So I uninstalled again, deleted all folders , all widgets, lost all previos downloaded objects and widgets . scan disked, defragged, ran 5 virus scans, ad-aware---then re-installed desktopX again. Then I went and redownloaded the same widgets. But no matter what I do, they wont function. And the core picture frame even though its deleted and reinstalled, still " remembers " the same setting and is only 1/8th of the picture and 2 sides are still missing. I've run out of ideas. The last DesktopX was an Alpha version.Anyone have this problem and or a solution ?
6,342 views 8 replies
Reply #1 Top
I am using the released version 2.40.035 on WinXP Home SP2 and there is something funky with using widgets. I tried adni18's True Weather widget and the only way I could get it to work was to run DX itself and import the widget. Trying to run it just as a widget and it seemed "stuck"...not being able to change any settings.
Reply #2 Top
I had same problems with widgets,then I found one way :first import widgets to objects to your desktop,after that export them back to widgets !I got them to work by that system!
Reply #3 Top
I think one of the problems with the latest alpha version of dx is in the Object_OnScriptEnter phase of scripts. I am by no means certain as the problems I have been experiencing have been quite random and do not seem to occur every single time - but as far as I can tell this is where some of the problems lie.

This means that any script which initialises variables and starts timers and so on from within the Object_OnScriptEnter subroutine will produce unpredictable results. Sometimes it seems to initialise fine and other times it does not.

Fairry - I would suggest either uninstalling the alpha and re-installing the last official release, or wait until future betas and release versions become available. Other than that I have no solution and must sit back twiddling my proverbials until a new stable version is released - very frustrating as I have some projects 99% completed, several updates and many more "pending" (ie: in my head) just waiting for a stable platform.
Reply #4 Top
I was working with Alberto this morning on the IRC channel...I believe he has a clearer understanding of what we are seeing with the Alpha release. Until there is a new release, you may want to roll-back to 2.4.035.

Wicked.
Reply #5 Top
https://www.wincustomize.com/Forums.aspx?ForumID=144&AID=60262#481993
Reply #6 Top
~Thankyou all for being very helpful. Its odd that not everyone is having this problem. I wish I had seen your thread before SD. At least I would have realized it wasn't my computor. I will try the import widget to object>export widget back to widget...if that fails , I'll remain widgetless for now.
Reply #7 Top
I'm widgetless. ...sounds funny. Am waiting for a fix. ... also sounds funny
Reply #8 Top
~We remain widgetless...the import/export/import resulted in...
Lets see, when I imported it, the picture frame was only half there, so I exported back to widget folder but came up with script error. The end result was when I click on just the widget now , i get the whole picture..but the widget frame is now completely missing.

But...at least I still have the little fishy swimming up and down.