mousestate nopoll does not deactivate reporting
Does look very simple, but why ....
I want mouse state only report on a bang. That is ok the first time. But then, also after sending it a no poll-message, it keeps reporting. And I can send "nopoll" as often as I like but it doesn't stop.
What do I do wrong?
Thanks
Peter
works here, win 10, Max 8.2.0
Yes, it seems once you've sent a bang to [mousestate] it keeps on reporting the click. Could be a bug. But if I only use "poll" to activate it, "nopoll" stops it reliably.
The thing is that I only want a report when my dial is operated. So I cannot switch poll on because I don't know when it will happen. I can, however, send a bang when the dial sends out data.
I thought it would be simple. Sorry. But I guess I'll have to look for another way.
Thanks.
Switching on and off in one message should be the same as sending a bang.
That trick unfortunately is principally unable to return mouse-up in the below situation.
But I did find my solution for my self-centering dial in mouse filter:
Thanks for the help. And it is still strange that after one bang mouse state refuses to let itself nopoll-ed.
As long as mousestate does not get banged, poll/nopoll works fine with regard to mouse up/dn info aa well as coordinates. Once banged, it never forgets and the up/dn info will always be polled regardless. Clearly a bug. However, poll/nopoll will still start/stop coordinate output.
So don't bang it. Here's my workaround: