nvglucifer
nvglucifer
This is a feature request. I made first picture with paint.
I think it need to use drag_rect's callback instead of plot's callback. ```python with dpg.tree_node(label="Drag Rects"): def drag_query(sender, app_data, user_data): # FIXME: app_data always None ? x1, y1, x2, y2...
Related to #2409 and #2459 . It might caused by mvPlotting.cpp line#513 - commit bbd1df6  If you replace it with this line (it was there before): `child->draw(drawlist, ImPlot::GetPlotPos().x, ImPlot::GetPlotPos().y);`...
@nkraemer2 I would modify mvPlotting.cpp line#513 to use `child->draw(drawlist, ImPlot::GetPlotPos().x, ImPlot::GetPlotPos().y);` And for custom series to not crash, I would remove its section about `// Begin a popup for a...
My bad for not using "Copy permalink" in previous comment. https://github.com/hoffstadt/DearPyGui/blob/d3577817fa69d6b5a8b56fde023b0200c0ff83ef/src/mvPlotting.cpp#L2354-L2369
@v-ein Yes, I will modify a point about `payload_type` being optional.
For drop callback to work, `payload_type` need to be specified the same. Even droppable, you can accept/discard data depend on your `user_data`. `user_data` of drag/drop callback, or `dpg.get_item_user_data(a_drag_payload_id)` might help....
```python import dearpygui.dearpygui as dpg dpg.create_context() def drag_cb(sender, app_data, user_data): # sender is btn_drag # app_data is btn_drag (value from drag_data) # do some configure(drawing_item), animation print(sender, app_data, user_data) ......