Summary: | NEWT bcm.vc.iv only consume one mouse input event per frame | ||
---|---|---|---|
Product: | [JogAmp] Newt | Reporter: | Xerxes Rånby <xerxes> |
Component: | embedded | Assignee: | Sven Gothel <sgothel> |
Status: | CONFIRMED --- | ||
Severity: | minor | ||
Priority: | --- | ||
Version: | tbd | ||
Hardware: | embedded_arm | ||
OS: | linux | ||
Type: | DEFECT | SCM Refs: | |
Workaround: | --- | ||
Bug Depends on: | |||
Bug Blocks: | 1178 |
Description
Xerxes Rånby
2015-09-30 23:56:06 CEST
This bug would provide a solution to bug 1178 cc5, adding this bug as a blocker for 1178. cc5: re-use the x11 newt events as is then it would support multiple mousepointers etc https://jogamp.org/bugzilla/show_bug.cgi?id=1178#c12 Having only one event dispatch thread would makes it easy to solve 1178 cc2: if you move the X11 window outside the visible screen then the overlay gets recentered by bcm.vc.iv code to be inside the screen. Fix for cc2 require that the bcm.vc.iv driver send a new WindowEvent when it have re-centered inside the screen. Because having two event dispatch threads one for X11 window toolkit and one for the BCM VC IV dispmanx toolkit easily cause hairy deadlocks. https://jogamp.org/bugzilla/show_bug.cgi?id=1178#c12 moved to post 2.3.2 - sorry |