ArrayArrayArrayArrayArrayArrayArray
BrainModularBrainModular Users Forum2017-08-08T01:25:27+02:00https://brainmodular.org/forums/app.php/feed/topic/58242017-08-08T01:25:27+02:002017-08-08T01:25:27+02:00https://brainmodular.org/forums/viewtopic.php?t=5824&p=37502#p37502Statistics: Posted by ahonoe — 08 Aug 2017, 01:25
]]>
2017-08-08T01:12:29+02:002017-08-08T01:12:29+02:00https://brainmodular.org/forums/viewtopic.php?t=5824&p=37501#p37501Statistics: Posted by 23fx23 — 08 Aug 2017, 01:12
]]>2017-08-08T00:59:36+02:002017-08-08T00:59:36+02:00https://brainmodular.org/forums/viewtopic.php?t=5824&p=37500#p37500 On a related note, why not use the collision property? Isn't this what it's for?
]]>2017-08-08T00:03:48+02:002017-08-08T00:03:48+02:00https://brainmodular.org/forums/viewtopic.php?t=5824&p=37496#p37496 create a container, layout the 16 cellz (buttons) in the container, ordered from top left to botom right. collect all the mouse down output of buttons in an array. so when a button is clicked, checking the max position in the array returns the id of the clicked cell. thats the 'source', then i would make a virtual grid, a computation relating current mouse X,Y position in container returning wich cell id mouse is currently over, this is the 'target', so when draging a button we know wich cell is under. then on mouse down, from 0 to 1, get the desired 'propriety' for ex a value in an array, and when mouse is up, from1 to 0, copy this to the target, ie set array element value.
here is an exemple where i used polyphonic patch to go quicker, but hope can get the idea:
]]>2017-08-07T22:42:16+02:002017-08-07T22:42:16+02:00https://brainmodular.org/forums/viewtopic.php?t=5824&p=37495#p37495 I'm creating a 4 x 4 button grid where, "dragging and dropping" one button over another, copies its properties. I figured the best way to do this is use the collision property to determine which button is being dragged over. It doesn't seem to work for me. Collisions are not detected.
I've studied the GROOVE Physics patch and it shows the same problem. As soon as I set physics speed and gravity to 0 (to get my buttons to stay still), collisions are no longer detected.
Any suggestions? I'm open to another approach as well. Thanks.
]]>BrainModularBrainModular Users Forum2017-08-08T01:25:27+02:00https://brainmodular.org/forums/app.php/feed/topic/58242017-08-08T01:25:27+02:002017-08-08T01:25:27+02:00https://brainmodular.org/forums/viewtopic.php?t=5824&p=37502#p37502Statistics: Posted by ahonoe — 08 Aug 2017, 01:25
]]>2017-08-08T01:12:29+02:002017-08-08T01:12:29+02:00https://brainmodular.org/forums/viewtopic.php?t=5824&p=37501#p37501Statistics: Posted by 23fx23 — 08 Aug 2017, 01:12
]]>2017-08-08T00:59:36+02:002017-08-08T00:59:36+02:00https://brainmodular.org/forums/viewtopic.php?t=5824&p=37500#p37500 On a related note, why not use the collision property? Isn't this what it's for?
]]>2017-08-08T00:03:48+02:002017-08-08T00:03:48+02:00https://brainmodular.org/forums/viewtopic.php?t=5824&p=37496#p37496 create a container, layout the 16 cellz (buttons) in the container, ordered from top left to botom right. collect all the mouse down output of buttons in an array. so when a button is clicked, checking the max position in the array returns the id of the clicked cell. thats the 'source', then i would make a virtual grid, a computation relating current mouse X,Y position in container returning wich cell id mouse is currently over, this is the 'target', so when draging a button we know wich cell is under. then on mouse down, from 0 to 1, get the desired 'propriety' for ex a value in an array, and when mouse is up, from1 to 0, copy this to the target, ie set array element value.
here is an exemple where i used polyphonic patch to go quicker, but hope can get the idea:
]]>2017-08-07T22:42:16+02:002017-08-07T22:42:16+02:00https://brainmodular.org/forums/viewtopic.php?t=5824&p=37495#p37495 I'm creating a 4 x 4 button grid where, "dragging and dropping" one button over another, copies its properties. I figured the best way to do this is use the collision property to determine which button is being dragged over. It doesn't seem to work for me. Collisions are not detected.
I've studied the GROOVE Physics patch and it shows the same problem. As soon as I set physics speed and gravity to 0 (to get my buttons to stay still), collisions are no longer detected.
Any suggestions? I'm open to another approach as well. Thanks.