Enlarge the cell size in table control will make the program run slower?

[lolkc2]

I am writting data in to the table control and to color some the of cell background. Firstly, I work with the table control in smaller size. After that, when I set my cell become larger I found that the data is updating slower than when the cell size is smaller. Is there any solution to solve this problem?

[nyc_(is_out_of_here)]

---

@lolkc2 wrote:

I am writting data in to the table control and to color some the of cell background. Firstly, I work with the table control in smaller size. After that, when I set my cell become larger I found that the data is updating slower than when the cell size is smaller. Is there any solution to solve this problem?

---

VI  ?

[billko]

Are you overlapping other controls when you enlarge the cells?  Or even coming close?  (Sometimes the boundaries of the control go beyond the visible part.)

[lolkc2]

Already solved the problem. Thanks for reply.

[billko]

Do you think you can at least give an overview of how you solved it (and then mark that post as the solution) so that other people who have that problem can have the benefit of your knowledge?

[lolkc2 · Accepted solution]

I store all my data into the shift register then only update to the table. I found that by this way the data will show out in the table faster then updating one by one.

[billko]

Interesting.  I 'm not quite sure how that helped the slowdown on resizing.  Maybe because you're not updating the front panel so often any more?

[lolkc2]

Yes, I also feel that is the thing that made the program faster. Because if I update the data one by one will make the front panel keep on updating. So I think of this way which store all the data into the shift register and then only update to the front. 

[Hooovahh]

What version of LabVIEW was this in?  In 2013 there were quite a few improvements to table formatting.

https://lavag.org/topic/17009-labview-2013-favorite-features-and-improvements/page-2#entry104672

I'm just curious if it was slow even on 2013 or newer than it would have been terrible in older versions.

Also I believe the technique you used is called virtual tables or virtual multicolumn listboxes which is common in other languages were only the data being seen is updated.

https://lavag.org/topic/15289-virtual-multicolumn-listbox/