I think I need your help - it's another case of 'it works fine on my machine' 😉
- two tabletops
- one PC
- one desktop AIR app w/ two modules in it, for two concurrent users
- touches via TUIO server
As I mentioned above - the app works flawlessly on my PC - I can interact w/ it using mouse or TUIO Simulator:
But then there is a test rig w/ actual tabletops and something strange happens.
The app works well on one of them, but on the other... not really.
Look at the vid, please:
test PC is a piece of crap [just 30fps], but it is not the case - the same issue appears on a decent one, just in 60fps.
As you can see the pointer-hand
appears [on DisplayList, not in Starling], moves and disappear w/ interactions, which means the app gets events from TUIO server, the log from the console also confirms that communication is not a problem here.
Please take a look at these two stills from test rig vid:
The problem seems to be somewhere in between of my TUIO Listener and buttons listening to touch events.
The only [?] thing in between is TouchProcessor, innit?
So my next step before Monday was:
I made a copy of TouchProcessor.as, renamed it, didn't change any logic there, just added logging from methods:
I'd appreciate any advice on what more should I log before the next test. As I am in Europe, test rig is in US [distance and time zone offset don't help] I'd like to add as much useful info to logs as possible
If anyone has seen anything like this before and knows the cause/solution - please share.