This isn't me not doing my research, this is objectively JavaFX not providing
the functionality that is necessary to do something rather trivial: update an
API object and provide information from that API object right after it's
updated to the user(without ChangeListener).
You are not
Il giorno mar 13 nov 2018 alle ore 16:11 Ty Young
ha scritto:
>
>
> On 11/12/18 9:12 PM, Brian Hudson wrote:
> > JavaFX like every other modern UI framework is single threaded.
>
>
> Which in itself is fine, running *just* the UI isn't much on modern
> processors. Adding a bunch of API object
On 11/13/18 12:12 AM, Tom Schindl wrote:
I'm sorry that I'm the one to bring you the bad news that you need to do
the work and can't offload multi-threading to JavaFX.
I already explain why it *seems* to work one some elements (until it
breaks like shown in the bug-report I referenced) and
On 13.11.18 04:00, Ty Young wrote:
>
> On 11/12/18 5:39 PM, Tom Schindl wrote:
>> Hi,
>>
>> You are supposed to interact with Nodes who are currently shown in the
>> SG only only the JavaFX Application Thread.
>
>
> I never touch the GUI in my other threads, ever. The threads simply
> change
I'm sorry that I'm the one to bring you the bad news that you need to do
the work and can't offload multi-threading to JavaFX.
I already explain why it *seems* to work one some elements (until it
breaks like shown in the bug-report I referenced) and for others it
breaks immediately because they
On 11/12/18 9:12 PM, Brian Hudson wrote:
JavaFX like every other modern UI framework is single threaded.
Which in itself is fine, running *just* the UI isn't much on modern
processors. Adding a bunch of API object updates that cause thread
slowdown to the mix that can cause UI stuttering
JavaFX like every other modern UI framework is single threaded.
The updating of your “API objects” can and should remain on a background
thread, however once updated the changes which trigger an update to your UI
(changing a value in a bound property) should occur on the JavaFX thread
via
On 11/12/18 5:39 PM, Tom Schindl wrote:
Hi,
You are supposed to interact with Nodes who are currently shown in the
SG only only the JavaFX Application Thread.
I never touch the GUI in my other threads, ever. The threads simply
change the value of a type stored in a property. The
Hi,
You are supposed to interact with Nodes who are currently shown in the
SG only only the JavaFX Application Thread.
JavaFX although is not checking each and every property (change) as this
would be too resource intensive but at sensitive cases (eg when
interacting with Glass) it does check
On 11/9/18 11:58 PM, Ty Young wrote:
Hi,
My JavaFX program updates API objects in the background via a non FX
thread that, when changed by another program, are reflected in my
JavaFX GUI's controls by property binding, specifically TableView,
Slider, TextField, and ComboBox. Problem is,
Hi,
My JavaFX program updates API objects in the background via a non FX
thread that, when changed by another program, are reflected in my JavaFX
GUI's controls by property binding, specifically TableView, Slider,
TextField, and ComboBox. Problem is, while JavaFX is OK with this for
11 matches
Mail list logo
