SCRIPTS ALL GONE!!!
Thursday, October 6, 2005 by RomanDA | Discussion: DesktopX
I have been working on it for about 1-2hrs I think i have have saved the desktop.
I'm cleaning up the WORKING code, trying to make some functions to make it cleaner.
BOOM DX SHUTS DOWN... no warning no nothing, just GONE...
I figure, OK, let me load DX back up..
I say NO the the message that asks me if i want to just forget what i was working on, and it loads up DX.
YEAH!! all my objects are there, just like they were..
I right click on the master object, click "EDIT SCRIPT"
WTF!!!! Where is my script, there is NOTHING in there, its all gone!!
WHAT THE HELL IS GOING ON!!
Where is my script? Where did it go?
Where is the dump file of the script?
What deleted it?
Who decided nuking my script was the only way to fix an ERROR?
I'm so sick right now i want to beat this pc into the wall.
It was WORKING!! I didn't even hit the SAVE/APPLY button in my script, i was just moving some things around.
BAM GONE
Does someone at Stardock know what the h causes this?
and how in the world am i going to get my 2 hrs of work back?
HELP!!!
Reply #2 Thursday, October 6, 2005 9:13 AM
Reply #3 Thursday, October 6, 2005 9:20 AM
For future reference, emailing [email protected] is the best approach to resolving any issues you might be having and is the #1 line of communication to the developers.
We apologize for the inconvenience this issue has caused you.
-Mike
[Stardock Support]
Reply #5 Thursday, October 6, 2005 9:29 AM
Reply #6 Thursday, October 6, 2005 9:30 AM
Reply #8 Thursday, October 6, 2005 10:46 AM
I have a theory about why this happens - It seems to happen when there are quite a few objects in the theme, and DX does an auto-save (in the background), if you save the desktop explicitly and it happens to be during the auto-save, which takes longer with lots of objects, then wham!
I once permanently lost a theme I was working on this way. Also, I think there is an issue with programatically changing transparency in multiple objects. I've had things go south on me multiple times when trying that.
I've talked to Alberto about the auto-save issue and requested he make an option to turn it off. He said he would, but so far...haven't seen it.
Reply #9 Thursday, October 6, 2005 11:20 AM
Reply #10 Thursday, October 6, 2005 11:31 AM
We should try to determine what the common elements are when DX builder crashes. What other software was running? What action directly preceded the crash?
Reply #11 Thursday, October 6, 2005 11:35 AM
I now export object each time I make more than few lines, and keep backup of previous save too. Basically I have object on desktop, and exported object obj.dxpack and oldobj.dxpack.
Reply #12 Thursday, October 6, 2005 11:44 AM
Reply #13 Thursday, October 6, 2005 11:47 AM

Reply #14 Saturday, October 8, 2005 8:13 AM
Reply #15 Saturday, October 8, 2005 9:43 AM
Reply #16 Saturday, October 8, 2005 2:07 PM
Barring actually figuring out what is happening it would be nice to have easier methods of ensuring you've got a backup. If scripts could be saved as txt files from the editor, that would make it easy to at least have it backed up. And the export process itself could be more user friendly (what's up with the full path in the final box, leaving me about 4 spaces to type a name for a file that probabluy has a 6 character extension to begin with?). OK, that's another subject, I guess.
Reply #17 Saturday, October 8, 2005 2:50 PM
| What is Keepsafe? Anyone have an URL to it? |
It's part of Think Desk. You'll find it in SDC.
Reply #18 Saturday, October 8, 2005 6:35 PM
4 hours worth of work totally lost. Not to happy. Even worse because of that fact that DX is so darn shaky to begin with. The slightest problem with a script brings the whole thing crashing down on your head. That should'nt h appen no matter how messed up a script it, it shoudln't take down the entire VM as well.
Reply #19 Saturday, October 8, 2005 6:59 PM
Reply #20 Sunday, October 9, 2005 12:14 AM
For instance, I have had problems occur several times when making a change to a number of objects, by bringing up the properties for each one that needs the change, making the change in each, but not applying until all are done, then apply the changes to each. If I apply as fast as I can (as fast as DX returns control), eventually, after maybe 5 or 6 applies, it will crash. I've learned to apply a couple, wait a bit, apply a couple more, etc. I think this relates to applying in the middle of auto-save.
I have no way to really verify this, I know, but something is going on.
I also want to say re jvandebeck's post: It is not my experience that DX is that shaky. I routinely have errors in my scripts that are caught by the system with no problems. I fix them and continue.
Please login to comment and/or vote for this skin.
Welcome Guest! Please take the time to register with us.
There are many great features available to you once you register, including:
- Richer content, access to many features that are disabled for guests like commenting on the forums and downloading skins.
- Access to a great community, with a massive database of many, many areas of interest.
- Access to contests & subscription offers like exclusive emails.
- It's simple, and FREE!







Reply #1 Thursday, October 6, 2005 9:12 AM
This SUCKS!!!!! I have had this problem before, but I am doing some realy elaborate scripts for the GalCiv2 UI. I have reported this bug to Alberto, and he is looking in to it.
Hopefully we will have this fixed ASAP. For the moment i dont know of any fix. Becuse this error is very rare we are having a hard time tracking it down.
There is a round about way. Back up, often. I also run Keepsafe. witch backs up all my dxpacks everytime I save.
PS. you might look in the "Current Theme" for the scripts but it is probobly to late.
PS. This is not offical support. I just work at stardock. I will send this on to Support as well, incase there is something I dont know.