Updated TableView API Reference Guide

abstract, background, hexagons, design, pattern, technology, tech, hi tech, sci fi, digital, innovation, innovative, concept, computer, computing, science, scientific, structure, networking, connection, data, banwidth, loading, shape, gradient, green, vector, illustration, power, arrow, medical, health care,

I’ve posted an updated TableView API Reference Guide. The sample programs are revised and expanded, and there’s a much more extensive sample app that illustrates how you would use the className property of a TableViewRow.

We’ll be continuing work with this series of documents; several more of these API Reference Guides will be coming later this week and next week, each with more sample code. As always, comments are welcome. Happy coding!


  1. Hey. Thanks for this post. I had tried to use the same className for rows that had the same structural layout but found oddities occurring during scrolling and interaction. It was recommended in the forums to name each row a different classname which solved that problem. Should I switch back now? has the codebase changed in a latest continuous build that solves these issues?



    • @Dave – using a classname for each row will absolutely destroy all performance gains since it means each row has to be repainted each time.

  2. there are dashes at the end of each long code sample lines. So that cut n paste dont work. Good job however

  3. Yes, I also found that className does not currently seem to be usable with ‘complex’ layouts, i.e. TableViewRows that contain other controls (Labels etc) – seems to work ok on simpler rows though (eg. with just a ‘title’ set or whatever).

  4. Ignore my earlier note… I just noticed, you very recently updated it… The latest guide has more sample programs which is new to me. That is surely improvement. Thank you..

    I must have read the prev guide which I printed I believe “yesterday”. The more the samples, the better it is.

    Just add the default values ( I suggested in my earlier note ) please. And may be mark those items that are used a lot.

  5. There’s a good example of using the className in the TableView API Reference Guide, available on our documentation page. The 4th code example shows how to use className to distinguish two types of rows. In that example, there is one className (‘Pic’) assigned to all the rows that have images associated with them, and another className (‘noPic’) that’s assigned to the remaining rows that don’t have images.

    Rows that have the same structure should share the same className. “The same structure” means “the same controls with the same layout added to the row in the same order”.

    It’s not correct to have a unique className for every row, regardless of its structure. Rather, you want to have rows with the same structure share the same className. If you were to use a unique className for every row, you would have poor performance with more than a small number of rows.

Comments are closed.