Important: Please read the Qt Code of Conduct -

Response Issues with Beaglebone

  • Re: Beaglebone Black screen calibration

    Running Qt Creator 4.0.3

    Based on Qt 5.7.0 (GCC 4.9.1 20140922 (Red Hat 4.9.1-10), 64 bit) with the Beaglebone 4.3" Touch display by 4D Systems I am having trouble with response to touches not totally similar to the referenced topic but this is the only reference I found here about touch problems.

    A large percentage of the time when selecting a button using a cross compiled app on the Beaglebone, the button will indicate the touch but the action will not be called. Occasionally it will call twice or have a long delay. Sometimes you have to touch the button a few times to get a burst of activity. All of these are seemingly random and do not seem to depend on how long you hold your finger or how hard you press. The problems do not exist on the desktop application.

    I've tried responding to release action rather than click but the behavior remains the same.

    Anyone have a clue about what might be causing this flaky behavior?
    Has anyone experienced similar response issues using any touch screen?

  • Did anyone find a solution for this problem?
    its really annoying...
    please advice.

  • I responded to the Pressed event and thought it improved things a bit.

  • @jastmc said in Response Issues with Beaglebone:

    I responded to the Pressed event and thought it improved things a bit.

    is there any other solution to fix this problem properly?

  • Perhaps there is something in your code that hogs the UI thread on this platform, but not on desktop -- due to the specific activity or just faster processor.

  • Lifetime Qt Champion

    Did you test with default project with 1 button?
    If that lags, then its driver issue or something with the
    Beaglebone board.

  • @mrjj
    yeah, i just make a simple project with 1 button and 1 text box.
    probably there is something wrong with touchscreen driver.

  • Does the program have a C++ portion, or can one be created? I've found QAbstractNativeEventFilter to be useful for diagnosing these issues, along with any logging facility the underlying touch interface supports. Timestamps and event types are nice for determining if there is a significant delay or compression occurring between the kernel and application.

Log in to reply