Allow scroll scoreboard(64 players) #3240

[teeworlds-mirror]

upstream: https://www.github.com/teeworlds/teeworlds/pull/3240

[ChillerDragon]

The current scoreboard is really bad and we should address that in teeworlds-community. But I personally am #TeamNoPages

[Bamcane]

I need to fix a bug

[Bamcane]

OK now

[BlaiZephyr]

i personally dont like the use of w as the actual scrollkey - a few friends of mine and me included have that key bound for something else already (most commonly used as free-view from what i can tell) - should we really hardcode it to a key that is commonly bound to something else already? - i also wonder if this interferes if the key is already bound to something else

[Robyt3]

I and probably many other players use w to jump so that's probably not a good hotkey to pick for this.

I don't like the static scrolling either, it's not great to follow entries with your eyes. If we want something to scroll it should be smooth scrolling like all scrollregions and listboxes.

[Bamcane]

I and probably many other players use w to jump so that's probably not a good hotkey to pick for this.

I don't like the static scrolling either, it's not great to follow entries with your eyes. If we want something to scroll it should be smooth scrolling like all scrollregions and listboxes.

For the first problem:
That's just a default key w that you could bind it to another keys, so i think this is not a big problem so far.

For the second problem:
Maybe we could make it to a list, so that we could scroll it more smoothly. To do this, i will update the code in 5 days (Maybe later).

[Bamcane]

I had a better idea that we should keep pressing the key, then use mouse to scroll it.
So does anyone use the key 'mouse3'?

[BlaiZephyr]

pressing the mousewheel while Scrolling feels weird IMPO, But it could Work i guess

[BlaiZephyr]

You pulled latest so you now have a 2K Line diff btw :P

[ChillerDragon]

You pulled latest so you now have a 2K Line diff btw :P

This is a pr upstream so it should be on the latest change. I just updated the community fork so the diff is now gone (#119).