-
-
Notifications
You must be signed in to change notification settings - Fork 1.4k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Horizontal Line Rendering Issues with widget.NewSeparator() and canvas.Line #5348
Comments
Lines slope diagonally from top left to bottom right if not managed specifically for line placement. Putting a line into a container is unlikely to do exactly what you want, that is what the separator does. What issues did you have when you placed the separator into a container? In an HBox they will display vertically as they are separating items in a horizontal row of content... |
Thank you for your response! I understand that widget.NewSeparator adapts its orientation based on the parent layout. I tried the following configurations:
but, the separator is not visible. Do you recommend a more straightforward way to achieve this behavior? Thank you again for your guidance! |
I don't understand what you are trying to do. A separator inside a VBox inside an HBox will have minimum width and height, I.e. probably only a pixel in size. I don't understand how a separator in a horizontal arrangement of widgets would have a "vertical alignment"... what does that even mean? |
It looks like that is a separator with a label on top - a Stack container allows you to put one thing over another |
It might not be the most optimal solution, but I found a hacky way to achieve this layout.
|
Checklist
Describe the bug
I am encountering consistent issues rendering horizontal lines in Fyne. Neither widget.NewSeparator() nor canvas.Line produces a proper horizontal line in my application. The lines either render vertically or fail to appear altogether, depending on the layout used.
How to reproduce
Use the following minimal code snippet to reproduce the issue:
Run the code.
Observe the following:
Screenshots
No response
Example code
The text was updated successfully, but these errors were encountered: