Re: Alternative approach for behaviors, leveraging existing event system

John, >> >> You’re proposing using a similar mechanism to enable behaviors to >> communicate with their controls. That seems like a different problem that >> deserves a different discussion. In particular I don’t think these two >> problems need to be solved at the same time even if they both

Re: [External] : Re: Alternative approach for behaviors, leveraging existing event system

their InputMap), while (as far as I can see) not considering all the roads that you will be closing off forever by doing so. --John Thank you -andy *From: *John Hendrikx *Date: *Monday, October 16, 2023 at 13:10 *To: *Andy Goryachev , openjfx-dev@openjdk.org *Subject: *[External] : Re: A

Re: Alternative approach for behaviors, leveraging existing event system

ion of the application or a page container to intercept the key binding, and not the TextArea’s. -andy *From: *openjfx-dev on behalf of Martin Fox *Date: *Wednesday, October 18, 2023 at 10:15 *To: *John Hendrikx *Cc: *openjfx-dev@openjdk.org *Subject: *Re: Alternative approach for behaviors,

Re: Alternative approach for behaviors, leveraging existing event system

> On Oct 18, 2023, at 1:20 PM, Andy Goryachev wrote: > > I wonder if this might encroach upon application-specific requirements/logic > (that is, does not belong to the control behavior). > > For example, when the user enters text in a TextArea inside of a multi-cell > notebook style applic

Re: [External] : Re: Alternative approach for behaviors, leveraging existing event system

: Alternative approach for behaviors, leveraging existing event system Hi Andy, Thanks for the quick response! Let me see if I can clarify some of your questions. Thank you, John, for a detailed writeup. Before going into details, I would like to ask you to clarify some of the aspects of the

Re: Alternative approach for behaviors, leveraging existing event system

Hendrikx Cc: openjfx-dev@openjdk.org Subject: Re: Alternative approach for behaviors, leveraging existing event system John, I want to explore this a bit further. I think there are two separate proposals in here. In most UI toolkits there’s one or may ways to translate a key event into an action

Re: Alternative approach for behaviors, leveraging existing event system

John, I want to explore this a bit further. I think there are two separate proposals in here. In most UI toolkits there’s one or may ways to translate a key event into an action. For example, Ctrl-C yields the Copy action and the right arrow key yields the moveRight action. This is done in a c

Re: Alternative approach for behaviors, leveraging existing event system

imarily looked at ButtonBehavior so far, and that seems pretty trivial to change. Thanks. --John Thank you -andy *From: *openjfx-dev on behalf of John Hendrikx *Date: *Monday, October 16, 2023 at 04:51 *To: *openjfx-dev@openjdk.org *Subject: *Alternative approach for behaviors, leveragin

Re: Alternative approach for behaviors, leveraging existing event system

() except by subclassing, correct? 7. I wonder if this will require a more drastic re-write of all the skins? Thank you -andy From: openjfx-dev on behalf of John Hendrikx Date: Monday, October 16, 2023 at 04:51 To: openjfx-dev@openjdk.org Subject: Alternative approach for behaviors, leveraging

Alternative approach for behaviors, leveraging existing event system

Hi Andy, hi list, I've had the weekend to think about the proposal made by Andy Goryachev to make some of the API's surrounding InputMap / Behaviors public. I'm having some nagging doubts if that proposal is really the way forward, and I'd like to explore a different approach which leverages