From: Doug B. <dou...@gm...> - 2010-12-14 12:25:41
|
On Tue, Dec 14, 2010 at 3:37 AM, Benny Malengier <ben...@gm...> wrote: > > > 2010/12/12 Doug Blank <dou...@gm...> >> >> After a few days of using trunk on some good data (I know, I know), >> and deciding to Backup, and selecting a different directory, I forgot >> that FileChooserDialog can go into an infinite loop, and lost* all of >> my changes. Then I did the same thing again in changing the default >> media path. >> >> I decided that "papercut" had to go. Googling, I couldn't find any >> hint of anyone else having that problem. So, I tried randomly mutating >> the FileChooserDialog and found something that apparently works, with >> no ill side-effects. I changed: >> >> action=gtk.FILE_CHOOSER_ACTION_CREATE_FOLDER, >> >> to >> >> action=gtk.FILE_CHOOSER_ACTION_SELECT_FOLDER, >> >> and that seems to work fine. It even has a button for creating new >> folders, which I suspect was the reason it was used in the first place >> [1]. >> >> I committed these changes to the these two dialogs; please let me know >> if you see any unintended consequences. >> >> -Doug >> >> [1] - >> http://gramps.svn.sourceforge.net/viewvc/gramps?view=revision&revision=9435 >> > > I suppose this can happen in branch32 too, so best do the patch there too. Good idea. Peter was the only one that had an issue, but I don't think that was related to the patch, and at least it didn't hang. If there are no other issues, I'll apply to gramps32. >> * I was able to recover all of my changes with a simple "db4.8_recover >> -c". Perhaps we can suggest that when a database is locked? Is there a >> way to do that programmatically? >> > > Dangerous to choose for the user, most of my cases the database is locked is > due to other reasons. Also, they need the db tools installed. It would be > nice if this crash can be detected, so as not to show a lock icon but a > repair or other icon. Yes, I didn't mean to imply doing it automatically, but rather asking to do it, or suggesting that the user should. > Did you really loose all your changes? All committed things before the crash > should be just fine. Was it not a repair button? Then the user already sees > a very extensive popup. No, I didn't loose a thing. But there was a good half an hour that I was furiously backing backups, and trying various things. I didn't notice if the "Repair Button" was available. Why doesn't bsddb commit these changes when we issue a commit? That's just crazy. -Doug > Benny > >> >> >> ------------------------------------------------------------------------------ >> Oracle to DB2 Conversion Guide: Learn learn about native support for >> PL/SQL, >> new data types, scalar functions, improved concurrency, built-in packages, >> OCI, SQL*Plus, data movement tools, best practices and more. >> http://p.sf.net/sfu/oracle-sfdev2dev >> _______________________________________________ >> Gramps-devel mailing list >> Gra...@li... >> https://lists.sourceforge.net/lists/listinfo/gramps-devel > > |