Linux - NewbieThis Linux forum is for members that are new to Linux.
Just starting out and have a question?
If it is not in the man pages or the how-to's this is the place!
Notices
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
I have a touch interface with a stylus. I've no problems under the normal case, where the screen size is the same size as the output display size. However when I enable panning, I have problems panning out to the right and bottom of the display. The top and left sides are fine. Calibration was done several times with little or no success. Furthermore it was attempting with many combinations of options and tricks to try to fake out where the screen edges occured on the resistive matrix.
One interesting thing that makes me wonder, is that when I use a mouse, it works fine, ...BUT...I noticed that the pointer itself, when driven to the edges of the sides that operate correctly, drives off the screen for about 250-400ms then bounces back several tens of pixels to where it is fully visible on the display graphics. The pointer stays there until pan has shifted the screen is all the way to edge of the output display and then moves to the edge of the screen again. All this seems to make sense. Now for the sides that do not work, the pointer completely disappears off the screen for the same 250-400mSec but when bounces back towards the graphics area where it should be seen, only the the back trailing edge of the pointer is revealed on the graphics. The tip and rest of it are still off screen.
So in short, because of the way the mouse behaves when doing panning, it is consistent to the touch screen and stylus behaviour. I'm questioning whether there is an underlying, maybe fundamental issue with the way the off screen detection and cursor positioning is done, and not necessarily a driver issue. The mouse may work because it's not relying on the resistive touch screen coordinate position, but only it's digital counts related to movement and that is totally is independent of the pixel map.
Anyway those are my my thoughts and observations. So if anyone has any experience with this I would appreciate the help and advice.
Nial..
Last edited by nialbar; 03-24-2016 at 01:19 PM.
Reason: errors
that is not actually the OS you are using to post as an answer to that person question. It is only its version number which could be attached to many different Distros but not really, (depending on version handing that may well be only one version of OS that uses that method of version setting, so one may well be able to "google" that bit of information and find out what Distro it is attached to, but that is nip picking, and having to fix your mistake.)
Search Results Centos 6.5 (2.6.32-504.8.1-el5.x86_64 ) for example.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.