my application Horizon EDA uses spinbuttons in the scale tool, among other things. The interaction goes like this:
In the scale tool, the user can open the non-modal window shown below. Adjusting the spinbutton (
value-changed signal) will immediately update the scale of the objects in the background. Pressing enter (
activate signal) confirms the entered scale and closes the window. This gets us these behaviors:
- User changes spinbutton value using mouse wheel or up/down keys until they’re at the correct value and press enter to confirm. Okay.
- User types in new scale, presses enter, dialog goes away without a way to make further changes. Not okay.
I’m now looking for a way to tell apart pressing enter in the second case where it causes user input to be parsed from the first case so I can get this behaviour:
User types in value, presses enter, spinbutton parses value, emits
value-changed, objects update, user is happy with the outcome, presses enter again to confirm.
I had look at the sequence of the
value-changed signals, but the sequence is the same in both cases.
I hope that my explanations weren’t too confusing.
EDIT: Why does a bot(?) think this spam?