Prioritized event handlers

[Andy Goryachev]

Dear Michael:

What happened to this proposal?  I would like to restart the discussion, if possible.

More specifically, I would like to discuss the following topics:


  1.  the reason the discussion was started was due to "priority inversion" problem in Controls/Skins, ex.: JDK-8231245<https://bugs.openjdk.org/browse/JDK-8231245> Controls' behavior must not depend on sequence of handler registration.  Do we have this problem elsewhere?  In other words, does it make sense to change the API at the EventDispatcher level when the problem can be easily solved by the InputMap at the Control level?
  2.  dispatching of events that have been consumed (as mentioned in the earlier discussion)
  3.  problem of creating unnecessary clones of events via Event.copyFor(), leading to ex.: JDK-8337246<https://bugs.openjdk.org/browse/JDK-8337246> SpinnerSkin does not consume ENTER KeyEvent when editor ActionEvent is consumed
  4.  why do we need Event.copyFor() in the first place?  why does Event contain the target??

Too many topics, yes, we might want to split the discussion into separate threads.

-andy


From: openjfx-dev <openjfx-dev-retn at openjdk.org> on behalf of Michael Strauß <michaelstrau2 at gmail.com>
Date: Friday, October 27, 2023 at 19:41
To: openjfx-dev <openjfx-dev at openjdk.org>
Subject: Re: Prioritized event handlers
Here is the proposal:
https://gist.github.com/mstr2/4bde9c97dcf608a0501030ade1ae7dc1

Comments are welcome.


On Fri, Oct 27, 2023 at 8:21 PM Andy Goryachev
<andy.goryachev at oracle.com> wrote:
>
> Would it be possible to create a proposal in the JEP format outlining the proposed public API?
>
>
>
> Thank you
>
> -andy
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://mail.openjdk.org/pipermail/openjfx-dev/attachments/20241107/de629c65/attachment-0001.htm>