When using the Combo Box dashboard item, it would be convenient that the default focus was set on the OK button so that the user would be able to arrow through the list, using the space bar to select/deselect items and pressing OK to have their dashboard reflect the changes. Currently the focus remains on the drop down and it simply closes the drop down with no filtering being performed. The user has to open the drop down up and either click OK or click on the line displaying the selected values.
Another option would be to have the closing of the drop down file the OK button clicked.
Thanks,
Todd
>> the user would be able to arrow through the list, using the space bar to select/deselect items and pressing OK to have their dashboard reflect the changes.
Would you please describe the required functionality in greater detail? Dashboard already behaves as you wish. The combo box uses arrows for navigation, the space bar for selection/deselection, Enter to accept changes and Esc to cancel them.
Attached is a small video sample that illustrates the ComboBox Item functionality.
John,
I would have expected when you clicked the Enter key, the grid would have filtered by the section that you selected. Watching the video, the drop down closes, but the grid does not get filtered.
Thanks,
Todd
Also, when you clicked Enter a second time, after the drop down was closed, it did not re-open drop down which is why I do not think that the current logic is consistent.
Hi Todd,
Thank you for the clarification, now I see the problem. The dashboard does not apply a selected filter when a popup is closed by the Enter key down. I have passed this ticket to our developers for further research.
Regarding your second question about re-opening the dropdown by the Enter key press. We have a separate ticket where we discuss how to improve this behavior: Dashboards - Provide a way to work with dashboards with a keyboard. I have added your requirement to that ticket. Feel free to post your other ideas regarding this functionality there. We will take them into account while introducing more rich keyboard support in the future.
Thanks John!