News:

Rule #1 - Be Patient - Rule #2 - Don't ask when, if you don't contribute - Rule #3 - You have coding skills - LinuxMCE's small brother is available: http://www.agocontrol.com

Main Menu

touchscreen problem

Started by widescreen, August 07, 2009, 05:23:40 PM

Previous topic - Next topic

widescreen

I solved one problem with my core touchscreen and between my first 8.10 install and the latest 8.10 install update used in my reinstall, there is another issue. Whenever I touch home or make certain other selections, it appends "1" right after thereby sending me to lighting. example, if i select direct dial, the keypad shows up with a 1, if I dial 9....you see 91, dial 8...you 81 etc etc.  It has nothing to do with the driver and this was not happening before the latest alpha install.  My question is whether this has to do with .xorg settings or should i create a xmodmap, or if this is a error like the one that existed in the prior alpha install with weird characters were showing up? It seems to be happening upon "release", meaning if i hold my finger it stay on the main menu. Once i move my finger off, it's like pressing 1 in the keyboard.  I works perfectly on the kubuntu desktop, no errors there. thanx ;D

tschak909

shit.. it looks like my GenericHIDInterface driver is causing little glitches by overzealously translating event packets.

-Thom

widescreen

damn, i was hoping it was something i did wrong :P

widescreen

Thom, is there a work around for this for the time being by any chance?  8)

huh

Hijacking this thread- there may also be issues with touch pads.  Whenever I try to drag the cursor, whenever I release it thinks that I've clicked in the upper left hand corner of the screen on the "lighting" button.  By using a USB mouse, this effect is not seen.  Maybe related?

widescreen

#5
that is the same issue i'm referring to. It isn't that it's clicking on the upper left hand corner.  It is appending the number one to the release of every selection, thereby bringing up the lighting screen making touchscreens unusable.

tschak909

you wanna fix it? install orbiter properly on a device, or get a WebDT from tkmedia.

Otherwise, I'll have to fx the GenericHIDInterface class when I can.

-Thom

widescreen

#7
Quote from: tschak909 on August 12, 2009, 12:08:24 AM
you wanna fix it? install orbiter properly on a device, or get a WebDT from tkmedia.

Otherwise, I'll have to fx the GenericHIDInterface class when I can.

-Thom

oooo..kay, That's what i was asking. sorry if it sounded a way, i know your busy, that's why i asked of there was a work around because i didnt want to bug you. Maybe i'm a little slow, what do mean install it properly? Not sure what i have done wrong.  I have 8.10 installed as a core with a touchscreen, i assume you mean that's no good?

huh

Actually I'm glad that Thom said that- got me thinking- the problem doesn't exist for me on any of the orbiters- the one I got from TKmedia, the win orbiter, etc, the problem only seems to appear when I'm using a MD with a touchpad.  Widescreen, can you confirm?


tschak909

that IS where the problem is. It comes from the fact that your touchscreen is an HID device. It uses the /dev/input subsystem to communicate. I intercept those packets and translate them.

-Thom

widescreen

Quote from: huh on August 12, 2009, 12:45:13 AM
Actually I'm glad that Thom said that- got me thinking- the problem doesn't exist for me on any of the orbiters- the one I got from TKmedia, the win orbiter, etc, the problem only seems to appear when I'm using a MD with a touchpad.  Widescreen, can you confirm?



no I can't, because i do not have any other touchscreen devices.  ;)

huh

Not to beat a dead horse, but do the webdt's not use the /dev/input subsystem?  And, my win orbiter is on a laptop, but maybe there aren't problems with it due to the OS differences...

tschak909

No, it doesn't. Please ... stop... asking... stupid...questions! You are wasting my time.

-Thom

colinjones

Thom - these aren't stupid questions, please keep the tone friendly!!

Newguy2

hello fellas, it sucks but i can now confirm this issue as well, has anyone found a solution besides just not using the touchscreen? thanks :)