touchscreen problem

[hari]

tschak: if this is really a regression, it has to be fixed asap. We can't trash existing stuff with new patches. And just as a note, that hid stuff should not really be handled in orbiter.

br, Hari

[Newguy2]

tschak: if this is really a regression, it has to be fixed asap. We can't trash existing stuff with new patches. And just as a note, that hid stuff should not really be handled in orbiter.

br, Hari

Hari,to answer your question,  it is definitely a regression, Everything was working great until i updated to the later alpha. thanks 

[tschak909]

This has been fixed, and should be available once the next round of updates is built. \

-Thom

[hari]

thanks tschak!!

[widescreen]

yeah thanks tom, appreciate it

[widescreen]

This has been fixed, and should be available once the next round of updates is built. \

-Thom

Thom, ahey buddy, has this fix been rolled in? i rebuilt my core and did a reinstall last night and was excited,  tried to use my md, but the same issues still occur.  

[dlewis]

I don't believe the next round of updates have been built yet.

[widescreen]

oh ok thanks

[Newguy2]

I don't believe the next round of updates have been built yet.

can anybody confirm this because i see this in the alpha 2.32 release:

pluto-orbiter (119,138) - Fixes to GenericHIDInterface for Gyration 3101 remotes.

is that anything to do with it? 

[Newguy2]

fellas, i'm not trying to be a pest, i'm just not sure....so has it been added to the updates already? if so it still does not work

[widescreen]

hey guys, my experience as of today is as follows:

1) any selection is still being appended with a 1, thereby bringing you to the lighting menu
2)it has gotten worse. the curser does not follow most selections now. before today it would follow wherever you touch.  Before you were able to use the touchscreen on the kubuntu desktop. it worked perfectly. now the cursor does not follow where you touch on there too.  works fine booting kubuntu from harddrive without lmce, so it's a problem with lmce. 
3) all my md hardware is unusable because of this, spent alot of money when it did work, now all is just a waste of money.
4) like hari said, this a regression. 

[Newguy2]

I can't get anybody to even respond to my questions and comfirm, thom or otherwise as to the status of the fix.

[tschak909]

apparently, there still is more to do, nevermind that you guys are using a setup i can't reproduce. *hmm*

-Thom

[widescreen]

apparently, there still is more to do, nevermind that you guys are using a setup i can't reproduce. *hmm*

-Thom

Thom, i understand, and i appreciate you responding to my post.  I appreciate your attempt to repair the driver.  Hope you understand where we're coming from from, it's a little frustrating to have something working one day, and spending alot of money to purchase more hardware that was proven compatible, to only have your entire setup made useless the next day because of an error i did not make, nor have the equip to fix. please do not take my anxiety any way.      

[hari]

apparently, there still is more to do, nevermind that you guys are using a setup i can't reproduce. *hmm*

I can't see anything special in the way those guys use their touchscreens, or do I miss something?

best regards,
hari