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 186584 - NullPointerException at org.netbeans.modules.javafx.composer.design.control.SceneControlPane.isFreeLayout
Summary: NullPointerException at org.netbeans.modules.javafx.composer.design.control.S...
Status: RESOLVED FIXED
Alias: None
Product: javafx
Classification: Unclassified
Component: Unsupported (show other bugs)
Version: 6.x
Hardware: All All
: P3 normal (vote)
Assignee: David Kaspar
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2010-05-24 08:35 UTC by Lukas Hasik
Modified: 2010-05-24 10:11 UTC (History)
0 users

See Also:
Issue Type: DEFECT
Exception Reporter: 170026

Attachments
stacktrace (5.50 KB, text/plain)
2010-05-24 08:35 UTC, Lukas Hasik 		Details
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description Lukas Hasik 2010-05-24 08:35:10 UTC 
Build: NetBeans IDE 6.9 RC1 (Build 201005202201)
VM: Java HotSpot(TM) 64-Bit Server VM, 14.3-b01-101, Java(TM) SE Runtime Environment, 1.6.0_17-b04-248-10M3025
OS: Mac OS X

User Comments:
lhasik: -add/remove tooltip




Stacktrace: 
java.lang.NullPointerException
   at org.netbeans.modules.javafx.composer.design.control.SceneControlPane.isFreeLayout(SceneControlPane.java:718)
   at org.netbeans.modules.javafx.composer.design.control.SceneControlPane$8.run(SceneControlPane.java:956)
   at org.netbeans.api.javafx.composer.kernel.ModelManager$3.run(ModelManager.java:226)
   at org.openide.util.Mutex.readAccess(Mutex.java:365)
   at org.netbeans.api.javafx.composer.kernel.ModelManager.readAccess(ModelManager.java:222)
   at org.netbeans.modules.javafx.composer.design.control.SceneControlPane.getMovementMatrix(SceneControlPane.java:924)
Comment 1 Lukas Hasik 2010-05-24 08:35:14 UTC 
Created attachment 99374 [details]
stacktrace
Comment 2 David Kaspar 2010-05-24 10:11:43 UTC 
The issue is caused by issue #561 and has been fixed in the latest build.