On v5.2.3 I am experiencing no touch input in SambaPOS only on the right side of the screen.
EDIT: I don’t believe it’s related to v5.2.3 - I have a customer on v5.2.2 with the same issue.
I believe it is the same issue as reported here 30 days ago, but since the YouTube video is no longer available on that post, I can’t be certain, also there was no further posts after recalibration was mentioned, so it may not be related since I’m using a capacitive multi touch screen on a tablet which doesn’t require calibration. So I’ve started this new post.
A column down the right side of the screen doesn’t work with touch. It works fine with the mouse. I have experienced this now with 3 separate tablets with different spec. All are running Windows 10 Home with latest build 1803.
On the above video, I am also using the
-notablet parameter on starting SambaPOS. Without using the parameter, the non responsive area on the right is larger.
I can’t be certain, but I have setup tablets in the past and did not notice this, so wondering if it is related to a windows update or change in touch input in the latest build of Windows 10?
In Windows and other software, the touch works perfectly to the edge of the screen. However I did notice this very strange behaviour which you can see in the video below. If SambaPOS is open, in a window and I open Microsoft Edge, it would appear the UI controls also don’t work on the right edge, or even at all. Once I close SambaPOS, Edge works perfectly including right up to the right edge of the screen!
So everything I am setting up on is using multi touch capacitive screens (so not a calibration issue - you only need to calibrate resistive touchscreens). As I am also using 15" touchscreen POS terminals with multi touch capacitive screens and they don’t have any problem, I started thinking about what is different about a tablet.
I checked that all the tablets are using display scaling of 125% or 150%. I thought this might be the issue, but I tested without display scaling (i.e. set to 100%) and the problem still exists.
Everything I have tested with and without the
-notablet startup parameter.
On the specific tablet in the video, it’s a Linx 12X64 with 12.5" screen, 1920x1080 resolution.
Other systems I confirm the same issue with are a Linx 1020 with 10.1" screen, 1280x800 resolution, and a PiPO X9 “mini touchscreen system” (basically a tablet without a battery) with 8.9" screen, 1920x1200 resolution.
I do wonder if it is related to the Windows 10 build, which is quite serious then as if this is the case, many people are going to start to experience this issue when their system updates. Going back to thinking what is different with a tablet and a POS terminal that have the same screen type, I can only really see it as the Windows 10 build. The tablets I use are consumer models so running Windows 10 Home, currently at build 1803. The 15" POS terminals, which have a 1024x768 PCAP (capacitive) screen and do not experience this issue, are running Windows 10 IoT Enterprise LTSB Entry with build 1607 (being LTSB “long term support for business” version they don’t get feature updates so will remain on 1607 build forever).
Any suggestions of anything else I can try?