Details
Description
The Swing controller when used as a component throws this exception.
Exception in thread "Thread-5" java.lang.NullPointerException
at org.icepdf.ri.common.SwingController.savePrinterProperties(SwingController.java:2653)
at org.icepdf.ri.common.SwingController.initialisePrinting(SwingController.java:2599)
at org.icepdf.ri.common.SwingController.access$400(SwingController.java:103)
at org.icepdf.ri.common.SwingController$3.run(SwingController.java:2549)
at java.lang.Thread.run(Unknown Source)
There is a pretty simple work around but I would rather that the defautl SwingViewBuilder would create a new isntance of the properites manager or alternatively do a check for the null manager.
Exception in thread "Thread-5" java.lang.NullPointerException
at org.icepdf.ri.common.SwingController.savePrinterProperties(SwingController.java:2653)
at org.icepdf.ri.common.SwingController.initialisePrinting(SwingController.java:2599)
at org.icepdf.ri.common.SwingController.access$400(SwingController.java:103)
at org.icepdf.ri.common.SwingController$3.run(SwingController.java:2549)
at java.lang.Thread.run(Unknown Source)
There is a pretty simple work around but I would rather that the defautl SwingViewBuilder would create a new isntance of the properites manager or alternatively do a check for the null manager.
Activity
- All
- Comments
- History
- Activity
- Remote Attachments
- Subversion
The work around is sufficient for most people but I also added a null pointer check encase someone doesn't want to use the property Manger with the component.