jonathan at jonathangiles.net
Wed Jun 20 08:28:23 UTC 2018
A great regret. I wish it were supported, but it isn't due to historical
legacy. There are some small ways you can make some progress, e.g. add
focus listeners on the editor node, but they are half solutions at best.
(Tapped on a touch device)
On Wed, 20 Jun 2018, 10:25 AM , <fastegal at swingempire.de> wrote:
> Zitat von Tom Eugelink <tbee at tbee.org>:
> > This is a well known and already deeply discussed issue. I'm still
> > not sure where we are with it, but Jonathan knows I believe.
> tbd_major ... since nearly 7 years :(( actually, it took 4 years to
> get the necessity accepted, then another 2 years playing with
> incomplete suggested fixes and then ...
> It's a complex problem, requires
> a) additional commit/cancel api on the virtual controls to allow
> collaborators to cleanly terminate ongoing edits - this part has still
> been debated
> b) a major cleanup of cell implementations - this part was under way
> (and evolving into the good direction) until Jonathan left
> CU, Jeanette
> > On 19-6-2018 20:53, Ty Young wrote:
> >> On 06/19/2018 10:51 AM, omniprof at gmail.com wrote:
> >>> A minor issue in the Table component existed in previous versions of
> >>> when editing in a cell was turned on. Only if the Return key was
> >>> pressed was
> >>> the data entered into the backing bean. Leaving the cell with Tab or by
> >>> mouse did not register the change. I thought just when a cell looses
> >>> it should trigger updating the bean. I have not looked at the recent
> >>> but I thought I'd ask if it has come up on anyone's radar. I
> >>> noticed it when
> >>> I moved from teaching Swing to FX.
> >>> Ken Fogel
> >> IIRC, this isn't specific to Table. A spinner with editing enabled
> >> also does this and it breaks events(onKeyTyped does nothing).
More information about the openjfx-dev