Re: Matisse is throwing exception until I restart NetBeans
Tomas Pavek <[email protected]>
| Newsgroups | gmane.comp.java.netbeans.user-interface |
|---|---|
| Message-ID | <[email protected]> |
Witold Szczerba wrote: > 06-11-10, Tomas Pavek <[email protected]> napisał(a): >> [Please post reports like this rather to nbusers mailing list... Thanks] > > Well, I have to confess that sometimes I find it hard to decide which > mailing list to choose :/ You can post almost everything to nbusers - unless you are not a developer developing NetBeans or NetBeans platform based product. The nbui mailing list falls more to the second category. It is for: "People interested in the usability of the IDE and helping to improve it - discussions on the graphical appearance of the IDE, its key bindings, workflow issues ... Note this is not a support forum." > >> The exception you attached is probably caused by a bug in the GUI builder >> (would be worth reporting in IssueZilla), however it is caused but >> another exception - DataPicker component fails on instantiation >> (thus the layoutloading fails). >> When you compile the other form and reopen the WizytyForm form, a new >> classloader is used to load the classes - so new version of >> DataPicker class >> is loaded, but it probably interacts with the old version of the >> BasicDatePickerUI. If you restart, everything seems ok - when the >> class is loaded first time. > > You are right, I've removed this component and now there is no problem. > So it looks like the bug in GUI is that it doesn't catch the exception > that is thrown by DataPicker? > Probably I will look for another component (btw: why there is no > component like this in Swing... Spinner with date is not good enough. > I think it is planned for Java 7. But have you tried the SwingX component? There is also a JXDatePicker. https://swingx.dev.java.net/ - Tomas > >> Would be good to investigate why this happens... especially the >> CalendarPane.updateUI method - how it gets the UI delegate. >> >> - Tomas > > I'm afraid that might be too difficult for me as I have no idea how > Swing is working under the hood. Investigating that would stop me from > continuing my investigations in other areas I have to figure out, > starting from general Swing data-aware application architecture up to > JEE 5/JPA/DB/JAX-WS (maybe JSR-170/283 as well). :( > > Java developer life is not easy... but actually quite exciting :)