Jeremy Faden

This has been a bug for a long time, going back to at least v2025a_1. This is also a problem for floats, too, especially when completions would be nice: .../dev/bugs/sf/2899/demo2899.jy?f=<T> The above would fail because f is equal to "" and doesn't parse. Interestingly, DatumRange parameters, which I always knew could parse incorrectly, are handled nicely. Since this is an old bug, I will not delay the release.

This has been a bug for a long time, going back to at least v2025a_1. This is also a problem for floats, too, especially when completions would be nice: .../dev/bugs/sf/2899/demo2899.jy?f=<T> The above would fail because f is equal to "" and doesn't parse. Interestingly, DatumRange parameters, which I always knew could parse incorrectly, are handled nicely.

I think I know the change I made this past week that causes this, with the handling of the parameters.

This should also demo: i= getParam('i',50) print i and then call this script with i=5.0e1 .

Runtime error when entering parameters GUI and argument is not integer

ChatGPT showed that g.setStroke( BasicStroke(3) ) avoids reflection and works on later Java versions.

I've added code to embed the resolution in the property name. Now it should keep track for different display settings.

TODO was done. Code that would lead to run time errors when multiple tabs were added is fixed.