90b1fbe2f8
The gesture was handed the pointer's frame and threw it away, creating at the playhead instead; and the palette row carried :lane? only once its track existed, so the first double-click on a palette lane -- the one that has to make the track -- dispatched nothing at all. Both are one rule now. ::new-symbol-at uses the frame it is given and resolves every row through drop-destination, with the destination deciding what is created: a clip of a palette track is a palette symbol, a clip of any other lane is blank. A row with no path of its own resolves to the symbol it names, which is what lets a palette track -- hanging off its owner by :palette-track rather than placed in it -- be reached without a special case; it also stops a palette cel's slide resolving against the open symbol and looking like a transfer out of the track. The one thing left that knows about palettes is materializing the lane a palette row names before anything asks where the row leads. Co-Authored-By: Claude Opus 5 <noreply@anthropic.com> |
||
|---|---|---|
| .. | ||
| arthur | ||
| browser | ||