Operation logic of the listbox when using hardware buttons.

[goddade]

I'm using three hardware buttons (prev, select, and next) to control my device. On the screen, there are several buttons and a listbox used to display a list of files.

I want to use prev or next to navigate/select files, and press select to open one.

The default logic is that I first need to navigate to the listbox and press select to give it focus before I can select an item.
After selecting an item and pressing select, the listbox only loses focus — there is no GSLC_TOUCH_UP_IN event, only two types: GSLC_TOUCH_FOCUS_PRESELECT and GSLC_TOUCH_FOCUS_SELECT.

[ImpulseAdventure]

HI @goddade --

It has been quite some time since I have used the hardware button navigation, but if I recall correctly, you should be able to map a button to the GSLC_ACTION_SET_REL action to get it to step through the listbox that received focus through the SELECT action.

If you could allocate a specific button to increment the listbox selection, then you can assign it like this:

gslc_InputMapAdd(&m_gui, GSLC_INPUT_PIN_ASSERT,   GSLC_PIN_BTN_C, GSLC_ACTION_SET_REL, +1);

If you have already used up all of your buttons in existing assignments, then you could assign the listbox navigation to a long-press event like this:

gslc_InputMapAdd(&m_gui, GSLC_INPUT_PIN_ASSERT,   GSLC_PIN_BTN_C_LONG, GSLC_ACTION_SET_REL, +1);

In the above example, the ACTION_SET_REL +1 should cause the focused listbox to advance its internal selection value by 1 (ie. relative position change).

Have a look at the ex27_m5_alpha.ino example to see how this was done.

Hope that helps!

[goddade]

I think the operation logic of the listbox very strange.

In a UI :

_______________
|  _______    |
|  | btn |    |
|  -------    |
| __________  |
| | item0  |  |
| | item1  |  |
| ----------  |
|             |
---------------

When the `btn is selected,

I press next, item0 in the listbox should be selected.

Then pressing next again should select item1.

Pressing "select" should trigger the listbox's touch_in event.

When item0 is selected,

I press "prev", it should directly select the "btn".

[ImpulseAdventure]

Hi @goddade -- apologies for the delay as I was out of town for some time. The following are some thoughts from what I recall of this portion of the implementation.

What you say makes sense for your example -- it would be convenient to have the next/prev controls advance through the elements on the page, and then descend into the compound listbox element.

As you have seen, the navigation is currently only active at either the page level, or within a compound element (like the listbox or keypad). Selecting a compound element at the page level (that is "editable") starts us to navigate within the compound element.

An alternate approach would have been to flatten all elements from a navigation perspective, both at the page level, and any compound elements.

While that may have worked intuitively for your listbox example, I think it would have been inconvenient for those who instantiate more complex compound elements like keypads. Flattening a keypad means that a user may have to press the "next" input 30 times just to skip over a keypad. Enabling the user to navigate a the high level first, then descend into a compound element (by "selecting" it first), was thought to be a suitable compromise, but clearly it doesn't make all display configurations as intuitive as you noted.

(If I misinterpreted your recommendation / question, please let me know)