This is starting to bug me…
When I’m creating an event, and adding a source, maybe 3 windows deep, I go and hit the OK, but stupid me, the OK from the wrong window. This closes all the sub-windows and I loose the data that I have entered.
Is there a way to prevent this? A way to force you to close the windows in the correct order?
I could position each new window over the OK button, however I reposition the windows a lot when I want to check other entries,
1 Like
I did some digging into this and found a surprise. In most cases, only the references/attachment portion is lost when you close spawned windows in the wrong order. The actual new records are still created. (Which is still painful but a bit more recoverable.)
In most cases, I can stitch the pieces together. Just hit the Share icons (to select from existing records), sort so the newest records are on top and select that missing piece. Then the ‘OK’ from the right level commits the attachment.
If there are a LOT of records that weren’t attached, I’ll go into the View for the Object type, sort on newest. If the References column is showing, I can work the ones with no references.
Like I said, painful but workable.
This bug has been reported & acknowledged: 12008: Parents quietly abandon spawned newborn Objects
One of the things I try to do is as the windows open on top of another, I make sure the OK/Cancel buttons of the lower windows are not visible. Only the top window’s OK/Cancel is visible. As Gramps remembers the position of windows this works until I have to slide windows around on the monitor
This does not always prevent the selection of the wrong open window but more often than not it helps.
1 Like
I used to get this too. My solution (on Windows 10) is to use AutoHotkey, in Gramps, to map enter to Cntl+O. Now I just hit enter enough times and the windows close in the correct order.
David Lynch
Although there’s another bug related to Ctrl+O & data entry.
It is a Schrodinger’s Cat bug.
If you have typed into a text field but have not ‘commited’ the field (by tabbing to or clicking on another field) then Gramps will be badly confused if it uses that field as a basis for any calculation. At that point, the field is both populated and unpopulated.
As a concrete example while you are roughing-in a family. You just added a father or child (the surname would’ve been pre-populated and the given name field is active by default) then you type the given name ‘John’ but hit Ctrl+O. Since Gramps tries to match the first word of the given name against the statistical genders for that name, Gramps becomes confused.
Gramps knows there is probably something in the field but cannot look inside to discover the name. But it HAS to check that name because it exists. But it doesn’t exist because it hasn’t been created.
Error… error… Norman, coordinate!
This topic was automatically closed 30 days after the last reply. New replies are no longer allowed.