After updating from Ventura to Sequoia, many (but not all!) of my apps’ ListBoxes no longer display their horizontal lines, which I typically set to “Thin Dotted”.
Under Windows, they all look normal.
Xojo 20221r2.1.
Anyone else seen this issue?
Looks like they display ok initially before loading, but then after RemoveAllRows and a bunch of AddRows they lose their horizontal lines.
Stupid question:
have-you checked in the ListBox Properties what is checked as lines ?
I think thin dotted was removed in recent(s) Xojo versions…
It’s early in the morning here:
That screenshot was done with Xojo 2026r1.
Couldn’t resist…
@Julia_Truchsess You must be from the very distant future! Despite the haters - looks like Xojo survives another 20,000 or so years…Geoff became pure GeoffAI in the late 2020’s and still runs the company.
4 Likes
Is your screen HiDPI / Retina? I faintly recall something about the partial-pixels, edges of listbox cells, and macos updates.
For science™ have you tried a newer version just to see if the issue is resolved?
It’s an M1 MacBook Pro, so yes it’s a retina screen.
If I turn off Supports Hi-DPI, the behaviour changes - which ListBoxes show horizontal lines and which don’t is different.
If I use Thin Solid instead of Thin Dotted the horizontal lines are always shown. I don’t like the appearance, but it may be my only choice for a workaround.
In Xojo 2025r3.1, it looks like the ability to choose line styles has been eliminated - what?!? You only get None, Horizontal, Vertical, or Both. The lines appear but they’re a very faint thin solid gray 
Bonjour Emile, I hope you have had a nice coffee and croissant by now.
The lines all display as expected when I build for Windows, and they display as expected in Mac builds when the listboxes first open, so the IDE settings are correct.
Yes, I just noticed that the ability to select line styles has unfortunately been completely removed in recent Xojo. But I use 2021r2.1, so this is not too relevant.
Merci!
Could you just draw the line yourself in the CellBackgroundPaint event? To work around this bug and/or limitation…