Trying to compare same WebApp in both versions of Xojo, WebListBox specifically, using Data Source.
I have noticed that column labels in newest Xojo2025R3 will be shown rather than truncated but now I am not sure if this is better, see the snapshot for comparison with Xojo2025R2.1:
So the question is, what should I do now.
The answer depends on what you want.
Do you like 2025r3 behavior? Use that.
Do you prefer 2025r2.1 behavior? Create an Issue with a simple sample project for @Ricardo_Cruz to review. He, or someone else, may post code to fix the problem to use before the fix is released.
Looks to me as a Xojo user trouble; either:
a. Enlarge each columns (… means that IMHO),
b. Use less columns (and you get rooms to do a.)
c. Worst, use A, B, C, … as Header Text.
Both are wrong in my POV. The top one is worth than the first letter followed by an ellipsed, but the bottom is not instructive at all.
We are near a catch-22 dilemna.
Looking at it from an end user perspective, both look bad
It looks like a regression to me, that has to be fixed, but I agree with @brian_franco, there might be too many columns there.
I don’t know how many rows do you need to display, but if there aren’t too many, you could design containers using more vertical space and then place them dynamically using the Flex LayoutType.
Well, the number of columns for this particular page is what users need and frankly it is never enough for some users, some columns are always going to be narrow to save space hence the column title may be always truncated. At first I welcomed the fact that column titles showed up when there was enough room, but on this list they flow over which is bad.
I need to keep this WebApp compatible with “latest and greatest” Xojo so that the app is up to date.
In terms of number of rows, well, that is always a tricky question, the query behind the data source can produce many rows (thousands or more). I don’t want to complicate the design by introducing yet another layer of complexity. Right now the WebList is using data source and thread and data seems to be loading smoothly when scrolling through the list, all columns are set dynamically, the sorting on single column works fine. I just wish for multi-sort feature but that is for some other time.
I agree, but keep in mind, users of this WebApp care about the data a lot, hence there are always many columns and they are made narrow when needed unfortunately. So the column title inevitably may be truncated. I am not saying that either of those two version is better, just noticing the difference.
Except that there are limitations with the hardware, like monitor width-to-height ratio, then what can be done: buy larger monitors that cost more, or use other sophisticated technology that also has a high cost? Or you may reduce the font size; everything will be displayed, but unreadable.
How about replacing the WebListBox with a Container in which you create more containers in which you display data in a form-like fashion? If a WebListBox with a unique column can display a Container in that column, then it is even easier. The tradeoff here is that you have fewer records in the screen height, but hey, you can’t have your cake and eat it too!
I’m sure @Ricardo_Cruz will fix the regression if that is what it turns out to be.
I certainly hope it doesn’t go back to truncating way too early like it had been. IMO what has changed as far as non-modified controls is operational.
OP is doing a bunch of CSS changes to the table, so in my opinion THEY are responsible for making sure their font change truncates at the right place.
Who knows what they copy and pasted? We haven’t seen their CSS changes, and the built in changes are working flawlessly for me. I will be mad if truncation gets changed without seeing OPs CSS.
