This repository has been archived by the owner on Jan 2, 2025. It is now read-only.
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Fixes #10.
Now on pressing "up" or "down" buttons, it'll scroll to the top or the bottom. (Scrolling by 1 up or down is quite unintuitive, as it starts with selecting the 1st row, so if your screen fits 30 validators, you have to press down 29 times so it'll actually scroll on 30th, same with scrolling up).
I've also updated a splitVotes function to return the count of rows, as otherwise it may happen that columns do not have equal rows count, so when scrolling, one (fitting the screen) would be scrolled, and the other (not fitting the screen) would not, so we need to prefill the strings array with empty values to make it work properly