]]>
of yeah that's cool i always put some array out back in to save them, no that mean no need of that now?
all array's in scripts are stored automatically by default. son you don't need to store them in an external array module.what do you mean by pm ? If it's preset manager, normally yes it should..would that work with pm also?
Statistics: Posted by senso — 08 Sep 2010, 01:09
]]>
that's very exciting to use gesture detection.
on multitouch, wow that seems powerfull to call functions!
Statistics: Posted by 23fx23 — 08 Sep 2010, 00:55
]]>
Silly me, I didn't think of expanding the module. Of course, the parameters don't miss inputs or outputs, they're just a bit shy and like to play hide'n'seek
. This will come in very handy. Thank you, boss!
Statistics: Posted by bsork — 08 Sep 2010, 00:31
]]>
If you "expand" the module the arrX and Y are visible.
I use the instruction set
CODE:
SetIsInput(arrX,false);SetIsOutput(arrX,false);SetVisible(arrX,false);
So gestures are memorized without any additional code.Tricky but cool...
Also it becomes easier to debug because we can watch inside array's with an array editor module.
I confirm, this script is not so easy...
Statistics: Posted by senso — 07 Sep 2010, 22:42
]]>
I had a quick look at the script (of course...) but this one will take quite some time to understand. If I ever will, that is.
I noticed, however, that arrX and arrY where defined as tParameter, but with neither input nor output, and also as invisible. Is this a way of using the new feature where array values are stored with the patch even when the variables seem to be "internal" to the script?
Statistics: Posted by bsork — 07 Sep 2010, 22:01
]]>
]]>
The basic idea is to memorize mouse, fingers, wiimote, etc, movements and trig actions when they are recognized.
See the demonstration video and the Wiki page for more informations.
Thanks to Nay-Seven for his help.
Statistics: Posted by senso — 07 Sep 2010, 13:32
]]>