My favorites | Sign in
Project Home Downloads Issues
READ-ONLY: This project has been archived. For more information see this post.
Search
for
  Advanced search   Search tips   Subscriptions
Issue 257: TuioTouchProvider does not honour "device" attribute
1 person starred this issue and may be notified of changes. Back to list
Status:  Done
Owner:  ----
Closed:  Jun 2010


 
Reported by ilya.cas...@gmail.com, Jun 1, 2010
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.
Jun 2, 2010
Project Member #1 txprog
fixed in pymt + osc
You can use a new dump tools:
python -m pymt.tools.dumpinput
Status: Done
Labels: Milestone-0.5 Component-Core

Powered by Google Project Hosting