Consider this code:
Uncommenting the touch animation will cause the MFD screen to not be rendered at all. This only happens when both the touch and pick animations are active; either one by itself works as advertised.
Additionally (or instead), I would love to be able for the touch animation to capture all mouse buttons and scroll wheel events, and distinguish them in the event data structure it emits; AFAICT, this should be possible without introducing breaking changes.
Context: the E-Jet uses a device they call "CCD", "Cursor Control Device", which is kind of a trackpad, with a click button ("enter") and a two-ring knob; it controls a cursor on the EFIS screens, giving access to a click-and-point style GUI on those screens, and the MFD uses this most heavily. Since a 3D CCD in flightgear would be very inconvenient due to the lack of tactile feedback (in the real aircraft, the CCD is designed to be operated "blindly", you look forward at the screens while your hand rests on the CCD on the center pedestal), I need to implement an alternative that mimics the ergonomics of the CCD, and my plan is to allow clicking directly onto the EFIS screens, and using the mouse scrollwheel to emulate the CCD scroll knob. Obviously this requires both touch (because that is the only animation that captures click position) AND pick or knob (because touch does not capture scroll events).