**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 `KeyEvent`s (PRESS, TYPE, RELEASE).
~~~java
Platform.
Hey,
yesterday a code change was made [1, 2] which removes FXRobot and the
com.sun.javafx.robot package in JavaFX 9.
>The com.sun.javafx.robot package contains obsolete, unused Prism
functionality that was intended for testing automation. It was superseded
long ago by glass Robot and should be re
On 13.05.16 2:53, Jim Graham wrote:
It is implemented in the FX Robot in that webrev...?
No, I meant the Robot class itself.I tried to find getHidpiScreenCapture
method..., but now I recognized that there is a method+hidpi parameter.
On 13.05.16 0:43, Jim Graham wrote:
bug: https://bugs.op
It is implemented in the FX Robot in that webrev...?
...jim
On 5/12/16 3:07 PM, Sergey Bylokhov wrote:
Hi Jim.
Do you plan to implement the new HiDPI API for the Robot class?
On 13.05.16 0:43, Jim Graham wrote:
bug: https://bugs.openjdk.java.net/browse/JDK-8137050
webr
Hi Jim.
Do you plan to implement the new HiDPI API for the Robot class?
On 13.05.16 0:43, Jim Graham wrote:
bug: https://bugs.openjdk.java.net/browse/JDK-8137050
webrev: http://cr.openjdk.java.net/~flar/JDK-8137050/webrev-00/
The order of taking scaling parameters in order of higher to lower
pr
bug: https://bugs.openjdk.java.net/browse/JDK-8137050
webrev: http://cr.openjdk.java.net/~flar/JDK-8137050/webrev-00/
The order of taking scaling parameters in order of higher to lower priority is:
- -Dglass.gtk.uiScale system property
- Same property in the environment
- GDK_SCALE in the environ
Thanks Kevin.
I was more curious as to why WebGL support hasn't been there since day 1, given
that WebKit itself supports it.
Felix
> On 13 May 2016, at 01:52, Kevin Rushforth wrote:
>
> It was an issue of resources versus priority and scope. JDK 9 is focused on
> Jigsaw modularity and a few
Hi Chien,
Please review the following.
https://bugs.openjdk.java.net/browse/JDK-8156809
http://cr.openjdk.java.net/~kcr/8156809/webrev.00/
This is a simple fix to cleanup some dead code that was discovered as
part of the review of the encapsulation work you are doing.
-- Kevin
It was an issue of resources versus priority and scope. JDK 9 is focused
on Jigsaw modularity and a few other minor features. It is more of a
"smoothing out" release than a big feature release (except for Jigsaw).
We expect JDK 10 to be a somewhat more feature-oriented release.
-- Kevin
Feli
