Which OS are you using? Can you send me an example of your patch?
I am on windows XP. The patch I am updating is here
http://www.apfrod.com/works/2005/04#Shape_Sequencer_Release_1
That does indeed help, thank you Joe! I was assuming. It behaves how I
would expect when I stick a print in place of the route which it didn't
before. But I will have to go back and work out where I have compensated
elsewhere in the patch for this assumption as just changing that part
hasn't stopped it acting wierd yet...
I can't believe I left it like that for a year without realising http://lists.puredata.info/pipermail/pd-list/2004-04/019433.html
-poil-
The joystick object sends both the button id and state for each button press event to avoid any ambiguity (or at least it is supposed to!).So
I'm not sure why your patch is getting confused, but it might bethat you
(like any good Pd user) are assuming that the rightmostoutlet fires
before the second-to-the-rightmost outlet. The joystickobject actually
sends the button-id first and then the button-state.So what you want to
do is use a "trigger" object and an "int" objectto reverse the event
ordering. Something like:[ joystick ] |
|
| [ t b f ] | / / | / / |/ / /| / / | | [ int ] | | / | / | / [ pack ] | [ route 1 2 3 4 ]Here, the first four outlets of the "route" object should be the states
of the first four buttons.Hope this helps, Joe jsarlo@ucsd.edu