Closed jbsarrodie closed 2 years ago
The null check works, but I was interested in why it was null. I've committed a change to master
that ensures the locale is never null and that a custom default locale (if specified on the command line) is added to the combo box.
You can delete your branch if you like. :-)
The null check works, but I was interested in why it was null. I've committed a change to
master
that ensures the locale is never null and that a custom default locale (if specified on the command line) is added to the combo box.
I was sure there was a better fix than mine. Thank you !
You can delete your branch if you like. :-)
Done ;-)
Fixed in Archi 4.10
Hi,
I've found a bug or edge case. I usually run Archi with a custom language pack for all sort of reasons (by adding
-nl myorgname
inArchi.ini
). This language pack being a custom one, there is no matching locale in the jasper report dialog. When running the report the first time everything is fine and the report is created, but it no more work if you run the report a second time: the jasperreport dialog doesn't even appear and a stack trace is logged (see below).It seems that checking for null before calling
fComboLocale.setSelection(...)
inExportJasperReportsWizardPage2#createControl
fixes it. I'm commiting a fix.stack trace: