On 08/11/2023 17:23, Andy Goryachev wrote:
Dear John:
1.Runtime modification of key bindings on a per control basis
Before I reply further, where is the use case for this?
A very good question, thank you for asking. You might scroll back to
find it answered a couple of times during the dis
On 08/11/2023 21:18, Andy Goryachev wrote:
Dear Michael:
Thank you for specific questions!
> "switch between vim/emacs/etc. key mappings"? Maybe you can give a specific
example.
Vim/emacs might be a bad example, as they use key sequences. Key
sequences are not a part of this proposal (but
something like that.
It’s probably my fault that it is not immediately apparent from the proposal
that these use cases are supported by design.
Thanks
-andy
From: openjfx-dev on behalf of Michael Strauß
Date: Wednesday, November 8, 2023 at 11:24
To: openjfx-dev@openjdk.org
Subject: Re: [Ex
Hi Andy!
> There is a number of use cases for runtime modifications:
>
> - there might be a requirement to switch between vim/emacs/etc. key mapping
> - there might be a requirement to customize the mapping per user
> configuration (see the Eclipse “Keys” UI that I’ve shown before)
> - there are
jfx-dev@openjdk.org
Subject: [External] : Re: Key binding customization proposal
On 06/11/2023 20:54, Andy Goryachev wrote:
Dear John:
Thank you again for submitting a separate KeyBinding proposal. Ignoring my
objection for its sibling, I just wanted to point to these two items in Goals
and
On 06/11/2023 20:54, Andy Goryachev wrote:
Dear John:
Thank you again for submitting a separate KeyBinding proposal.
Ignoring my objection for its sibling, I just wanted to point to these
two items in Goals and Non-Goals:
* Keep internal details of InputMap implementation hidden (it is
: openjfx-dev on behalf of John Hendrikx
Date: Sunday, November 5, 2023 at 18:07
To: openjfx-dev@openjdk.org
Subject: Key binding customization proposal
This is an extension that builds on top of the Behavior API proposal (see
Public Behavior API proposal thread).
Summary:
Provide an opportunity
This is an extension that builds on top of the Behavior API proposal
(see Public Behavior API proposal thread).
Summary:
Provide an opportunity to customize key bindings during construction
time of standard behaviors, without exposing the internal|InputMap|s.
The API is constructed in such a
