Hi John,

In regard to your input issue. If it's a possibility, I'd recommend looking
at 'libinput'. It's an generic input abstraction library. It might be more
up to date and provide quirk fixes for (all kind of) input hardware.
It's already the default input library used by X.org and Wayland
compositors but is in no way dependend on them.



On Mon, Nov 7, 2016 at 7:07 PM, David Hill <david.h...@oracle.com> wrote:

> On 11/7/16, 12:55 PM, John Neffenger wrote:
> Hi John,
>     I am probably the guy that will be looking over these, but I am in the
> middle of a big push. Feel free to ping me offline if I don't get back to
> you by early next week.
> Dave
> While porting OpenJFX to devices with an electronic paper display, I
>> resolved three issues in the graphics module that I thought I should pass
>> along. The following merge request on GitLab lists the issues and my minor
>> changes. See the Commits and Changes tabs in the middle of the page for
>> details.
>> WIP: Patches to OpenJFX
>> https://gitlab.com/openjfxepd/jfxpatch/merge_requests/1
>> Did I understand the code correctly? I would appreciate any feedback.
>> As a brief summary, the first issue, "QuantumRenderer modifies buffer in
>> use by JavaFX Application Thread," may be of general interest because it
>> occurs on the Monocle Headless and VNC platforms.
>> The second issue, "zForce touchscreen input device fails when closed and
>> immediately reopened," might affect only my platform, or maybe just the
>> older Linux kernel and device driver I'm forced to use, but I couldn't find
>> a good workaround without duplicating the entire LinuxInputDevice class.
>> The third issue, "Get two bytes for the Linux input event type, not
>> four," doesn't seem to cause any problems, but may still be worth fixing.
>> Thank you,
>> John
> --
> David Hill<david.h...@oracle.com>
> Java Embedded Development
> "A man's feet should be planted in his country, but his eyes should survey
> the world."
> -- George Santayana (1863 - 1952)

Reply via email to