Drag and drop

ImGui’s drag-drop API is two paired Begin*/End* calls: one attached to the previously submitted item that’s being dragged, one attached to the previously submitted item that’s receiving. Both Begin* calls return false unless ImGui’s internal drag state machine says “drag-active” or “hover-over-target with payload”; calling End* when Begin* returned false is undefined behavior.

The boost layer ships two [container]``s ``drag_drop_source and drag_drop_target — that gate their bodies on the corresponding Begin* return. Payload set/accept stay raw calls inside the body because the data is caller-owned and crosses widget boundaries.

Source: examples/features/drag_drop.das.

Walkthrough

The recording introduces the source button and the drop target, then performs a real drag of the source onto the target. On release the target accepts the MY_INT payload — Target received value flips to 42 and Drops accepted ticks to 1. The drag is synthesized through the same synth-mouse pipeline a test would use, and the recording asserts the drop actually landed (see Driving from outside below).

 1options gen2
 2
 3require imgui/imgui_harness
 4
 5// =============================================================================
 6// FEATURE: drag_drop — [container]s drag_drop_source + drag_drop_target.
 7//          Both gate their body on ImGui's internal drag-drop state machine.
 8//          Bodies call raw SetDragDropPayload / AcceptDragDropPayload —
 9//          payload data is caller-owned and crosses widget boundaries.
10// SHOWS:   drag SOURCE_BTN onto TARGET_BTN; TARGET_BTN's body accepts the
11//          "MY_INT" payload and writes it into RECEIVED. DROP_COUNT
12//          increments on each successful release-over-target.
13// STANDALONE: daslang.exe modules/dasImgui/examples/features/drag_drop.das
14// HEADLESS:   daslang.exe modules/dasImgui/examples/features/drag_drop.das -- --headless --headless-frames=60
15// LIVE:       daslang-live modules/dasImgui/examples/features/drag_drop.das
16// =============================================================================
17
18var PAYLOAD_VALUE : int = 42
19var RECEIVED : int = 0
20var DROP_COUNT : int = 0
21
22[export]
23def init() {
24    harness_init("drag_drop — source + target", 720, 480)
25    var io & = unsafe(GetIO())
26    unsafe(GetStyle()).FontScaleMain = 1.5
27}
28
29[export]
30def update() {
31    if (!harness_begin_frame()) return
32    harness_new_frame()
33
34    SetNextWindowSize(ImVec2(660.0, 420.0), ImGuiCond.Always)
35    window(MAIN_WIN, (text = "drag_drop", closable = false,
36                      flags = ImGuiWindowFlags.None)) {
37        text("Drag the SOURCE button onto the TARGET button.")
38        separator()
39
40        // Source: a normal button. Body runs only on active drag.
41        button(SOURCE_BTN, (text = "SOURCE"))
42        drag_drop_source(SOURCE_DD, (flags = ImGuiDragDropFlags.None)) {
43            unsafe {
44                SetDragDropPayload("MY_INT", addr(PAYLOAD_VALUE),
45                                   uint64(typeinfo sizeof(PAYLOAD_VALUE)),
46                                   ImGuiCond.Once)
47            }
48            text("Dragging int: {PAYLOAD_VALUE}")
49        }
50
51        // 40 px gap between the source and target buttons.
52        // Note: same_line's named-tuple destructure is POSITIONAL; the
53        // first field is offset_from_start_x, the second is spacing.
54        // `(spacing = 40.0f)` alone would bind 40 to offset_from_start_x
55        // and let TARGET overlap SOURCE -- the source/target hit-test
56        // tie breaks toward TARGET, so the drag fails to start.
57        same_line((offset_from_start_x = 0.0f, spacing = 40.0f))
58
59        // Target: a normal button. Body runs only when payload-bearing drag hovers.
60        button(TARGET_BTN, (text = "TARGET"))
61        drag_drop_target(TARGET_DD) {
62            let payload = AcceptDragDropPayload("MY_INT", ImGuiDragDropFlags.None)
63            if (payload != null) {
64                unsafe {
65                    RECEIVED = (reinterpret<int? const>(payload.Data))[0]
66                }
67                DROP_COUNT++
68            }
69        }
70
71        separator()
72        text("Source payload value: {PAYLOAD_VALUE}")
73        text("Target received value: {RECEIVED}")
74        text("Drops accepted: {DROP_COUNT}")
75    }
76
77    harness_end_frame()
78}
79
80[export]
81def shutdown() {
82    harness_shutdown()
83}
84
85[export]
86def main() {
87    init()
88    while (!exit_requested()) {
89        update()
90    }
91    shutdown()
92}

Requires

Same backend + boost layer as the other container tutorials, plus the drag_drop_source / drag_drop_target macros from imgui/imgui_containers_builtin (which is already required by the container family).

Source side

Attach a drag_drop_source immediately after the source widget. ImGui implicitly binds it to the previously submitted item:

button(SOURCE_BTN, (text = "SOURCE"))
drag_drop_source(SOURCE_DD, (flags = ImGuiDragDropFlags.None)) {
    unsafe {
        SetDragDropPayload("MY_INT", addr(PAYLOAD_VALUE),
                           uint64(typeinfo sizeof(PAYLOAD_VALUE)),
                           ImGuiCond.Once)
    }
    Text("Dragging: {PAYLOAD_VALUE}")
}

The body runs only while the drag is active — after the user has pressed the mouse on SOURCE_BTN and dragged past ImGui’s io.MouseDragThreshold. Inside the body:

  • SetDragDropPayload(type, data, size, cond) publishes the payload. type is a short string (max 32 chars) that the target compares against; data is a raw pointer with caller-controlled lifetime (ImGui copies it into its internal buffer on each call, so a stack pointer is fine inside the body).

  • Any rendering call (Text, Image, etc.) draws the drag preview tooltip that follows the cursor.

Target side

Attach a drag_drop_target immediately after the target widget:

button(TARGET_BTN, (text = "TARGET"))
drag_drop_target(TARGET_DD) {
    let payload = AcceptDragDropPayload("MY_INT", ImGuiDragDropFlags.None)
    if (payload != null) {
        unsafe {
            RECEIVED = (reinterpret<int? const>(payload.Data))[0]
        }
    }
}

The body runs only while a drag is hovering this widget. Inside:

  • AcceptDragDropPayload(type, flags) returns a non-null ImGuiPayload? on the frame the user releases over the target with a payload whose type matches type; otherwise it returns null (including on every frame the drag is hovering but not yet dropped).

  • The returned payload’s Data field is a void? constreinterpret<T? const>(payload.Data)[0] reads the typed value back.

Driving from outside

Playwright exposes a high-level drag_to that bridges source-bbox → target-bbox automatically:

require imgui/imgui_playwright
drag_to(app, "MAIN_WIN/SOURCE_BTN", "MAIN_WIN/TARGET_BTN", steps = 8)

It reads both bboxes from a fresh snapshot, computes (dx, dy) = target_center - source_center, and composes an imgui_mouse_play timeline — warp to the source, press, steps-scaled interpolated moves to the target, release. ImGui’s drag state machine activates around the second or third move (depending on io.MouseDragThreshold) and resolves on release.

The lower-level drag(app, target, dx, dy, steps) is available when you want absolute offsets — useful for testing drag-without-drop or drag-cancel paths.

Verifying the drop. drag_drop_target surfaces a running accepted count in its telemetry payload — it counts the drops ImGui actually delivers (GetDragDropPayload().Delivery), so a driver or test can assert the drop landed without reaching into the example’s caller-owned globals:

drag_to(app, "MAIN_WIN/SOURCE_BTN", "MAIN_WIN/TARGET_BTN")
// accepted ticks 0 -> 1 on a real delivery over the target
wait_for_payload_value(app, "MAIN_WIN/TARGET_DD", "accepted", 1, 300)

Next steps

That’s the last container tutorial. The next walkthrough switches focus to live-reload internals.

See also

Full source: examples/features/drag_drop.das

Integration test: tests/integration/test_drag_drop.das.

Boost macros — the macro layer.

Containers — the container family in general.