Drag and drop in new device

[pongasoft]

How is this possible exactly with the current SDK?

Am I missing something here? It looks like drag and drop across custom displays even?

Screen Shot 2022-06-29 at 06.00.55.png

[deeplink]

I think it's just one custom display? Made to look like two

[buddard]

I did not implement this, but there are two adjacent custom displays: One for the grid and piano roll, and one for the sequencer. They both track the same drag-related properties and make sure to add the correct coordinate offsets so they both draw the "chord clip" in the same place for a seamless handover effect.

Looks pretty cool!

[Billy+]

I did not implement this, but there are two adjacent custom displays: One for the grid and piano roll, and one for the sequencer. They both track the same drag-related properties and make sure to add the correct coordinate offsets so they both draw the "chord clip" in the same place for a seamless handover effect.

Looks pretty cool!

Definitely looks pretty cool - one of if not the best designs for player devices and the sequencer lengths are spot on. If only they would sort out Pattern Mutator

[orthodox]

Simple stuff, just keep track of the dragged object position as properties in all custom displays.

[pongasoft]

Simple stuff, just keep track of the dragged object position as properties in all custom displays.

I don't believe it is "simple". It is a trick. A very clever trick mind you, but a trick nonetheless. It means that every developer who wants to do the same, needs to do something similar (which is not documented, so reinvent the wheel) and manage it manually. It also highly constrain the design as the custom displays must be touching each other otherwise the dragged object will just vanish.

This leads to inconsistencies (looks ugly/broken) as can be seen in this screenshot which clearly shows the boundaries of the custom displays...

Screen Shot 2022-06-30 at 05.40.43.png

[orthodox]

Simple stuff, just keep track of the dragged object position as properties in all custom displays.

I don't believe it is "simple". It is a trick. A very clever trick mind you, but a trick nonetheless. It means that every developer who wants to do the same, needs to do something similar (which is not documented, so reinvent the wheel) and manage it manually. It also highly constrain the design as the custom displays must be touching each other otherwise the dragged object will just vanish.

Ok, it may be a trick, but it is very very easy to implement. Takes almost nothing in terms of the lines of lua code. Both displays use the same function to draw the object being dragged. I was more impressed with the trick where you can drag the arrow from the modulation matrix to any destination control on the device. That requires having a map of all the controls in display.lua. While this new trick needs only the relative position of one display to the other one.