Why-AreWeUsing-BothDashes-And-CamelCase? It creates unnecessary ambiguous situations where you don’t know if a command is Word-Word-Word, Word-WordWord or WordWord-Word. It’s like how PHP names its primitives all over again. Both dashed-separated-commands and CamelCase commands are fine, just, why both?
huh that is different then. It really boils down to how your hardware works.
I suppose the laptop stylus works only by pressure/contact, so not like a tablet stylus. In that case, a friend of mine uses a special kind of glove that is specifically made to prevent the hand from being recognized by the touchscreen.
I could ask her later, but in the meantime I think they are called stylus gloves or something on the lines.
A touchscreen that supports active styli instead of the simple capacitive ones are pretty similar to a drawing tablet, but it does require the software to understand how it works.
Interesting, I though windows or a specific driver allowed to disable one of the input modes.
I’m not sure honestly. As far as I know, active styli touchscreens “work” in Linux, but very little software actually take advantage of it on the Linux side since it’s largely a Windows thing that was introduced with the Surface line.
I don’t have enough experience with HID device drivers or input libraries to say this with proof, but I think the underlying structure to enable that should already be in place, so it could be a matter of time for it to become “mainstream” in drawing/note taking programs.
The only deep dive I took was into libevent when trying to come up with a way to map the tablet buttons, and seeing the capacity in a wayland environment makes me think each wayland wm/dm is “stylus-ready”.
I have no clue about xorg though, so xorg-native programs might not be able to distinguish mouse/tablet/stylus in a decisive manner.