Read All !!! Stupid Save Function

[ianion]

 Dont make the same mistake as i.
-Edit your macropump file
-Edit your macropump file
-Test your macropump file
...repeat this 300 x
-Close Mach3 VB Script editor
-Make new macro
-Open Mach3 VB Script editor ( The file is not saved yet, its new blank file )
-Save
-?
-?
-Piiip
The new blank macro file has a name macropump.m1s
-?
-?
All 6 months work is gone, Great
Dont make the same mistake.

[BR549]

Been there done that one as well,(;-) It does not hurt near  as bad after about the 3rd time you do it.

(;-) TP

[ger21]

I lost my macros about 3 times while working on my screen. Now I edit in Wordpad, or at least save a copy with a .txt extension for backup.

[poppabear]

For what ever it is worth........  The work around I found for this, is when I save my VB editor work, I only use the "Save As" button, and write or Over Write my last file, each time. It will ask you if you want to do this each time, but at least it Does save it.

scott

[rrc1962]

As well as using save as, I also save everything I enter in VB editor in the separate text file. 

[wvancura]

Been there too. Been burned a couple of times. Perhaps it needs to either auto-load the macro, or not remember the name. As you say always "save as"

The other thing I would like is for it to have its own directory pointer. It shares the one from 'Load G-code' which is not even close to my macro directory.
 
The editor could add line feeds to make it more compatible with notepad. (Nice that WORD will put them back in.)

It does recognize "else if" but does not highlight it like a true command

Also if you test it and it has an operator input, you can't stop it without a break-point.

Always make a backup copy. Always. Always.

Thanks,
Bill

[ianion]

Thanks to all for sugeriments.
Now i have two backups of macropump.
And ALWAYS save with Save As.