This Bugzilla instance is a read-only archive of historic NetBeans bug reports. To report a bug in NetBeans please follow the project's instructions for reporting issues.

Bug 18077 - Unable to use Form module with WindowsLookAndFeel
Summary: Unable to use Form module with WindowsLookAndFeel
Status: CLOSED FIXED
Alias: None
Product: guibuilder
Classification: Unclassified
Component: Code (show other bugs)
Version: 3.x
Hardware: PC Windows ME/2000
: P3 blocker (vote)
Assignee: Tomas Pavek
URL:
Keywords:
: 18583 (view as bug list)
Depends on:
Blocks:
 
Reported: 2001-11-26 09:41 UTC by Jiri Mzourek
Modified: 2003-06-30 18:32 UTC (History)
2 users (show)

See Also:
Issue Type: DEFECT
Exception Reporter:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Jiri Mzourek 2001-11-26 09:41:35 UTC
When you start NetBeans on JDK1.4rc (W2k) in WindowsLookAndFeel it's impossible
to run Form Editor.
Comment 1 Marian Mirilovic 2001-11-26 12:41:06 UTC
It seems like JDK_1.4 / Windows 2000 issue. I try it on my Solaris and
it works fine.
If you try to set MetalLookAndFeel it works fine too.
Comment 2 Jan Chalupa 2001-11-27 12:38:06 UTC
Target milestone -> 3.3.1.
Comment 3 Tomas Pavek 2001-12-03 13:50:03 UTC
This looks like a bug in WindowsLookAndFeel. There's a NPE:

java.lang.NullPointerException
at com.sun.java.swing.plaf.windows.WindowsLookAndFeel$DesktopProperty.
<init>(WindowsLookAndFeel.java:1472)
at com.sun.java.swing.plaf.windows.WindowsLookAndFeel.initComponentDef
aults(WindowsLookAndFeel.java:398)
at javax.swing.plaf.basic.BasicLookAndFeel.getDefaults(BasicLookAndFee
l.java:80)

There is workaround - after runide ui switch:
  -ui com.sun.java.swing.plaf.windows.WindowsLookAndFeel
add also:
  -J-Dnetbeans.form.use_idelaf=true
Comment 4 Jiri Mzourek 2001-12-03 13:55:25 UTC
It would be good to add this information into FAQs and ReleaseNotes.
Comment 5 Tomas Pavek 2001-12-04 15:30:27 UTC
Actually it looks like it is not a bug in WindowsLookAndFeel. I can 
avoid the NPE, however I'm not sure quite about all consequencies so 
I suggest not to fix this in 3.3.0 (for which the mentioned 
workaround should be used).
Comment 6 Tomas Pavek 2001-12-04 16:42:03 UTC
Fixed in trunk and 3.3.1.
Comment 7 Tomas Pavek 2001-12-05 09:19:09 UTC
Þ
Comment 8 Marian Mirilovic 2001-12-12 10:31:10 UTC
verified in [nb_release33](200112120331)
Comment 9 Marian Mirilovic 2001-12-13 08:32:54 UTC
*** Issue 18583 has been marked as a duplicate of this issue. ***
Comment 10 Quality Engineering 2003-06-30 18:32:58 UTC
Resolved for 3.3.x or earlier, no new info since then -> closing.