my introduction - and 2 "quick" questions

[Rick Stockton]

INTRODUCTION:
Hi. I'm the person who recently extended the Qt Mouse Event API to 
handle "up to" 31 Pointer buttons, and I have begun to play with 
coresponding KWin enhancements. (Qt5, and KDE-Next.) You probasbly 
already know that Qt uses a set of "Platform Plugin" modules to 
interface with lower-level libraries (such as wayland, xcb, xlib, 
MS-Windows, and etc.). My work with xcb and xlib is done. But, when I 
started to add my changes into Qt's wayland Platform Plugin, I found 
that our "stale" code no longer compiles against a fresh pull of wayland.

I probably don't need help with accomplishing that migration. And BTW, 
with regard to my presence on this list, I intend to lurk QUIETLY. So 
please give me a swift kick, if I post an inappropriate message. :)
----
My questions are WRT to recent work by Taigo Vignatti (October, and 
maybe a little bit earlier). Those patches included an enhanced button 
translation routine (basically duplicating the X11 evdev Driver scheme.) 
But, in addition to the "mouse" button range, it adds translation code 
for the "generic" and "joystick" range of values as well. Other portions 
of the patch provide hotplug support in the compositor, and so I'd like 
to ask:

(1) Can these changes possibly support multiple pointers on the same 
Seat? (i.e., somewhat like XI Version 2.)

(2) and if so, does the concept of a "primary" versus "secondary" 
pointer still apply?

If multiple pointers are NOT supported on the same Seat, then I'll want 
to "translate" the events of a connected joystick into instances of 
QtMouseEvent (with "mouse" button numbers). But, if we can now support 
pointers at the same time, I'll want to create new QtJoystickEvent() 
Classes in our API.

My thanks in advance!