sky_line/Slipstream

Fork 1

Using up/down arrow keys to navigate Debug Settings dropdown has unexpected effects #943

New issue

Open

opened 2026-10-22 19:45:13 +00:00 by Hemiva · 3 comments

Hemiva commented

2026-10-22 19:45:13 +00:00

Environment

Slipstream Beta 1.4.0.5 (64bit) (SSE4_2)
Microsoft Windows 11 64-bit (Build 22621.4317)

Description

In the Debug Settings window, when you have an option in the Setting list selected and press the Up/Down Arrow button on your keyboard, the selected item jumps in a somewhat unexpected way.

Instead of always highlighting the option that's above the one you selected, pressing the Up Arrow seems to always jump to the first item on the list that starts with a R. And the behavior of the Down Arrow depends on if you have a search term on the search bar. If you don't, it will jump to QAMode for some reason, according to my testing. If you do, it seems to work properly.

Included is a video of the bug. I pressed Up and Down a few times through the recording.

Reproduction steps

Open Debug Settings (can be done through Advanced > Show Debug Settings).
Click on any item on the Setting list, to the left.
Press the Up Arrow or the Down Arrow on your keyboard. The highlighted option should jump around in a manner described previously.

### Environment Slipstream Beta 1.4.0.5 (64bit) (SSE4_2) Microsoft Windows 11 64-bit (Build 22621.4317) ### Description In the Debug Settings window, when you have an option in the Setting list selected and press the Up/Down Arrow button on your keyboard, the selected item jumps in a somewhat unexpected way. Instead of always highlighting the option that's above the one you selected, pressing the Up Arrow seems to always jump to the first item on the list that starts with a R. And the behavior of the Down Arrow depends on if you have a search term on the search bar. If you don't, it will jump to QAMode for some reason, according to my testing. If you do, it seems to work properly. Included is a video of the bug. I pressed Up and Down a few times through the recording. ### Reproduction steps 1. Open Debug Settings (can be done through Advanced > Show Debug Settings). 2. Click on any item on the Setting list, to the left. 3. Press the Up Arrow or the Down Arrow on your keyboard. The highlighted option should jump around in a manner described previously.

SlipstreamViewer_82lV2WqVCq.mp4

1.2 MiB

Hemiva added the

triage

bug

labels

2026-10-22 19:45:13 +00:00

Hemiva added this to the Slipstream project

2026-10-22 19:45:13 +00:00

sky_line referenced this issue from a commit

2026-10-25 04:56:50 +00:00

#943: Debug Settings list is sorted by name so Up/Down step to the adjacent row

sky_line referenced this issue from a commit

2026-10-25 04:56:56 +00:00

#943: Debug Settings list is sorted by name so Up/Down step to the adjacent row

Hemiva commented

2026-10-25 06:06:39 +00:00

Author

Despite claims on the release notes that Release 1.4.0 fixed this issue, it's still happening. The Up/Down Arrow buttons still make the selected item in the Debug Settings list to jump around as described.

Despite claims on the release notes that **Release 1.4.0** fixed this issue, it's still happening. The Up/Down Arrow buttons still make the selected item in the Debug Settings list to jump around as described.

sky_line commented

2026-10-25 07:00:25 +00:00

Owner

Reopened: the reporter (Windows) says Up/Down still jump to odd rows. The owner can't reproduce it on Linux.

The fix in 1.4.1 (de447ecbe9 on dev, 4fe6e36540 on release/1.4) sorted the Debug Settings list by name once in postBuild, on the assumption that hash-map row order was the cause. Next suspects:

The sort may not persist. updateList() re-adds rows after postBuild, and when the search filter changes, the rows are rebuilt; the one-time sortByColumnIndex may not apply to rows added later.
Windows-specific key handling. Key repeat or double delivery of arrow keys under the SDL window on Windows (each press moving two rows).
Selection commit side effects. Selection commits on every change, which may rebuild the list and lose the visual position.

Ask the reporter for the 1.4.1 build number, whether it happens with an empty search box and with a search term, and whether one press moves exactly two rows or jumps somewhere random.

Reopened: the reporter (Windows) says Up/Down still jump to odd rows. The owner can't reproduce it on Linux. The fix in 1.4.1 (de447ecbe9 on dev, 4fe6e36540 on release/1.4) sorted the Debug Settings list by name once in postBuild, on the assumption that hash-map row order was the cause. Next suspects: - **The sort may not persist.** updateList() re-adds rows after postBuild, and when the search filter changes, the rows are rebuilt; the one-time sortByColumnIndex may not apply to rows added later. - **Windows-specific key handling.** Key repeat or double delivery of arrow keys under the SDL window on Windows (each press moving two rows). - **Selection commit side effects.** Selection commits on every change, which may rebuild the list and lose the visual position. Ask the reporter for the 1.4.1 build number, whether it happens with an empty search box and with a search term, and whether one press moves exactly two rows or jumps somewhere random.

Hemiva commented

2026-10-25 07:29:43 +00:00

Author

@sky_line wrote in #943 (comment):

Reopened: the reporter (Windows) says Up/Down still jump to odd rows. The owner can't reproduce it on Linux.

The fix in 1.4.1 (de447ecbe9 on dev, 4fe6e36540 on release/1.4) sorted the Debug Settings list by name once in postBuild, on the assumption that hash-map row order was the cause. Next suspects:
* **The sort may not persist.** updateList() re-adds rows after postBuild, and when the search filter changes, the rows are rebuilt; the one-time sortByColumnIndex may not apply to rows added later.

* **Windows-specific key handling.** Key repeat or double delivery of arrow keys under the SDL window on Windows (each press moving two rows).

* **Selection commit side effects.** Selection commits on every change, which may rebuild the list and lose the visual position.
Ask the reporter for the 1.4.1 build number, whether it happens with an empty search box and with a search term, and whether one press moves exactly two rows or jumps somewhere random.

It happens both with an empty search box and a search term, in the ways that were described in the original description.
One Up/Down press doesn't move exactly two rows, it jumps to rows as described in the original description.
The behavior described in the original description persists even in the newer version of the viewer.

@Hemiva wrote in #943 (comment):

Instead of always highlighting the option that's above the one you selected, pressing the Up Arrow seems to always jump to the first item on the list that starts with a R. And the behavior of the Down Arrow depends on if you have a search term on the search bar. If you don't, it will jump to QAMode for some reason, according to my testing. If you do, it seems to work properly.

@sky_line wrote in https://git.slipstreamviewer.org/sky_line/Slipstream/issues/943#issuecomment-9833: > Reopened: the reporter (Windows) says Up/Down still jump to odd rows. The owner can't reproduce it on Linux. > > The fix in 1.4.1 (de447ecbe9 on dev, [`4fe6e36540`](/sky_line/Slipstream/commit/4fe6e36540) on release/1.4) sorted the Debug Settings list by name once in postBuild, on the assumption that hash-map row order was the cause. Next suspects: > > * **The sort may not persist.** updateList() re-adds rows after postBuild, and when the search filter changes, the rows are rebuilt; the one-time sortByColumnIndex may not apply to rows added later. > > * **Windows-specific key handling.** Key repeat or double delivery of arrow keys under the SDL window on Windows (each press moving two rows). > > * **Selection commit side effects.** Selection commits on every change, which may rebuild the list and lose the visual position. > > > Ask the reporter for the 1.4.1 build number, whether it happens with an empty search box and with a search term, and whether one press moves exactly two rows or jumps somewhere random. It happens both with an empty search box and a search term, in the ways that were described in the original description. One Up/Down press doesn't move exactly two rows, it jumps to rows as described in the original description. The behavior described in the original description persists even in the newer version of the viewer. @Hemiva wrote in https://git.slipstreamviewer.org/sky_line/Slipstream/issues/943#issue-954: > Instead of always highlighting the option that's above the one you selected, pressing the Up Arrow seems to always jump to the first item on the list that starts with a R. And the behavior of the Down Arrow depends on if you have a search term on the search bar. If you don't, it will jump to QAMode for some reason, according to my testing. If you do, it seems to work properly.

No milestone

No project

No assignees

2 participants

Notifications

Due date

The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference

sky_line/Slipstream#943

No description provided.

Rows
Columns