You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Starting with javaFX 17-ea+11 I noticed that scrolling a StyledTextArea (from RichTextFX) no longer worked properly: when clicking the scroll bar elements, the text scrolls for the first couple of clicks and then entirely stop responding to clicks on these elements.
It does respond to using the mouse wheel of keyboard arrows however.
broken_scrolling.mp4
Since it did work with previous early access of jfx (up to 17-ea-9, actually), I did manage to pinpoint that change responsible: openjdk/jfx#454
The above PR changes the type of listener used internally by the built-in bi-directional bindings, from ChangeListeners<T> to InvalidationListeners.
This should be transparent to most if not all applications, but because Flowless relies on ReactFX, which interacts with bindings and events in a very intimate way, something was broken by that change.
I managed to workaround the issue in the VirtualizedScrollPane by replacing the affect bi-directional bindings by a couple of mirrored ChangeListeners.
I will submit a PR illustrating this workaround for your consideration.
Starting with javaFX 17-ea+11 I noticed that scrolling a StyledTextArea (from RichTextFX) no longer worked properly: when clicking the scroll bar elements, the text scrolls for the first couple of clicks and then entirely stop responding to clicks on these elements.
It does respond to using the mouse wheel of keyboard arrows however.
broken_scrolling.mp4
Since it did work with previous early access of jfx (up to 17-ea-9, actually), I did manage to pinpoint that change responsible: openjdk/jfx#454
The above PR changes the type of listener used internally by the built-in bi-directional bindings, from
ChangeListeners<T>toInvalidationListeners.This should be transparent to most if not all applications, but because Flowless relies on ReactFX, which interacts with bindings and events in a very intimate way, something was broken by that change.
I managed to workaround the issue in the
VirtualizedScrollPaneby replacing the affect bi-directional bindings by a couple of mirroredChangeListeners.I will submit a PR illustrating this workaround for your consideration.