Widgets returning true only when they change value?

[ongamex]

I'm trying to implement a simple Undo/Redo for my level editor.
I use ImGui::DragFloat (and others..) to manipulate the values that I need to have history.
These values are updated when ImGui::DragFloat (and others) returns true.

The problem that I have is that ImGui::DragFloat returns true even when 'sliding' the widget, I want to get notified somehow when to user stopped interacting with the ImGui::DragFloat (for example edited with the keyboard and hit enter, or the user released the mouse) in order to create an undoable state only then.

is there a way to achieve this?

[ocornut]

See #820 Those helpers haven't been added to the main branch yet so we can keep this new issue open.

[ongamex]

Thanks for the quick replay,

For the hack, it's a pity that it does not work with PushID and thus with DragFloat2/3/4.

[ocornut]

It's not to do with PushId(), there was a problem with IsItemActive() within group which was fixed so it may just work now.

…

On 29 Dec 2016, at 18:02, ongamex ***@***.***> wrote: Thanks for the quick replay, For the hack, it's a pity that it does not work with PushID and thus with DragFloat2/3/4. ― You are receiving this because you commented. Reply to this email directly, view it on GitHub, or mute the thread.

[ongamex]

Yeah, the way I solved my problem is using the "hack" from #820 and basically duplicating the code for DragFloatN and tweaking it a little bit.

Here is the code just in case someone else needs it:
https://gist.github.com/ongamex/155c8b64186a4f5f41353dbfccbb018e

[ocornut]

So the problem is that the proposed solution for IsItemActiveLastFrame doesn't work for groups because the way EndGroup() makes IsItemActive() works is a little dodgy in the first place.
So we can aim at providing an official IsItemActiveLastFrame (even as an internal) function that works for groups (I don't know how to implement it yet but will find a solution) and expose IsItemJustReleased() publicly.

[eliasdaler]

Is there any progress in this? I think that it's a pretty important feature to have, seeing how many GUIs use this behavior as "PropertyChanged" event.

[ocornut]

It's not as easy as it sounds because of the architecture of InputText, which needs to be cleaned up. No progress on it yet.

[eliasdaler]

Okay, maybe anything I could help with? Or maybe changes are going to be pretty radical?

[ocornut]

@ongamex @eliasdaler
We now have a better solution for this issue that handle groups and multi-elements widget.
See there:
#1875 (comment)
(Closing this topic, please report/discuss in #1875 onward! Thanks!)