3 ms·
> No widget state needs to be kept. This is correct. Windows (which includes things like popups and dialogs) have "state behind your back", but widgets general
by formerly_proven 6y ago
> No widget state needs to be kept.
This is correct. Windows (which includes things like popups and dialogs) have "state behind your back", but widgets generally don't - at least I've never seen it in the code. 99 % of the examples given by other commenters are not handled by hidden widget state, but by g.activeID. As someone pointed out, changing IDs in the middle of an interaction is problematic for that reason (not because imgui fails to find the widget in its hidden tree of widgets, which doesn't exist).