Another Problem With Column Widths

,

As above, I have a column with a single unicode character. It has text size 1.5 via formatting rules but has a blank (" ") display name (column header). Why is the column so wide?? It really messes with the flow of the table, and I can’t think of any reason why this should be. I can work around it by concatenating the text of the “icon” column with the text of the “name” column…but then I lose the individual formatting options I was trying to use.

It seems like column width control has been a persistent problem with AppSheet table views…is there really no progress on it? / Any way to make a column properly “fit to contents”?

We have no control other than what’s provided in the view options of - Default, Narrow and Wide. AppSheet does try to use “best fit” up to a max width. Obviously the addition of the unicode character is throwing it off. Maybe you can find an alternative way to display the unicode? E.g. place it in its own column?

I agree this has been a huge oversight in the AppSheet platform - especially now that they support more robust desktop views. I have personally raised this problem a half-dozen times. There are MANY Feature Ideas on column widths and I think all those might be diluting the interest in this as a feature. Maybe we need to push for Community members to pick one and vote it up so it can finally, hopefully get some traction in development.

1 Like

I’m not quite sure what you mean here. The unicode character is in it’s own column, that’s why I’m confounded as to why it requires so much space! Unfortunately, the unicode is the alternative. I wanted to use the similar FontAwesome icons, but they aren’t available in the version AppSheet uses (they are ‘pro’ I believe).

Anyway, I also checked using just “normal” text:

Same poor spacing problem.

I don’t get why we aren’t allowed to just set the column widths directly, either in px or %. I mean the system already has a working cell/text truncation algorithm and you can manually adjust the column widths. Surely it can’t be that complicated, it’s practically done already? It’s just such an immediately obvious problem as soon as you try to use any table view - surely the devs can see that? I mean ResizeColumns() is a priority routine any time I’m working with a grid control!

1 Like

Back to the unicode…and for no discernable reason…it is now acceptable! So frustrating!