X220T Pen Input Screen Edge Sensitivity?

[Shogmaster]

Looking at Wacom Component website, I don't see any 16:9 digitizer boards. Could the problem be that the 12.1" 16x10 digitizer board is not quite lining up with the edges of the 12.5" 16x9 LCD's layout?



Samsung S7 uses 11.6" 16x9 LCD, so the same 12.1" 16x10 board would be good enough to overlap all the edges.

Too crazy of a theory? Thoughts?

[cegras]

Actually, that's a very astute observation.

But! It seems strange that Wacom would not custom produce digitizers for big customers like lenovo or samsung.

[wicked1]

I've had several mild posts deleted from the lenovo forums too. They don't like it if you actually try to get something done about the issue.
I'm down for anything that might officially get Lenovo's attention!

[Shogmaster]

Actually, that's a very astute observation.

But! It seems strange that Wacom would not custom produce digitizers for big customers like lenovo or samsung.

For Wacom, providing panels for Tablet PCs are lower priority since it's a low margin business. It also cannibalizes from Cintiq sales in some amount, so it's not a business they are hog wild to support...

[cegras]

Hmm, it would make sense. If your pen falls off the sensor grid then windows might do its best to extrapolate. So it could be mapping a portion of the digitizer space to an area not covered by the sensing grid, which would produce an increase in sensitivity as it is not a 1:1 correspondence.

I think it's a perfect explanation, if Wacom is indeed not giving digitizers that are correctly sized.

[ineededausername]

Hi everyone!
I'm an amateur C++ programmer and I just registered here. I just ordered an X220t.
When I saw that this tablet had problems, I decided to fix the damn thing instead of returning it and incurring the 15% fee (a ridiculous amount to charge).
People have commented before that a mesh map would be really easy to do. Indeed, I just found this:
Manually changing the mouse sensitivity with windows hooks - C++ | DaniWeb
showing that changing mouse position is very easy with the WinAPI.
If anyone here is willing to work with me, let's get this done before Christmas. It'd be nice to have an actually-working tablet.

[seaturn]

ineededausername,
Second, I did not get you what an idea of it. The digitizer generates the events from its grid/sensor. The driver listen those events and changed the pointer.

To remap 15Kx27K griid.... well good luck with RAM

[cegras]

You don't have to remap the entire grid .. just find a way to decrease sensitivity of the grid near the affected edges.

[seaturn]

You don't have to remap the entire grid .. just find a way to decrease sensitivity of the grid near the affected edges.

OK, it might work

[ineededausername]

ineededausername,
Second, I did not get you what an idea of it. The digitizer generates the events from its grid/sensor. The driver listen those events and changed the pointer.

To remap 15Kx27K griid.... well good luck with RAM

You wouldn't remap the entire grid... just remap some reference points and interpolate the others. Perhaps even only remap the edges.