SCRIPTS ALL GONE!!!
Thursday, October 6, 2005 by RomanDA | Discussion: DesktopX
Here I am working on a new object, its been going great.
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!!!
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!!!
 |
|
Page 2 of 2 | |
|
|---|
Cyberworld
Reply #22 Tuesday, October 11, 2005 3:34 PM
Ditto,also it would make it easier to edit scripts outside DX and then import them back in. That would be a way for DX not to crash so often when scripts are involved.
Reply #22 Tuesday, October 11, 2005 3:34 PM
| If scripts could be saved as txt files from the editor, that would make it easy to at least have it backed up |
Ditto,also it would make it easier to edit scripts outside DX and then import them back in. That would be a way for DX not to crash so often when scripts are involved.
_Martin_
Reply #23 Friday, October 21, 2005 7:07 AM
Reply #23 Friday, October 21, 2005 7:07 AM
I had this a while ago and reported it. Things with DX are generally more stable but this does happen occassionally. From memory, when I reported this, I seem to remember I thought the issue was caused by several scripts that interact with each other all running at the same time following a script change.
thomassen
Reply #24 Friday, October 21, 2005 12:58 PM
Reply #24 Friday, October 21, 2005 12:58 PM
Hmm.... I'm pretty sure I've had this issue even with just one script running... but I wouldn't bet my life on it...
XX
Reply #25 Friday, October 21, 2005 2:35 PM
Reply #25 Friday, October 21, 2005 2:35 PM
Yeah. last time it happened, it was a single centralized script. My linear object was scriptless after crashing, wiping out my entire changes to it. Newer version is much delayed because of that.
I suspect it happens somehow when it repackages the object after the changes is made to it. Maybe at one point, it has a new script file it's supposed to repack into object, replacing the old script. If it deletes old script and was about to move new script in and it crashes, that may be the reason the scripts go poof.
Word, for example, uses a temp file to save changes, if you crashes, then opens same word file again, it will check for that temp file to see if it crashes while file was being edited. It may be good idea for DesktopX.
I suspect it happens somehow when it repackages the object after the changes is made to it. Maybe at one point, it has a new script file it's supposed to repack into object, replacing the old script. If it deletes old script and was about to move new script in and it crashes, that may be the reason the scripts go poof.
Word, for example, uses a temp file to save changes, if you crashes, then opens same word file again, it will check for that temp file to see if it crashes while file was being edited. It may be good idea for DesktopX.
CerebroJD
Reply #26 Friday, October 21, 2005 4:26 PM
Reply #26 Friday, October 21, 2005 4:26 PM
I think you might be right, XX, but then why does it load the 'default' script instead of just a blank script? 
MountainDragon
Reply #27 Friday, October 21, 2005 4:48 PM
Probably because the data saying there was a script is separate from the actual script data. Like when you press New Script, it flips a switch saying "This object has a script", and the editor loads the default "new" script if no other is found.
Okay, so I'm tripping, but that could be how it works.
Reply #27 Friday, October 21, 2005 4:48 PM
| think you might be right, XX, but then why does it load the 'default' script instead of just a blank script? |
Probably because the data saying there was a script is separate from the actual script data. Like when you press New Script, it flips a switch saying "This object has a script", and the editor loads the default "new" script if no other is found.
Okay, so I'm tripping, but that could be how it works.
os1smith
Reply #29 Friday, October 21, 2005 10:42 PM
Reply #29 Friday, October 21, 2005 10:42 PM
HAHAHA...welcome to programming 101..now you know..all through college they kept telling me back up often, test each module, do your flow charts, do and keep records of hard copies of coding..lol..did I listen..hell no...hand this program I was working on, for 4 hours hadn't done one save, no flow chart, just did it off the top of my head on the computer. Heard some thurder, my finger was 3 inches from the save button...BAM lights flickered, computer shut down, four hours of my life wasted...but I learned, I save so often now probably going to wear out my HD. You can take solice in knowing there is not programmer alive that hasn't lost some code, nature of the beast!!!
Skarny
Reply #30 Wednesday, November 2, 2005 5:01 AM
Reply #30 Wednesday, November 2, 2005 5:01 AM
I'm sure this has been reported before. I know I've at least bi*ched about it a fair bit in IRC.
I second the autosave theory. I find even after making NO changes to an object, just bringing up the properties of an object, DX goes into an autosave fit, and whatever is going wrong happen then, right as its probably saving those script files out, resulting in blanks (and I dont mean completly blank, most occasions Ive had the default OnEnter and OnExit scripts within the object).
I second also loading and saving scripts to external files via the script editor as an option, which means the scripts can be outputted somewhere before the changes have been made to the actual object thus avoiding the crash during apply thing. I don't think allowing external scripts to be referenced directly (ie. being run as the actual script for the object) is a good idea, as it would probably be at risk from the same bug/problem.
When requests for 'wanted' features for the Desktopx3.0 launch was a post a while back I mentioned these things.
Here's hoping
I second the autosave theory. I find even after making NO changes to an object, just bringing up the properties of an object, DX goes into an autosave fit, and whatever is going wrong happen then, right as its probably saving those script files out, resulting in blanks (and I dont mean completly blank, most occasions Ive had the default OnEnter and OnExit scripts within the object).
I second also loading and saving scripts to external files via the script editor as an option, which means the scripts can be outputted somewhere before the changes have been made to the actual object thus avoiding the crash during apply thing. I don't think allowing external scripts to be referenced directly (ie. being run as the actual script for the object) is a good idea, as it would probably be at risk from the same bug/problem.
When requests for 'wanted' features for the Desktopx3.0 launch was a post a while back I mentioned these things.
Here's hoping
RomanDA
Reply #31 Friday, November 4, 2005 1:47 PM
Reply #31 Friday, November 4, 2005 1:47 PM
It seemed to crash on me when i was adding a "NEW" object or changing an existing object. IE: I had a background object, and everything was working perfect, and i opened the porperties on the bac object to change the PNG file i was using, as soon as i click the PNG file name in the dialog box, it all crashed, lost all the scripts, just like before. Only this time, I had made a NOTEPAD copy of my main script. IE: select all/copy /paste it into notepage.
I tried again, but it still didnt work. I ended up having to reboot, and start dx again, load a BLANK setup then create a new object, and add the PNG file. Then i had to add back all my scripts. WHAT A ROYAL PAIN IN THE......
DX PRO needs to have this fixed. I see my email was received on 10/6, its not 11/04 and i never received anything to tell me they got the email, nor any response on if there is a fix, or even to ask me any more questions.
Im working on a new DX widget, and i basiclly have to make multiple copies of the desktop, and the save the scripts into notepad just to be sure i dont waste time for nothing.
DX Development, Any ideas? Any news?
I tried again, but it still didnt work. I ended up having to reboot, and start dx again, load a BLANK setup then create a new object, and add the PNG file. Then i had to add back all my scripts. WHAT A ROYAL PAIN IN THE......
DX PRO needs to have this fixed. I see my email was received on 10/6, its not 11/04 and i never received anything to tell me they got the email, nor any response on if there is a fix, or even to ask me any more questions.
Im working on a new DX widget, and i basiclly have to make multiple copies of the desktop, and the save the scripts into notepad just to be sure i dont waste time for nothing.
DX Development, Any ideas? Any news?
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!
|
|
Page 2 of 2 | |
|
|---|
Reply #21 Sunday, October 9, 2005 12:27 AM
Yes, that would be a nice feature to be able to load and save files from the script editor it self. I know it's not hard to copy and paste, but it is extra steps. And if the script editr had load and save script feature it could also include templates of snippets you often use.