See updated webrev and comments at
https://bugs.openjdk.java.net/browse/JDK-8152423
-phil.
On 05/05/2016 12:16 PM, Jim Graham wrote:
In that case, in order to avoid race conditions (GC could be
accidentally triggered by this or subsequent shutdown hooks in the
system), it should be released b
Ah, that's good.
-- Kevin
Benjamin Gudehus wrote:
**Update:** I've found a work-around and quickly tested it on our test
suite. Previously we needed `FXRobot::keyPress()`, `FXRobot::keyType()`,
and `FXRobot::keyRelease()`. Since Java 8 it is possible to use
`Event.fireEvent()` and create three
I didn't realize that anyone was using the old FXRobot. I don't remember
this showing up on Jonathan's list of internal APIs that apps were
using, but I may have missed it.
I see two choices: 1) revert the change as you suggested...the cost of
keeping this code around isn't all that heavy; 2)
Voting for Guru Hb [1] to OpenJFX Committer [2] is now closed.
Yes: 9
Veto: 0
Abstain: 0
According to the Bylaws definition of Lazy Consensus, this is sufficient
to approve the nomination.
-- Kevin
[1] http://openjdk.java.net/census#ghb
[2]
http://mail.openjdk.java.net/pipermail/openjfx-de
Reminder, Monday is our weekly sanity testing.
You can find your testing assignment at:
https://wiki.openjdk.java.net/display/OpenJFX/Sanity+Testing
Also please remember that the repo will be locked from 1am PST until 1pm
PST.
Happy testing!
Thanks,
Vadim
