billy tran

i'm trying to create a pressure-sensitive patch with max/msp/jitter and hacked a mouse to bypass using a basic stamp to connect pressure pads to my computer. is there a way to extend the mousestate button so that it serves as a momentary switch rather than an on/off signal? in other words, i'd like the patch to recognize when i am standing on the pressure pad but stop as soon as i am off.

hi,
i'm trying to create a pressure-sensitive patch with max/msp/jitter and hacked a mouse to bypass using a basic stamp to connect pressure pads to my computer. is there a way to extend the mousestate button so that it serves as a momentary switch rather than an on/off signal? in other words, i'd like the patch to recognize when i am standing on the pressure pad but stop as soon as i am off.

extended-mousestate-on-maxmspjitter

At 7:14 PM -0600 6/9/07, billy tran wrote:

>i'm trying to create a pressure-sensitive patch with max/msp/jitter and hacked a mouse to bypass using a basic stamp to connect pressure pads to my computer. is there a way to extend the mousestate button so that it serves as a momentary switch rather than an on/off signal? in other words, i'd like the patch to recognize when i am standing on the pressure pad but stop as soon as i am off.

I may be misunderstanding the question, but the mousestate object already sends a 1 while the button is down, and a 0 when the button is released.

Chris Muir | "There are many futures and only one status quo.

cbm@well.com | This is why conservatives mostly agree,

 | and radicals always argue." - Brian Eno

At 7:14 PM -0600 6/9/07, billy tran wrote:
>hi,
>i'm trying to create a pressure-sensitive patch with max/msp/jitter and hacked a mouse to bypass using a basic stamp to connect pressure pads to my computer. is there a way to extend the mousestate button so that it serves as a momentary switch rather than an on/off signal? in other words, i'd like the patch to recognize when i am standing on the pressure pad but stop as soon as i am off.

-- 
Chris Muir           | "There are many futures and only one status quo.
cbm@well.com         |  This is why conservatives mostly agree,
http://www.xfade.com |  and radicals always argue." - Brian Eno


but i've only managed to interface the mousestate button in such a way that it just registers single click events... is there a way to make the patch recognize the mouse button being held down as one distinct timed event? does that make sense? so basically as long as i hold down the mouse button X occurs and as soon as i let go of the mouse, X stops.

but i've only managed to interface the mousestate button in such a way that it just registers single click events... is there a way to make the patch recognize the mouse button being held down as one distinct timed event?  does that make sense?  so basically as long as i hold down the mouse button X occurs and as soon as i let go of the mouse, X stops.


At 12:00 AM -0600 6/10/07, billy tran wrote:

>but i've only managed to interface the mousestate button in such a way that it just registers single click events... is there a way to make the patch recognize the mouse button being held down as one distinct timed event? does that make sense? so basically as long as i hold down the mouse button X occurs and as soon as i let go of the mouse, X stops.

At 12:00 AM -0600 6/10/07, billy tran wrote:
>but i've only managed to interface the mousestate button in such a way that it just registers single click events... is there a way to make the patch recognize the mouse button being held down as one distinct timed event?  does that make sense?  so basically as long as i hold down the mouse button X occurs and as soon as i let go of the mouse, X stops.

extended mousestate on max/msp/jitter