Julien Bayle

Usually, I used to use the set message with objects because it only sets without making the objects firing the message content.

At the same time, I need to refresh the matrixctrl, which I do with a clear object.

Clear object makes a "clear" of the display AND fires all the cleared position in the matrixctrl to output.

I'd like to avoid to fire 16 * 16 messages : set x y 0, instead of using clear...

Usually, I used to use the set message with objects because it only sets without making the objects firing the message content.
At the same time, I need to refresh the matrixctrl, which I do with a clear object.

matrixctrl-the-clear-message

You could put a gate at the output of matrixctrl and close it before you send a clear.

Or you could connect a grab to  matrixctrl and send clear to the grab instance.

if I can avoid to send 256 messages, I do.

thanks for the grab lead.. I'll check that.

for the gate it is like avoid to send 256 messages.. I just wanted to know if there was a better way.

if I can avoid to send 256 messages, I do.
thanks for the grab lead.. I'll check that.
for the gate it is like avoid to send 256 messages.. I just wanted to know if there was a better way.


matrixctrl & the clear message