Bug? JavaObject and Null parameter

[stevel05]

While tracking down issues with my previous post to do with UnmodifiableListSet I solved the issue by creating a library. The final library was so simple I went back to try to find out why it wouldn't work with a JavaObject.

The Object in question UnmodifiableListSet has two toArray methods (see docs here) one requires an Object[] array and the other requires no parameter.

Once I found the documentation I got it working with JavaObject by passing an Object array of size 0.

The method that requires no parameter always gives a null pointer error (although it works perfectly in the java library).

Is it possible that the JavaObject lib is confusing the two methods and passing null to the method that requires an object array? Or have I totally missed the mark?

Example app attached.

 

[agraham]

It looks like a bug in the JavaObject private method arrangeAndCheckMatch(). It only occurs when passing a Null parameter to an overloaded method. I'm sure that Erel will see it immediately when he looks at the code.

 

[Erel]

Fixed for the next update:

 

[agraham]

This is probably a stupid question but rather than waste my time displaying my stupidity to only myself while trying to figure it out I'll ask instead!

In this demo by what mechanism does the Tag (UserData) property of a Node get set from the name of the StyleClass? Is it a JavaFX thing?

 

[stevel05]

It's done in the subroutine SLUtils.ExtractTags(MainForm.RootPane). I was going to use the style field, but realized that I may want to set colours for some objects, then I realized that a dummy StyleClass won't do any harm as you have to specifically refer to it for it to do anything.

 

[agraham]

Thanks Steve. I didn't think to look in SLUtils - I thought it would be more arcane than that! I like the thought about using StyleClass.