On Thu Dec 29 2011 Sam Steingold wrote: > > * Roland Winkler <jvax...@tah.bet> [2011-12-29 10:54:29 -0600]: > > > > I am still confused. Why is the current behavior not appropriate for > > your needs? If BBDB detects that you have an auto-save-file that is > > newer than bbdb-file, why is it not OK to save it and then go on? > > when you are editing a file, would you like to be asked to save it every > few minutes? > > auto-save exists so that I can save when I am ready to save (note that > "/ c" is reset after each save!) not whenever I am about to hit space.
Could it be a better solution to check if an auto-save file already exists when BBDB is about to create a new one so that there would be two auto-save files? -- Oops, that doesn't work either! BBDB will try to create the auto-save file if the db has already be modified. So that's too late. I want to think about this once more, what can be a better order of things. Roland ------------------------------------------------------------------------------ Ridiculously easy VDI. With Citrix VDI-in-a-Box, you don't need a complex infrastructure or vast IT resources to deliver seamless, secure access to virtual desktops. With this all-in-one solution, easily deploy virtual desktops for less than the cost of PCs and save 60% on VDI infrastructure costs. Try it free! http://p.sf.net/sfu/Citrix-VDIinabox _______________________________________________ bbdb-info@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/bbdb-info BBDB Home Page: http://bbdb.sourceforge.net/
