UITable performance issues on Windows Phone 8

[latas]

We got an ScrollView which contains a UITable with some part hidden. We've got 3 sprites per row. We've got a total amount of 150 sprites. It's true that is under iOS which the performance is quite good. Android is a little bit slower, and under Windows Phone 8 simply it is impossible to make it work.

We think it works well but not with more than 50 sprites.

Any one can provide me some information about why to use a table or not, and what limits of information should I manage with that object?

Thank you very much.

[ArenMook]

I vaguely remember explaining this via skype yesterday, but I'll repeat myself here for future searches. Table is not a good choice if you care about performance, because it has to calculate the dimensions of every single cell. A Grid should be used instead if the width of your cells is known ahead of time. Other than that, there isn't any difference between NGUI on iOS/Android and WP8. Only the UIInput script differs. Unity's performance on Windows phones though... that is likely still being worked on.