ArrayArrayArrayArray
BrainModularBrainModular Users Forum2016-02-06T18:02:21+02:00https://brainmodular.com/forums/app.php/feed/topic/52922016-02-06T18:02:21+02:002016-02-06T18:02:21+02:00https://brainmodular.com/forums/viewtopic.php?t=5292&p=34659#p34659Statistics: Posted by ahonoe — 06 Feb 2016, 17:02
]]>
2016-02-03T22:15:53+02:002016-02-03T22:15:53+02:00https://brainmodular.com/forums/viewtopic.php?t=5292&p=34636#p34636like "if mouse down and param change it affects 1, if was 1 and mouse release affect 0". then this to a stop event flow to prevent feedback
]]>2016-02-03T18:41:10+02:002016-02-03T18:41:10+02:00https://brainmodular.com/forums/viewtopic.php?t=5292&p=34634#p34634 To check this, first get the plugin window open on screen, then open the Usine patch containing the plugin - so that you can see both at once.
Now click the button that you want to test for. If it can be automated, the 'plugin wrapper' module inside the Usine patch should grow a new input and output when you click the button on the plugin (hopefully with a sensible label, though some plugins are better than others in this respect!).
If the 'plugin wrapper' in the patch does grow a new output, the output value will be a value between zero and one, and you should be able to connect it to a "has changed" module in the patch to detect each click.
However, if the button doesn't expose itself for automation via the 'plugin wrapper' module, I don't think there's any simple way to detect the mouse click.
Statistics: Posted by Trogluddite — 03 Feb 2016, 17:41
]]>BrainModularBrainModular Users Forum2016-02-06T18:02:21+02:00https://brainmodular.com/forums/app.php/feed/topic/52922016-02-06T18:02:21+02:002016-02-06T18:02:21+02:00https://brainmodular.com/forums/viewtopic.php?t=5292&p=34659#p34659Statistics: Posted by ahonoe — 06 Feb 2016, 17:02
]]>2016-02-03T22:15:53+02:002016-02-03T22:15:53+02:00https://brainmodular.com/forums/viewtopic.php?t=5292&p=34636#p34636like "if mouse down and param change it affects 1, if was 1 and mouse release affect 0". then this to a stop event flow to prevent feedback
]]>2016-02-03T18:41:10+02:002016-02-03T18:41:10+02:00https://brainmodular.com/forums/viewtopic.php?t=5292&p=34634#p34634 To check this, first get the plugin window open on screen, then open the Usine patch containing the plugin - so that you can see both at once.
Now click the button that you want to test for. If it can be automated, the 'plugin wrapper' module inside the Usine patch should grow a new input and output when you click the button on the plugin (hopefully with a sensible label, though some plugins are better than others in this respect!).
If the 'plugin wrapper' in the patch does grow a new output, the output value will be a value between zero and one, and you should be able to connect it to a "has changed" module in the patch to detect each click.
However, if the button doesn't expose itself for automation via the 'plugin wrapper' module, I don't think there's any simple way to detect the mouse click.
Statistics: Posted by Trogluddite — 03 Feb 2016, 17:41