[improve] pressing Enter on keyboard launches an AO (undesirable about bfx-hf-ui HOT 3 CLOSED

UX volatility, observed after the ALIAS field has been introduced.'

When typing the descriptions in, the user might hit the ENTER key due to personal habits / previous other workflows unexpectedly. In the EXECUTE ORDER pane, this will launch the order unintentionally. While the numerical setup is still in progress

Come to think of it, this may be the true reason behind some 'spontaneous' AO triggers which had been observed before (never reported, unable to reproduce).

suggestion

De-activate the default ENTER key function on all panels / modals unless there is a clear indication to the user that a certain button has become hot.

Since we do not have that mouse over / focus showing over the individual elements (not really needed) better just to deactivate the ENTER. Optimizing GUI for keyboard control would require that and Honey will still do great for a long time even without it.

Otherwise, if pressing ENTER while editing a data value, the desired behaviour is not clear. Jumping to the next input field (same as TAB) would be OK.

from bfx-hf-ui.

added to the pipeline. will be disabled until a fully functional key-mapping feature exists

from bfx-hf-ui.

Stale issue message

from bfx-hf-ui.