Zugg Software :: View topic

Newbie Joined: 05 Mar 2006 Posts: 8

I just had a terrible experience. I have been working for about 4 hours on fixing my targeting system. I got it to work. I tried to make a tweak, all of the sudden i see "System Access Violation". Program crashes. I figure fine, only to realize once i get back in that my carefulness to hit the "save" button after every change is only saving to memory, no file of any type. I would make a suggestion that, in some future release, you move to saving changes to a temporary file so that i don't have to worry about erronously making changes and losing all my work. Another is that ctrl+s should save to the file when the editor window has focus. I kind of understand why the "save" button doesn't save to a file, but I think that the save system should be more robust incase of situations like this.

Besides that (maybe a little bit more angry than it should have been given it says "Settings in memory" at the top of the screen.) great program and thanks for all the help to everyone.

Nick

GURU Joined: 26 Jul 2001 Posts: 1958 Location: Canada

When I`m actively coding like that I have found that:

#alarm savealarm *360 {#SAVE}

Works wonders. Especially when I do something really stupid and trigger loop or erronously try and fill a variable with 293872938 items etc :P

Wizard Joined: 25 Mar 2003 Posts: 1113 Location: USA

Alarms to save your work are okay if you don't make a mistake and then accidentally save it. ;)

Also, the little "Save" button for individual settings will just update that one setting in memory, true, but using File -> Save (from the Settings Editor, or Settings -> Save from the main window) will save all your settings to disc for you.