#12 Error messages during GEDCOM import not delivered

[Tom Morris]

Errors during GEDCOM import using the BKedit interface
cause an assertion error and the user never receives
the error message.

The message window that the error routine is trying to
write to isn't instantiated because the jLifelines UI
isn't active.

java.lang.AssertionError
at jLifelines.stdlib.utils.ASSERT(utils.java:72)
at
jLifelines.stdlib.GraphicSys.wprintf(GraphicSys.java:54)
at
jLifelines.gedlib.valgdcom.handle_err(valgdcom.java:588)
at
jLifelines.gedlib.valgdcom.add_othr_defn(valgdcom.java:344)
at
jLifelines.gedlib.valgdcom.validate_gedcom(valgdcom.java:161)
at
jLifelines.gedlib.Import.import_from_file_common(Import.java:95)
at
jLifelines.gedlib.Import.import_from_file(Import.java:70)
at
net.sourceforge.gdbi.main.jlifelines.BKAltGUI.runGedcomImport(BKAltGU
I.java:194)
at
net.sourceforge.gdbi.editor.bk.BKEditAction.real_actionPerformed(BKEd
itAction.java:111)
at
net.sourceforge.gdbi.editor.bk.BKEditAction.actionPerformed(BKEditAct
ion.java:74)
at
javax.swing.AbstractButton.fireActionPerformed(Unknown
Source)
at
javax.swing.AbstractButton$ForwardActionEvents.actionPerformed(Unknow
n Source)
at
javax.swing.DefaultButtonModel.fireActionPerformed(Unknown
Source)
at
javax.swing.DefaultButtonModel.setPressed(Unknown Source)
at javax.swing.AbstractButton.doClick(Unknown
Source)
at
javax.swing.plaf.basic.BasicMenuItemUI.doClick(Unknown
Source)
at
javax.swing.plaf.basic.BasicMenuItemUI$MouseInputHandler.mouseRelease
d(Unknown Source)
at java.awt.Component.processMouseEvent(Unknown
Source)
at java.awt.Component.processEvent(Unknown Source)
at java.awt.Container.processEvent(Unknown Source)
at java.awt.Component.dispatchEventImpl(Unknown
Source)
at java.awt.Container.dispatchEventImpl(Unknown
Source)
at java.awt.Component.dispatchEvent(Unknown Source)
at
java.awt.LightweightDispatcher.retargetMouseEvent(Unknown
Source)
at
java.awt.LightweightDispatcher.processMouseEvent(Unknown
Source)
at
java.awt.LightweightDispatcher.dispatchEvent(Unknown
Source)
at java.awt.Container.dispatchEventImpl(Unknown
Source)
at java.awt.Window.dispatchEventImpl(Unknown
Source)
at java.awt.Component.dispatchEvent(Unknown Source)
at java.awt.EventQueue.dispatchEvent(Unknown
Source)
at
java.awt.EventDispatchThread.pumpOneEventForHierarchy(Unknown
Source)

at
java.awt.EventDispatchThread.pumpEventsForHierarchy(Unknown
Source)
at
java.awt.EventDispatchThread.pumpEvents(Unknown Source)
at
java.awt.EventDispatchThread.pumpEvents(Unknown Source)
at java.awt.EventDispatchThread.run(Unknown Source)

[Daniel Kionka]

Logged In: YES
user_id=325184

This is an important bug, but I think I will leave it for the next
release. The real solution, as described in RFE 851634, is to
add a GEDCOM import to GDBI instead of using jLL's.