TV touchscreen

[zmrzlapka]

Hello guys

In school I want to share my presentation on touchscreen tv from sharp but the touchscreen seems to stop working when I connect input (pc) but when It connected the TV touch still workes in (tv)setting  but on input screen(pc) it doesn’t. Can I somehow calibrate it or what should I do ?

[DarkWaterSong]

Most external touchscreens also have a USB cable that needs to be plugged into a computer to talk to them.  The issue is they need to connect to the PC as a mouse....and some may now be able to do that via Bluetooth but all the ones I worked with used USB.

 

Just a mouse input cannot be carried along a normal HDMI or Displayport cable.  Now if you have USB C it can carry both signals, but you may need to install some software from Sharp to get the tv working as mouse.

[Alex Atkin UK]

Its a bit misleading to say "working as a mouse" as that's not how they work, touchscreens are their own thing entirely.

A mouse sends information about direction of travel and acceleration, a touchscreen gives exact coordinates within its internal resolution that the OS has to translate to a position on the screen.  Its why mouse driven games wont work with a touchscreen without specific support or ugly hacks to simulate a touchpad (which DO behave like a mouse).

Its not exactly relevant to the topic here, but I feel its important to understand the difference as its also the reason why you may need drivers as mentioned.

[DarkWaterSong]

2 minutes ago, Alex Atkin UK said:

Its a bit misleading to say "working as a mouse" as that's not how they work, touchscreens are their own thing entirely.

A mouse sends information about direction of travel and acceleration, a touchscreen gives exact coordinates within its internal resolution that the OS has to translate to a position on the screen.  Its why mouse driven games wont work with a touchscreen without specific support or ugly hacks to simulate a touchpad (which DO behave like a mouse).

Its not exactly relevant to the topic here, but I feel its important to understand the difference as its also the reason why you may need drivers as mentioned.

I actually worked with embedded touch screens in kiosks in DMVs and other places.  Windows sees the touchscreen as a mouse, so its not issue on how the screen works....but what windows sees them as.  Basically any input device can speak mouse to a computer, and that computer does not know the device is not a mouse.

[Alex Atkin UK]

9 hours ago, DarkWaterSong said:

I actually worked with embedded touch screens in kiosks in DMVs and other places.  Windows sees the touchscreen as a mouse, so its not issue on how the screen works....but what windows sees them as.  Basically any input device can speak mouse to a computer, and that computer does not know the device is not a mouse.

You mean in device manager?  That's just to simplify things for the end user, its not technically how Windows sees it and I was thinking more from the technical side.

Realistically I think they should just bundle all "input devices" together instead of the legacy of mice having their own section, but instead they just added more confusion in the modern UI settings instead as there is no consistency between that and device manager.

I always tend to think of things more technically as its how Linux presents them.

[DarkWaterSong]

6 hours ago, Alex Atkin UK said:

You mean in device manager?  That's just to simplify things for the end user, its not technically how Windows sees it and I was thinking more from the technical side.

Realistically I think they should just bundle all "input devices" together instead of the legacy of mice having their own section, but instead they just added more confusion in the modern UI settings instead as there is no consistency between that and device manager.

I always tend to think of things more technically as its how Linux presents them.

I was talking win 8 and up where there is a "devices" section and it just shows as a mouse.  Also in all the mouse adjustment tools, how fast you click, touch screens, track pads, and all the other things that are not mice show up and windows pretends they are mice.  Basically the higher up your are in windows, the more a touch screen looks like a mouse.

 

Now there was also a bit of software we installed that did more than your average mouse driver, like being able to calibrate the touch screen and doing the software / driver translation to windows fake mouse land.

 

EDIT - as in command line knows its not a mouse, not so much the Windows GUI.

[Alex Atkin UK]

2 minutes ago, DarkWaterSong said:

Now there was also a bit of software we installed that did more than your average mouse driver, like being able to calibrate the touch screen and doing the software / driver translation to windows fake mouse land.

Newer devices (and by that I mean as far back as Windows 7) generally don't need any of that, as Windows gained a native protocol, though obviously the touchscreen has to be designed for it.  Which is kinda my point, that while touchscreens will share some UI things with mice, Windows doesn't actually see them as mice.

Example, if you hold the left button down you wont get a right click menu with a mouse.  Because a touch is not a click, it merely trigger the same UI function that a click does and holding your finger down triggers the UI element that right clicking does.  So the fact clicks are still configured in the mouse section is merely a legacy of mice being the most common input device for clicks.