Interactive display on a television surface.
Interactive display on a television surface.
Typically, external touchscreens require a USB cable to communicate with a computer. The challenge is they must connect to the PC as a mouse, and while some support Bluetooth now, most still rely on USB. A standard mouse input can't travel through regular HDMI or DisplayPort cables. If your device has USB-C, it can handle both data and power, but you might need to install specific software from Sharp to enable mouse functionality.
It’s confusing to label them as “working as a mouse” since that’s not their actual method. Touchscreens operate independently, providing precise location data that the operating system converts into screen coordinates. Mouse-based games won’t function properly on a touchscreen without proper support or awkward workarounds that mimic a touchpad (which do act like a mouse). This distinction matters because it explains why drivers are sometimes necessary.
I previously dealt with embedded touch screens in DMV kiosks and similar environments. Windows interprets the touchscreen as a mouse, which means there’s no problem with the screen’s functionality. However, what Windows perceives varies. Any input device can be treated as a mouse, and the computer doesn’t recognize the source isn’t a mouse.
Refers to the device manager interface. It’s meant to make things easier for users, but technically it doesn’t align with how Windows interprets the system. From a technical standpoint, I believe grouping all input devices together would be better, rather than maintaining separate sections for legacy items like mice. This approach could reduce confusion in modern UI settings, as there’s currently no consistency between the device manager and the overall system layout. I generally view technical design more like how Linux presents it.
I was discussing Windows 8 and above with a "devices" area that only displayed a mouse. All the adjustment tools for mice—click speed, touch screens, track pads, etc.—appeared as if they were mice. The more advanced you are in Windows, the more realistic the touch screen looks like a mouse. There was also some software we installed that went beyond a standard mouse driver, offering touch screen calibration and translating the software/driver to mimic a Windows fake mouse. EDIT - in command line it clearly isn't a mouse, but the Windows GUI behaves differently.
Newer gadgets, starting from Windows 7, typically don't require these features since Windows introduced its own protocol. Of course, the touchscreen must be built around it. This highlights my idea: while touchscreens resemble mouse interactions, Windows treats them differently. For instance, pressing a button doesn’t automatically show a right-click menu like with a mouse. A touch isn’t a click; it activates the same UI action, and holding your finger triggers the right-click element. Thus, the mouse-based click settings remain a relic from when mice were the primary input method.