Hi everybody,
Is there any further schedule for FX fully supporting VNC? Now I
really need input support :(
Best regards and thanks in advance!
2016-02-05 11:07 GMT-02:00 Daniel. :
> Hi everybody,
>
> I've succesfully build and using framebuffer-vncserver. The only
Hi Maurice,
Can you please file a JIRA on this issue?
Thanks,
- Chien
On 3/1/16, 11:45 PM, Maurice wrote:
Jim,
A solution in line of that of Johan Vos [1] works. JavaFX can be run
and doesn't crash on startup when compiling the shaders. I think they
should be taken into account for at
Thanks for reporting this.
-- Kevin
Anirvan Sarkar wrote:
I messed up before. I hadn't cleaned up my Javadoc directory before
building the documentation with jdk1.8.0_40.
The alignment issue exists with jdk1.8.0_40. After some searching in JBS I
found the javadoc bug JDK-8072461 [1].
We use javadoc from 8u40, too (at least for FX 8u60 and later). However,
it looks like an old version of the docs was published on the
docs.oracle.com web site. I will file a bug for that.
-- Kevin
Anirvan Sarkar wrote:
Hi,
Is the Javadoc tool used to build JavaFX documentation not from
I messed up before. I hadn't cleaned up my Javadoc directory before
building the documentation with jdk1.8.0_40.
The alignment issue exists with jdk1.8.0_40. After some searching in JBS I
found the javadoc bug JDK-8072461 [1].
According to the bug report the issue has been fixed in atleast
Hi,
Is the Javadoc tool used to build JavaFX documentation not from the JDK
used to build JavaFX ?
If you view the javafx.event.Event 'Uses' webpage [1] source, you will see
the comment:
So it looks like the documentation is built using jdk1.8.0 while JavaFX
itself is built using jdk1.8.0_40
It seems to me that initTransform(int axis, int index) in
LinuxTouchTransform calculates the wrong range. Regardless of the flipXY
setting it uses for the ABS_X the device's width and for the ABS_Y the
device's height. While in case with flipXY it should use for ABS_X the
device's height and