I have a table being generated from a script. In the script it is set to auto. Could the table be loading before the data is updated? The data is larger than the column width so it is chopping off data. Trying to avoid a strict width as the number size will change (totalizer).
Script:
How the table looks:
The columns object binding:
Table item set to "auto" width:
I'm not sure auto is a valid value. I use numeric values without strictWidth, where the value for each column indicates its width relative to the size of the other columns. Even single-digit values will work, so column A set at 1, and column B set at 2 will ensure that column B will be twice the size of column A. It doesn't mean 1 and 2 pixels big unless strictWidth is enabled.
I believe the width column is in "px". So 50 = 50px.
Relative weight is not working here for me. What other setting did you have?
From their online manual:
I found an answer in this post that worked for me:
How to define column width in percentage
Something to note. This is only happening on a version of Ignition Edge. I am running a similar app with a Standard version of Ignition. It appears to be fine on that one.
Standard Ignition:
You're not showing us the full screen width. Does your table overflow the screen or is it squashed into it? (i.e. Is there a horizontal scrollbar?)
Is there a difference in screen resolution or display size that would affect the table rendering?
Zoomed out to show the whole table.
Everything is identical except font size.
I am looking at the CCS for the table (inspected).
May try to adjust this: class="tc ia_table__Cell"
It has some padding applied to the field. Looks like it is shifting it over.
Does your table overflow the screen or is it squashed into it?
Horizonal Scroll bar. Not squashed.
Is there a difference in screen resolution or display size that would affect the table rendering?
Same resolution 1920x1080
I ended up making the font smaller. And having to remove "padding-left" that was showing up in the CSS.
Added to a custom CCS and copied over to my Opto22 Edge via Putty.
It appears the text is just slightly off center. The totalizer data will eventually grow. Will need to do some testing with larger numbers to see if the column will auto size. For now it looks "ok".
Left of center (see arrow) for larger numbers.
I was going to ask earlier but forgot; who needs nine significant digits? If you made it read ÷ 1000 values it would be more human friendly and 3,350,652.25 becomes 3,350 or ÷ 1 million → 3.350.
If you are using 32-bit floats, then any digits after the first six are utterly bogus, anyways.
