ArrayArrayArrayArrayArrayArray BrainModular BrainModular Users Forum 2010-03-06T11:40:08+02:00 https://brainmodular.org/forums/app.php/feed/topic/1972 2010-03-06T11:40:08+02:00 2010-03-06T11:40:08+02:00 https://brainmodular.org/forums/viewtopic.php?t=1972&p=12328#p12328 <![CDATA[mouse down zone]]> Statistics: Posted by 23fx23 — 06 Mar 2010, 10:40

]]> 2010-03-06T11:38:41+02:00 2010-03-06T11:38:41+02:00 https://brainmodular.org/forums/viewtopic.php?t=1972&p=12327#p12327 <![CDATA[mouse down zone]]> It's not easy to implement but far from impossible.
let me time for that.

Statistics: Posted by senso — 06 Mar 2010, 10:38

]]> 2010-03-06T09:24:34+02:00 2010-03-06T09:24:34+02:00 https://brainmodular.org/forums/viewtopic.php?t=1972&p=12301#p12301 <![CDATA[mouse down zone]]>
funny is it, i had same idea, instead of rec and storing many datas, why not simply be able to rec and replay "local" mouse moves to create complex automations, ie clic on 3 buttons, move a fader, set a lines array ect... then if the real hardware mouse is down on the object
it stops or re-rec the autom. but I imagine for more modularity this should be handled appart, kind of mouse rec/replay, and each local XY zone could be activated to be affected or not by the "virtual mouse", maybe...
as w7 return multitouch, we could even imagine each sub part to be able to receive/replay a diferent automation..

@ethnix: im not sure i understood , isn't it actually possible to "when you get CCx, make this sub container visible and active(patch active or let pass midi)? seems yes no? oh yup, maybe i catch now, a midi learn would avoid more complex patching?

Statistics: Posted by 23fx23 — 06 Mar 2010, 08:24

]]> 2010-03-05T21:40:29+02:00 2010-03-05T21:40:29+02:00 https://brainmodular.org/forums/viewtopic.php?t=1972&p=12282#p12282 <![CDATA[mouse down zone]]> It would be really cool then if we could also record that and then replay it as controller data for that specific container, inependant of the mouse...

Statistics: Posted by gurulogic — 05 Mar 2010, 20:40

]]> 2010-03-05T21:27:04+02:00 2010-03-05T21:27:04+02:00 https://brainmodular.org/forums/viewtopic.php?t=1972&p=12281#p12281 <![CDATA[mouse down zone]]>
i think it could be really improved if we could have
"mouse down zone", ie linked to a contenair or patch, or i was thinking back of an 'invisible but active" object that could even overlay
two differents contenairs
I'm agree but i believe it could more handy if this object could react also to midi.
My main idea: Imagine you control a patch with a midi foot controller, and within this patch, you have many subpatch with containers for each one. If an object is triggered by a midi cc, would be great to set the container to some kind of active mode, where it would receive midi, and others won't... Some kind of modularity for midi.

I know there is the rack/grid mode, but my main idea is to apply this to midi learn. You could control multiple subpatch with only a few controllers

Statistics: Posted by ethnix73 — 05 Mar 2010, 20:27

]]> 2010-03-03T00:49:50+02:00 2010-03-03T00:49:50+02:00 https://brainmodular.org/forums/viewtopic.php?t=1972&p=12194#p12194 <![CDATA[mouse down zone]]>
I know there is the mouse object that can return a global mouse down, but i think it could be really improved if we could have
"mouse down zone", ie linked to a contenair or patch, or i was thinking back of an 'invisible but active" object that could even overlay
two differents contenairs if set on top. dk if see what i mean, but i imagine it can be harder to set up. it's a bit like a kaos pad, where you can clic the independant cells or have a giant XY, tthis could be easy extended to work for all usine items.

example applications would be to turn a part of a patch active any time you clic on it, or easy higlight it.
actually for example if we have a patch with 16 buttons, plus other things, we need to track and collect every data to turn the patch on, we can use general mouse down but it would turn on all subpatchs on, and may results spikes, this can represent a lot of cpu vs what a simple mouse down zone return could allow ( and less wire)

another ex would be to make a draw mode on several switchs, set severals fader at once, or even listboxes, even if there are tools for that the modularity would have a lot of applications im sure, and it would make any item possible to have a mouse down, even if most have, ie on top of a fader we set a transparent (or invisible) rectangle that catch the mouse down, but still allow to control the fader.

i don't know how technically and if hard/possible, but it would be cool if we could set such a "mouse down transparent/invisible area"
linked to container, or independant, would be my suggestions if anyhow it can be done...

Statistics: Posted by 23fx23 — 02 Mar 2010, 23:49

]]> BrainModular BrainModular Users Forum 2010-03-06T11:40:08+02:00 https://brainmodular.org/forums/app.php/feed/topic/1972 2010-03-06T11:40:08+02:00 2010-03-06T11:40:08+02:00 https://brainmodular.org/forums/viewtopic.php?t=1972&p=12328#p12328 <![CDATA[mouse down zone]]> Statistics: Posted by 23fx23 — 06 Mar 2010, 10:40

]]> 2010-03-06T11:38:41+02:00 2010-03-06T11:38:41+02:00 https://brainmodular.org/forums/viewtopic.php?t=1972&p=12327#p12327 <![CDATA[mouse down zone]]> It's not easy to implement but far from impossible.
let me time for that.

Statistics: Posted by senso — 06 Mar 2010, 10:38

]]> 2010-03-06T09:24:34+02:00 2010-03-06T09:24:34+02:00 https://brainmodular.org/forums/viewtopic.php?t=1972&p=12301#p12301 <![CDATA[mouse down zone]]>
funny is it, i had same idea, instead of rec and storing many datas, why not simply be able to rec and replay "local" mouse moves to create complex automations, ie clic on 3 buttons, move a fader, set a lines array ect... then if the real hardware mouse is down on the object
it stops or re-rec the autom. but I imagine for more modularity this should be handled appart, kind of mouse rec/replay, and each local XY zone could be activated to be affected or not by the "virtual mouse", maybe...
as w7 return multitouch, we could even imagine each sub part to be able to receive/replay a diferent automation..

@ethnix: im not sure i understood , isn't it actually possible to "when you get CCx, make this sub container visible and active(patch active or let pass midi)? seems yes no? oh yup, maybe i catch now, a midi learn would avoid more complex patching?

Statistics: Posted by 23fx23 — 06 Mar 2010, 08:24

]]> 2010-03-05T21:40:29+02:00 2010-03-05T21:40:29+02:00 https://brainmodular.org/forums/viewtopic.php?t=1972&p=12282#p12282 <![CDATA[mouse down zone]]> It would be really cool then if we could also record that and then replay it as controller data for that specific container, inependant of the mouse...

Statistics: Posted by gurulogic — 05 Mar 2010, 20:40

]]> 2010-03-05T21:27:04+02:00 2010-03-05T21:27:04+02:00 https://brainmodular.org/forums/viewtopic.php?t=1972&p=12281#p12281 <![CDATA[mouse down zone]]>
i think it could be really improved if we could have
"mouse down zone", ie linked to a contenair or patch, or i was thinking back of an 'invisible but active" object that could even overlay
two differents contenairs
I'm agree but i believe it could more handy if this object could react also to midi.
My main idea: Imagine you control a patch with a midi foot controller, and within this patch, you have many subpatch with containers for each one. If an object is triggered by a midi cc, would be great to set the container to some kind of active mode, where it would receive midi, and others won't... Some kind of modularity for midi.

I know there is the rack/grid mode, but my main idea is to apply this to midi learn. You could control multiple subpatch with only a few controllers

Statistics: Posted by ethnix73 — 05 Mar 2010, 20:27

]]> 2010-03-03T00:49:50+02:00 2010-03-03T00:49:50+02:00 https://brainmodular.org/forums/viewtopic.php?t=1972&p=12194#p12194 <![CDATA[mouse down zone]]>
I know there is the mouse object that can return a global mouse down, but i think it could be really improved if we could have
"mouse down zone", ie linked to a contenair or patch, or i was thinking back of an 'invisible but active" object that could even overlay
two differents contenairs if set on top. dk if see what i mean, but i imagine it can be harder to set up. it's a bit like a kaos pad, where you can clic the independant cells or have a giant XY, tthis could be easy extended to work for all usine items.

example applications would be to turn a part of a patch active any time you clic on it, or easy higlight it.
actually for example if we have a patch with 16 buttons, plus other things, we need to track and collect every data to turn the patch on, we can use general mouse down but it would turn on all subpatchs on, and may results spikes, this can represent a lot of cpu vs what a simple mouse down zone return could allow ( and less wire)

another ex would be to make a draw mode on several switchs, set severals fader at once, or even listboxes, even if there are tools for that the modularity would have a lot of applications im sure, and it would make any item possible to have a mouse down, even if most have, ie on top of a fader we set a transparent (or invisible) rectangle that catch the mouse down, but still allow to control the fader.

i don't know how technically and if hard/possible, but it would be cool if we could set such a "mouse down transparent/invisible area"
linked to container, or independant, would be my suggestions if anyhow it can be done...

Statistics: Posted by 23fx23 — 02 Mar 2010, 23:49

]]>