SCENARIO: ALEX or LOGAN wants to reduce the sole reliance on click-and-point reactivity within the gui and have the most common editing actions mapped to keyboard keys in such a way that perfectly replicates the effect of pressing the corresponding actionButton in the gui.
GIVEN: ALEX or LOGAN have appropriately selected a subset of points to edit.
WHEN: ALEX or LOGAN hits the a key on their keyboard
THEN: IBI_VizEdit should react the same as if they had clicked on the Average actionButton`.
Lastly here is the first draft of a function that returns the javascript text to be inserted into the UI portion of the application. It is almost certainly going to need some work. (think also about how to mock key presses for unit tests).
SCENARIO: ALEX or LOGAN wants to reduce the sole reliance on click-and-point reactivity within the gui and have the most common editing actions mapped to keyboard keys in such a way that perfectly replicates the effect of pressing the corresponding
actionButton
in the gui.GIVEN: ALEX or LOGAN have appropriately selected a subset of points to edit.
WHEN: ALEX or LOGAN hits the
a
key on their keyboardTHEN:
IBI_VizEdit
should react the same as if they had clicked on theAverage
actionButton`.Notes:
a
= Average;c
= Combine;d
= Divide;i
= Insert; andr
= Removehttps://github.com/matgbar/IBI_VizEdit/blob/07d2bae820a39b8febcf2793d845c703062f9a9b/R/hotkey_utils.R#L11-L32