Fluid.plotter mouse up


It seems like fluid.plotter is sending x y coordinates on both mouse down and mouse up events. Is there a way of reporting the coordinates only on mouse down? I don’t want a sound triggered when I release the mouse from the plotter.

I looked into the jsui file but couldn’t figure it out.

Thanks a bunch!


1 Like

I’ve managed to filter the mousedown event using [mousestate], but was curious whether it could be done in a more clever way…
Capture d’écran, le 2022-01-05 à 14.54.34

1 Like

This is how I envisaged one might make a more custom set of behaviours when I was thinking about the interface initially. It stops the fluid.plotter becoming too bloated with parameters and attributs to manage which are all hidden inside the object. As well, we try to keep the SC and PD versions with feature parity and how you deal with the callback of coordinates is something that is very CCE specific.

I hope the solution is not too patchy for your tastes :stuck_out_tongue:

1 Like

Haha, thanks James! You are giving such complete tools that I am now relunctantly connecting Max objects together… :laughing:

I do think [fluid.plotter] reports mouse clicks faster that [mousestate] though… I had to invert the state of the mouse (==0) so that the mousedown event is actually triggering the samples…

1 Like

Convenient but maybe dangerous? Something for us to ponder :slight_smile:

Ill test on my end because this is a good reason to put the mouse behaviour directly into the JS.

1 Like

There’s the [mousefilter] in Max but i think it’s made to only report on button-up event.

Sorry for the very long delay.

I just added an internal filter so that you only get output of coordinates while the mouse is down. This means that you won’t need to mousefilter on the outside to make it not trigger things as you release your mouse click.


Which means it will be in the nightly builds and soon Beta7 release.