mirror of
https://github.com/Rigellute/spotify-tui.git
synced 2026-04-27 00:25:53 +03:00
[GH-ISSUE #175] after upgrade cursor in search bar not aligned vertically correctly #90
Labels
No labels
bug
enhancement
good first issue
help wanted
pull-request
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
starred/spotify-tui#90
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Originally created by @stevensonmt on GitHub (Nov 30, 2019).
Original GitHub issue: https://github.com/Rigellute/spotify-tui/issues/175
Updated to latest release with cargo. After update the cursor in the search box is vertically centered on the bottom of the search box border while text appears centered vertically in the search box. See screenshot:

@Rigellute commented on GitHub (Dec 2, 2019):
Hmm... strange. Looks okay to me.

Not yet sure which commit might have messed with cursor position in your case.
@ghost commented on GitHub (Dec 2, 2019):
I'm not sure what caused this behavior but it seems to occur depending on terminal size.
51 lines in the window:

43 lines in the window:

@ghost commented on GitHub (Dec 2, 2019):
I found that the margin of main layout is set to 1 or 0 depending on terminal height (line 142 in
src/ui/mod.rs) and this seems to cause the problem. To fix it, fix margin size to 0 or 1 regardless of terminal height or change cursor position when terminal height is lower than 45. If anyone does not fix it, I will do.@stevensonmt commented on GitHub (Dec 2, 2019):
Can confirm that larger terminal height fixes the cursor alignment. As for which commit, I don't know but I've got version 0.10.0 - 2019-11-30 showing up on the initial screen.
@Rigellute commented on GitHub (Dec 2, 2019):
@echoSayonara ah yes of course!! I will PR a fix a bit later today