Hi again Lingocoder,
I may have forgotten to specify what corresponds to “JavaFx violate which lacks openness in places”.
Many JavaFx methods are declared as “final” which already limits the inheritance needed for customization.
But also a number of internal object constructions are not facing outward.
For example, instead of making a public method of construction available, the object is directly instantiated in a private method to an attribute that is also private. All often in a package hidden by the JPMS.
So, since I want total control of rendering and behavior of my graphics components, I have to “violate” the protections set up by JavaFX using java.lang.reflect.
But this is only possible if my IDE agrees to compile ;0).
Best Regards.
----- Mail original -----