You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Hi! Thanks for maintaining such complex and demanded project!
I'm not sure if that's a right place to ask questions, so excuse me if it's not.
I have ARM embedded Linux board with USB touchscreen controller. It's required to run single Qt app with tslib and linuxfb plugin (without X-Server or anything similar).
To test the touchscreen I use ts_test app.
Identify chardev major and minor, then create file for that chardev (I assume that file can be used by tslib (and it's so) and have constant filesystem path)
The problem is when USB repluged - ts_test app stop receiving input from touchscreen controller. If I restart ts_test with the same command from shell - it's working like a charm up to next replug.
Is there any possibility to handle USB replug by some hack? E.g. handle replug by udev event or something similar? Main showstopper is that I can't just restart Qt app because of complex state, that can't be serialized with ease, I have same behavior in Qt app - on USB replug Qt app stops receiving touchscreen input and all is fine if Qt app is restarted.
There is related issue: #52
That's somehow resolved by commit: 5bfde87
I couldn't understand how that can help me with this case.
Is there any possibility to make things work without restarting the app on replug?
The text was updated successfully, but these errors were encountered:
Hi! Thanks for maintaining such complex and demanded project!
I'm not sure if that's a right place to ask questions, so excuse me if it's not.
I have ARM embedded Linux board with USB touchscreen controller. It's required to run single Qt app with tslib and linuxfb plugin (without X-Server or anything similar).
To test the touchscreen I use ts_test app.
Then run ts_test with:
The problem is when USB repluged - ts_test app stop receiving input from touchscreen controller. If I restart ts_test with the same command from shell - it's working like a charm up to next replug.
Is there any possibility to handle USB replug by some hack? E.g. handle replug by udev event or something similar? Main showstopper is that I can't just restart Qt app because of complex state, that can't be serialized with ease, I have same behavior in Qt app - on USB replug Qt app stops receiving touchscreen input and all is fine if Qt app is restarted.
There is related issue:
#52
That's somehow resolved by commit:
5bfde87
I couldn't understand how that can help me with this case.
Is there any possibility to make things work without restarting the app on replug?
The text was updated successfully, but these errors were encountered: