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.
netbeans-trunk-nightly-200909151512-javafx-full.zip Product Version = NetBeans IDE Dev (Build 200909151512) (#ebf350cbb86b) Operating System = Windows XP version 5.1 running on x86 Java; VM; Vendor = 1.6.0_15; Java HotSpot(TM) Client VM 14.1-b02; Sun Microsystems Inc. Steps to reproduce: - Copy the code to the editor: -------------------------------- var i = 3; var num = 3.0; var b = true; var c = "2".charAt(0); var byte:Byte = 1; var short:Short = 2; var long:Long = 3; var float:Float = 5.0; var double:Double = 10.0; var date = 3h; var str = "Hello!"; class A{} var a = A{}; var f = function(a:Number, b:String):Boolean { true }; var seqf = function(a:A[], b:String[]):Boolean[] { [] }; var seq = ["1", "2", "3" ]; -------------------------------- - Set breakpoints for the first and the last lines - Debug the project - Go to the variables window The Variables windows shows boolean, char, byte, short, long and double types instead of the JavaFX types: Boolean, Char, Byte, Short, Long, Double
Boolean, Char, Byte, Short, Long, Double are not JavaFX types only Integer, boolean and Number are. View fixed for JavaFX types only
See http://java.sun.com/javafx/1/tutorials/core/dataTypes ----------------------------------------------------------------------------------------------- Note: As of SDK 1.1, the language also contains numeric types that align with those found in the Java programming language. The full list of numeric types is therefore: Byte, Short, Number, Integer, Long, Float, Double, and Character. However, the advice given above still holds true: most programmers will only need Integer (or Number) for the scripts that they write. If you are coming to this language from a Java programming language background and have a task that absolutely requires one of the other types, just know that these additional types are now available to your scripts. -----------------------------------------------------------------------------------------------
The issue is much more deeper than it seems. The JavaFX is compiled directly do the Java virtual machine code and when the program is running the debugger has no information about the original script values. I'm moving this issue to NO68 because without deeper debugging information compiled into class files from javafxc compiler I'm unable to recognize what type of variable is the one in the virtual machine.
*** Bug 174193 has been marked as a duplicate of this bug. ***
as this bug is either caused by the fx compiler or it too complicated to fix it in 6.8 - > approved
There is no mapping available between original FX and Java types included in classfiles.
Fixed.
The separated issues are created: issue 188761 Double and Character types are not shown in FX style issue 187984 Variables window does not show function type in FX style