mirror of
https://github.com/rivo/tview.git
synced 2026-04-26 13:25:51 +03:00
[GH-ISSUE #521] Form border lines are rendered white on white since tcell update #381
Labels
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
starred/tview#381
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 @berrange on GitHub (Nov 5, 2020).
Original GitHub issue: https://github.com/rivo/tview/issues/521
If I build the 'demos/form/main.go' demo program and run, the form used to have a double line border around it with background in black and lines in white, along with the title text in white.
Since the update to tcell in
@rivo commented on GitHub (Nov 17, 2020):
I cannot reproduce this with the latest version:
Which terminal / OS are you using?
@berrange commented on GitHub (Nov 18, 2020):
This is with latest tview source, cloned right now, and then building from the git root
I'm using Fedora 33, x86_64, with GNOME Terminal (gnome-terminal-3.38.1-1.fc33.x86_64).
Normally I'm using a white-ish background, and black text, but for this screenshot I've set my terminal background to pink, to make it obvious that the borders are inheriting the terminal's default background colour instead of any tview colour theme:
@joegrasse commented on GitHub (Mar 4, 2021):
I am also running into this issue. With me though, it is anything that has a boarder. I can set the color of the border line with
SetBorderColor, but there is actually a color behind (around) the line that matches the terminal color (black).Here is another example.
@rivo commented on GitHub (Mar 12, 2021):
Please check out https://github.com/rivo/tview/issues/520#issuecomment-797659408 and let me know if the latest version resolves your issue.
@mevdschee commented on GitHub (Mar 13, 2021):
@joegrasse Seems fixed to me.
@rivo commented on GitHub (Mar 13, 2021):
Great! Thanks for the feedback!
@joegrasse commented on GitHub (Mar 15, 2021):
Yes, fixed for me as well.