Re: master 3b41141708: Expose the name of an event's input device to Lisp

[Po Lu]

Brian Cully <bjc@spork.org> writes:

>       What level of application code is exposed to device naming?
> Surely the vast majority of code in Krita is completely agnostic as to
> where the event is coming from and only responding to an event type. The
> configuration would only specify a map of device+device-event ->
> internal-event (eg: (“logitech usb mouse” + “button 1 down”) -> “eraser
> down”), and the rest of the code in the system only cares about the
> latter event (“eraser down” in this case).

That's out-of-scope.  Krita plugins are based on attaching Qt signals to
objects, and the plugins are supposed to utilize the Qt input device
object that is passed around inside input events, which contains the
name.  Qt determines the type of device via that name, like Emacs does
and other X programs do.