ie let's say on a knob, i dlike to make it vertical-encoder type, rather than horizontal absolute, or make a combo swich function
this can be easy patched, but if we control input while the mouse is on it, it will fight with the 'build in' setting that also
set the value relative to mouse local position, leading to jumps.
I imagine lot of various applications, like setting all the steps of an array with 'external' mouse process instead of single, make small sized items that can be set even out of their edges limit, have a vumeter fader that transform to fader on msdwn, in fact very modular as the process is 'outside'. we can then link to XY of item or to anything else we want like general msdwn or other.
we can use bmp and two items in lot of cases but i guess it use more cpu, and need 2x modules, such 'block build in mouse process' could avoid that and would expand possibilities nicely. ..
now i can understand getting on all the modules codes must be a pain, cause ideally we would still need the item to output the
mouse dwn led, local xy, for us to start process, while blocking internal data setting, input taking over, so just block mouse general input wouldn't work i guess..
who knows..
just a though....
otherwise i would be happy of this even just for knob, it's a cool visual elmt to see a value on low screen size..Statistics: Posted by 23fx23 — 03 Jun 2010, 19:57
]]>