TouchPoint Queueing

Dear Adobe Community

The company I work at is running into an old problem again we enquired about 2 years ago.

We create multitouch software for large screens connected to desktop computers. This means multiple users can be active on the same screen. The problem we have is that a lot of touches eventually result in queueing of the touch points. The program then goes through all the touches at it's own pace. This results in the user feeling disconnected with the software, as it is going through touches that happened a while before.

For the past years, as hardware moved forward, the problem was in most cases not noticeable anymore. The previous tips we got were about making chances to improve the overall performance so the program would not start queueing the touch points. However, we are now running into this problem again. Our program is targeted at children. And children are not subtle like grown ups in handling the screens. So the program gets to process lots of touchpoints. Theoretically speaking, you do expect that if a screen has 100 touchpoints, the underlying program should be capable of processing them all. I understand there needs to be some way of determining the order of the inputs and it's probably hard to work around queueing, because the other solution would be to drop touches over an x amount. And this might also lead to a user feeling disconnected.

We tried to use the lasted version of the AIR SDK, but this did not change anything.

Is there anything planned to find a more user friendly solution for the touchpoint handling?

Are there any new tips you could give us to workaround the current queueing?

Sincerely,

Jens