This is likely true, to a degree. The thing is, most people who customise their
controls do this at the skin level and retain the same behavior. This isn't
always true of course, but it generally is. For this reason the priority is on
getting the skins public first. Behaviors will come second, w
Am I seeing this right that this means that overriding/extending
existing controls in JDK9 will become real hard because we have no way
to get the already existing behavior and build upon it?
On 31.08.2015 10:06, Jonathan Giles wrote:
> That is correct. The feasibility of doing this in a JDK 9 up
That is correct. The feasibility of doing this in a JDK 9 update release is
another issue entirely, so the main point is that it will be at some point
after the first JDK 9 release, but no guarantees when.
-- Jonathan
Sent from a touch device. Please excuse my brevity.
On 31 August 2015 20:00:2
On 28.08.2015 00:41, Jonathan Giles wrote:
> ...but for two it doesn't feel right to release it without the behaviors
> themselves becoming public. I worried that without the behaviors being
> public that the InputMap was a bit of a 'map to nowhere'. My hope is
> that we can resolve this in an upda
