Hi all, I was thinking about how to implement the warning when there are autosave backups newer then the schematic itself. I have some issues I want to get comments about.... The main one is what should applications other than gschem do when they found an autosave backup. For example: what happens if an autosave backup is found when running gattrib, gnetlist, or whatever? should the user be warned and asked for an action? should they just exit (telling the user what's happening, of course) and let the user run gschem to correct the situation?
Currently, autosave is done in gschem, and when opening an schematic, there is a call to f_open, which is in libgeda. I'm considering two ways of implementing the warning: - First one: look for autosave backups in f_open, in libgeda. If backups are found, then call an application function, which should be coded in gschem, gattrib, gnetlist or whatever (like libgeda's arc_draw_func(), for example). This will allow each app to handle this situation independently, with or without GUI. I'm not sure about what to do in the other apps. I think the user shouldn't be allowed to run any other app in an schematic older than its autosave backup (this situation should be corrected before the user goes further in the process flow). - Another option would be to replace all the f_open calls in gschem by a call to another function, which looks for the autosave backup and ask the user if necessary. This way all the other apps won't change, but the user will only notice that there's an autosave backup when running gschem. What do you think? Regards, Carlos P.S.: Ales, could you tell more about the bug you found in the last FreeDog meeting?
