Unable to access favorite channel from dashboard with index >9

[elcoco]

First of all thank you for this amazing project!

Describe the bug:
Since the dashboard screen only accepts a single number it is not possible to access any favorite channels higher than the 10th channel.
Could possibly be solved by using [a-z][A-Z] instead of [0-9].

To Reproduce:
Configure more than 10 channels in the config file:

[frontend]
favorite_channels = ["channel0", "channel1", ..., "channel10"]

Expected behavior:
Have a way to access a favorite channel with index >9 by using a keyboard stroke.

System:

• Twitch-tui version: 2.6.17 (using arch package: extra/twitch-tui 2.6.17-1)
• Operating System: Arch Linux w/ kernel 6.12.7
• Terminal: kitty 0.38.1
• Shell: zsh 5.9-5

[Xithrius]

Thanks for the issue! That ain't good, I'll get around to this as soon as I can.

[Xithrius]

@elcoco Sorry it's been a bit, focused on IRL stuff. I believe I have a solution to this, which I think I saw in a neovim dashboard at some point. As an example, let's say there's a large amount of channels in your favorites, like 123. If you hit 1, then the string "1" is matched to a number of a channel, being the first one. If you hit two, the string gets a "2" concatenated to it, so the channel with number 12 is now selected. Then hitting 3 would get you the very last channel, 123. Hitting enter at any point would select the relevant channel of the number, and connect to it. From a user perspective, does this sound sane? Would greatly appreciate your input. Thanks!

[elcoco]

Hey, Thanks for coming back to the issue.

It may be a little confusing for the user if you make pressing enter a requirement. I think the user won't expect to have to
press enter to finalize input.
You could fix that by giving some visual feedback.

Another solution could be to add a bit of a timeout after each input where the program waits for more input.
So if the user would enter 1, then 2, the application would accept 12 as the input if there is no more input from the user before the timeout is over.
This is more or less how the leader key in vim is implemented. I believe vim uses a default timeout of 1 second.
This may be annoying for some users because the user would have to wait a second before final input is accepted.
By pressing the enter key as you've described in your example you could enable the user to accept the input without having to wait for the timeout to be over.
You can of course completely skip this behavior if there are less than 10 channels configured.

A downside is that it does make implementation a little more complicated though.

[Xithrius]

The delay is a pretty good idea, but yeah it'll definitely be a bit complicated to implement. Of course I'll also include configs and all for the user to modify if they want. I'll see what I can do.

[kaizoplant]

should be fixed by #686