#261 Export of .xena files and NAA plugin

[Allan Cunliffe]

Testing Branch

Export will not work if you are running Xena without the NAA plugin and the Xena file was normalised with the NAA plugin.

This behaviour is expected, however, a message to the user might be helpful. At the moment I get a message saying:

Could not get output filename for some reason.

And in the console:

au.gov.naa.digipres.xena.kernel.XenaException: Could not get output filename for some reason.
at au.gov.naa.digipres.xena.kernel.normalise.NormaliserManager.getExportFilename(NormaliserManager.java:1181)
at au.gov.naa.digipres.xena.kernel.normalise.NormaliserManager.export(NormaliserManager.java:1143)
at au.gov.naa.digipres.xena.kernel.normalise.NormaliserManager.export(NormaliserManager.java:1115)
at au.gov.naa.digipres.xena.kernel.normalise.NormaliserManager.export(NormaliserManager.java:1071)
at au.gov.naa.digipres.xena.core.Xena.export(Xena.java:759)
at au.gov.naa.digipres.xena.viewer.NormalisedObjectViewDialog.exportXenaFile(NormalisedObjectViewDialog.java:292)
at au.gov.naa.digipres.xena.viewer.NormalisedObjectViewDialog.access$3(NormalisedObjectViewDialog.java:279)
at au.gov.naa.digipres.xena.viewer.NormalisedObjectViewDialog$2.actionPerformed(NormalisedObjectViewDialog.java:174)
at javax.swing.AbstractButton.fireActionPerformed(AbstractButton.java:1995)
at javax.swing.AbstractButton$Handler.actionPerformed(AbstractButton.java:2318)
at javax.swing.DefaultButtonModel.fireActionPerformed(DefaultButtonModel.java:387)
at javax.swing.DefaultButtonModel.setPressed(DefaultButtonModel.java:242)
at javax.swing.plaf.basic.BasicButtonListener.mouseReleased(BasicButtonListener.java:236)
at java.awt.Component.processMouseEvent(Component.java:6263)
at javax.swing.JComponent.processMouseEvent(JComponent.java:3267)
at java.awt.Component.processEvent(Component.java:6028)
at java.awt.Container.processEvent(Container.java:2041)
at java.awt.Component.dispatchEventImpl(Component.java:4630)
at java.awt.Container.dispatchEventImpl(Container.java:2099)
at java.awt.Component.dispatchEvent(Component.java:4460)
at java.awt.LightweightDispatcher.retargetMouseEvent(Container.java:4574)
at java.awt.LightweightDispatcher.processMouseEvent(Container.java:4238)
at java.awt.LightweightDispatcher.dispatchEvent(Container.java:4168)
at java.awt.Container.dispatchEventImpl(Container.java:2085)
at java.awt.Window.dispatchEventImpl(Window.java:2475)
at java.awt.Component.dispatchEvent(Component.java:4460)
at java.awt.EventQueue.dispatchEvent(EventQueue.java:599)
at java.awt.EventDispatchThread.pumpOneEventForFilters(EventDispatchThread.java:269)
at java.awt.EventDispatchThread.pumpEventsForFilter(EventDispatchThread.java:184)
at java.awt.EventDispatchThread.pumpEventsForHierarchy(EventDispatchThread.java:174)
at java.awt.EventDispatchThread.pumpEvents(EventDispatchThread.java:169)
at java.awt.EventDispatchThread.pumpEvents(EventDispatchThread.java:161)
at java.awt.EventDispatchThread.run(EventDispatchThread.java:122)

It would be good if the message alerted the user that the file was created with a version of Xena that was using the NAA plugin and to view the file, they will need to run Xena with the NAA plugin.