<AWT Dev> OpenJdk11-28-EA JDialog hanging

Sergey Bylokhov Sergey.Bylokhov at oracle.com
Wed Oct 31 16:13:16 UTC 2018

Hi, Martin.
On 31/10/2018 09:03, Martin Balao wrote:
> Your MultipleContextsUnitTest test has 2 assertions that don't look good to me:
>   * dispatchSENumber < num1
>   * dispatchSENumber < num2
> My understanding is that these assertions mean that a non-SequencedEvent event is expected to be synchronized with SequencedEvent events. If such synchronization is needed, the event has to be wrapped in a SequencedEvent event. There are no guarantees otherwise; previous to my proposal these event were discarded and in my Webrev.02 they are dispatched asynchronously.

This is not a strong synchronization, it is just an expectation that the events which were posted after SequencedEvent should be dispatched after it. So if the app will have focus event and then mouse click, then mouse click should be dispatched after the focus. Note that the for this case the test does not check the exact sequence of order(==), just a relative order(<).

Best regards, Sergey.

More information about the awt-dev mailing list