Posted: 16 Feb 2016, 20:46
I am having 2 problems with mousedown on the matrix:
First of all, no mousedown information is sent if the clicked cell is the same as 'last clicked cell'. I often change the data in the matrix programmatically, and need a mousedown to be sent even if it's in the same cell, as it will now trigger computation of a new value.
I can't actually think of a use for a mousedown event if it is not independent of a change in the value of lastClicked..... a hasChanged on lastClicked would give you the current mousedown behaviour.
Secondly, I'm finding that if a change in the matrix triggers a processor intensive event, such as loading a bank from a VST, no mouseUP event is sent.
That's okay, but then the next mouseDown event sends a 0 instead of a 1.
I've actually worked around the 2nd of these, but cannot think of a workaround for the first.
Thoughts?
thanks,
-eric
First of all, no mousedown information is sent if the clicked cell is the same as 'last clicked cell'. I often change the data in the matrix programmatically, and need a mousedown to be sent even if it's in the same cell, as it will now trigger computation of a new value.
I can't actually think of a use for a mousedown event if it is not independent of a change in the value of lastClicked..... a hasChanged on lastClicked would give you the current mousedown behaviour.
Secondly, I'm finding that if a change in the matrix triggers a processor intensive event, such as loading a bank from a VST, no mouseUP event is sent.
That's okay, but then the next mouseDown event sends a 0 instead of a 1.
I've actually worked around the 2nd of these, but cannot think of a workaround for the first.
Thoughts?
thanks,
-eric