search

mansrz / pymt

Automatically exported from code.google.com/p/pymt
0 stars 0 forks source link

TuioTouchProvider does not honour "device" attribute #257

Closed GoogleCodeExporter closed 9 years ago

GoogleCodeExporter commented 9 years ago 
What steps will reproduce the problem?
1. launch pymt app with two tuio providers (i.e. 'left' and 'right')
2. generate tuio msgs on both ports
3. on_touch_move(self, touch): print touch.device => gives the one with
lowest UDP port

What is the expected output? What do you see instead?
expected: based on what port osc message is received, use the correct
TuioTouchProvider instance.
instead: whatever the port, only the device with lower port is used, always

Please provide any additional information below.

osc is a singleton, when registering a callback, you can only give the
oscpath (and that's fine _IF_ osc were _NOT_ a singleton).

The problem is that TuioTouchProvider does not have a, let's say,
"self.osc" instance, but osc is a global object shared by all the
TuioTouchProvider instances.

Not to be fixed in Pymt, but in osc.

Original issue reported on code.google.com by ilya.cas...@gmail.com on 1 Jun 2010 at 9:59

GoogleCodeExporter commented 9 years ago 
fixed in pymt + osc
You can use a new dump tools:
python -m pymt.tools.dumpinput

Original comment by txprog on 2 Jun 2010 at 9:11