Schematic Recovery Bugs

Shifrin · 6 Jun 2005

Tom7777 wrote: Also if there is an empty schematic it will recover that too which i think is pointless, maybe you should make it so that at least 1 module/componant must be on the schematic to recover it.

Sounds like a sensible idea to me!

Shif.

infuzion · 7 Jun 2005

Tom7777 wrote: If you get a crash when the option is on and then double click and load a .OSM file it won't load it but will only load the recovered schematic.

Yep, I was getting frustated with this.

Also if there is an empty schematic it will recover that too which i think is pointless, maybe you should make it so that at least 1 module/componant must be on the schematic to recover it. Thanks

seems that when you open SM now, it actually opens a blank schematic automaticly. Handy for newbies, but an extra hassle if I don't want to write one from scratch every time.

Tom7777 · 7 Jun 2005

First off thanks guys for thinking that this is a good idea 🙂

seems that when you open SM now, it actually opens a blank schematic automaticly. Handy for newbies, but an extra hassle if I don't want to write one from scratch every time.

Secondly infuzion, this is becuase you have it set to Empty schematic, do the following -

Click Options - and under the startup tab select most recent schematic

infuzion · 8 Jun 2005

Tom7777 wrote: Click Options - and under the startup tab select most recent schematic

I can't: there is/was a bug in that if the most recient schematic crashes, I can never again run SM unless I go through 15 minutes re-installing/uninstalling. Actually, perhaps I could make a script to remove the most recient SM files in the regestry, but it's alot less pain just to open what I want when I want.

Besides, isn't that what "My Recient Documents" in the Windows Start menu for? 😉