What you suggest would not be possible without considerable refactoring
of the modules with native code, since the Java module system does not
allow modules to be split across jars.
-- Kevin
On 8/27/2018 12:02 PM, Sam Carlberg wrote:
It would be moving the platform-independent classes (ie th
It would be moving the platform-independent classes (ie the public API)
into the empty jars, leaving the platform-specific classes and binaries
where they are in the platform JARs. The service loader mechanism seems
suitable for tying the APi and platform modules together at runtime.
I don't think
>From Scene doc: "The scene graph detects dynamic node changes which affect
layout (such as a change in size or content) and calls requestLayout(),
which marks that branch as needing layout so that on the next pulse, a
top-down layout pass is executed on that branch by invoking layout() on
that bra
Why not do the necessary stuff on the next layout-pass?
Tom
On 27.08.18 09:48, Zsolt Kúti wrote:
> Thank you for the idea, I'll explore it.
>
> On Sun, Aug 26, 2018 at 5:16 PM Michael Paus wrote:
>
>> One possible solution for this would be to use an AnimationTimer.
>> Maintain a dirty state s
Thank you for the idea, I'll explore it.
On Sun, Aug 26, 2018 at 5:16 PM Michael Paus wrote:
> One possible solution for this would be to use an AnimationTimer.
> Maintain a dirty state somewhere and check that when the AnimationTimer
> gets called for the next pulse.
>
> Am 26.08.18 um 16:59 sc
