forge-draggable-windows

To add draggable floating windows to a ForgeUiContext application, wrap your context in a ForgeUiWindowContext each frame, then use window_begin and window_end to declare panels with drag handles, collapse toggles, and z-ordering.

Z-ordering for overlapping ForgeUi windows works by deferring per-window draw buffers and sorting them at frame-end, ensuring correct rendering order and input routing that blocks background interactions in overlap regions.

Yes, you can collapse and expand UI windows in ForgeUi to save screen space using built-in collapse toggles managed by ForgeUiWindowState, which tracks per-window state across frames.

The best way to handle input routing for stacked UI windows is using z-order-aware sorting that blocks interactions with background windows when overlapping regions exist, ensuring only the topmost window receives input.

Yes, you need a ForgeUiContext because draggable windows are initialized by wrapping it in a ForgeUiWindowContext, using APIs like forge_ui_wctx_init and forge_ui_wctx_begin to integrate panels into your existing application.

ForgeUi windows draw behind other panels when draw buffers are not deferred and sorted per-frame; correct rendering order requires using forge_ui_wctx_end to trigger frame-end sorting before final rendering.