This is not 100% symmetric with StartMouseMovingWindow(). We do NOT clear ActiveID, because: - It would lead to rather confusing recursive code paths. Caller can call ClearActiveID() if desired. - Some code intentionally cancel moving but keep the ActiveID to lock inputs (e.g. code path taken when clicking a disabled item).
| 5293 | // - It would lead to rather confusing recursive code paths. Caller can call ClearActiveID() if desired. |
| 5294 | // - Some code intentionally cancel moving but keep the ActiveID to lock inputs (e.g. code path taken when clicking a disabled item). |
| 5295 | void ImGui::StopMouseMovingWindow() |
| 5296 | { |
| 5297 | ImGuiContext& g = *GImGui; |
| 5298 | |
| 5299 | // [nb: docking branch has more stuff in this function] |
| 5300 | |
| 5301 | g.MovingWindow = NULL; |
| 5302 | } |
| 5303 | |
| 5304 | // Handle mouse moving window |
| 5305 | // Note: moving window with the navigation keys (Square + d-pad / Ctrl+Tab + Arrows) are processed in NavUpdateWindowing() |
nothing calls this directly
no outgoing calls
no test coverage detected