Context: Receive mouse drags on layer, says it's blocked from sending out of composition. Inserting a "Hold Value" node removes the message, but still blocks the signal from leaving the subcomposition if using a "Fire on display refresh". Using the triggers from the "Window" input port (generated from a node "Window" input) works, but stalls the composition (probably because of some sort of feedback).
I don't know if simple, but the attached ones should maybe convey the issue. Everything is WIP, so not really commented or structured in a sane manner. You'll also need the mm.layer nodeset also attached (only a simple statless thing to scale Vuo coordinates from within one layer to the bounds of a different layer).
As I seemingly had worked further on some other stuff, I didn't have the one I was complaining about. I had removed duplicate inputs and all of that, but this should still work the same.
In mm.cornerPoints, as you noted, the Dragged To trigger ports have the warning about "Events from this trigger are blocked from exiting this subcomposition". If events fired from within the subcomposition (Dragged To) can overlap with events coming in through the published input ports (as they would at the Select Latest nodes), then the fired events will be blocked. (More info in the manual.)
Often, the solution is just to insert a Hold Value node to merge the two event streams. But when I tried that with mm.cornerPoints, the 4 circles ended up displayed in the center of the window initially. I realized that the Hold Value had messed up the event flow which Select Latest needed in order to make the correct decision. So instead I took out the Select Latest and put in slightly different logic to make it use the default circle position (Option1) until the mouse was dragged.
Comments
Context: Receive mouse drags
Context: Receive mouse drags on layer, says it's blocked from sending out of composition. Inserting a "Hold Value" node removes the message, but still blocks the signal from leaving the subcomposition if using a "Fire on display refresh". Using the triggers from the "Window" input port (generated from a node "Window" input) works, but stalls the composition (probably because of some sort of feedback).
May be bug.
A sample composition would
A sample composition would probably help ... at least for those of us who might like to experiment. :-)
Indeed. Magneson, could you
Indeed. @MartinusMagneson, could you post a simple composition that demonstrates the problem? The attached composition, at least, works as expected.
drag-subcomposition.zip
I don't know if simple, but
I don't know if simple, but the attached ones should maybe convey the issue. Everything is WIP, so not really commented or structured in a sane manner. You'll also need the mm.layer nodeset also attached (only a simple statless thing to scale Vuo coordinates from within one layer to the bounds of a different layer).
As I seemingly had worked further on some other stuff, I didn't have the one I was complaining about. I had removed duplicate inputs and all of that, but this should still work the same.
MultiMapper.vuo
MultiMapper_subComp.vuo
MM.layer.vuonode
Could you also upload mm
Could you also upload
mm.cornerPoints
?Oh, sorry, here it is
Oh, sorry, here it is
mm.cornerPoints.vuo
In mm.cornerPoints, as you
In
mm.cornerPoints
, as you noted, theDragged To
trigger ports have the warning about "Events from this trigger are blocked from exiting this subcomposition". If events fired from within the subcomposition (Dragged To
) can overlap with events coming in through the published input ports (as they would at theSelect Latest
nodes), then the fired events will be blocked. (More info in the manual.)Often, the solution is just to insert a
Hold Value
node to merge the two event streams. But when I tried that withmm.cornerPoints
, the 4 circles ended up displayed in the center of the window initially. I realized that theHold Value
had messed up the event flow whichSelect Latest
needed in order to make the correct decision. So instead I took out theSelect Latest
and put in slightly different logic to make it use the default circle position (Option1
) until the mouse was dragged.MultiMapper.zip