[TIMOB-2719] TableViewRows containing multiple views & having the same className exhibit weird behaviour

See https://gist.github.com/ab80b6d74e1559bdb7f5">https://gist.github.com/ab80b6d74e1559bdb7f5 for example app on Titanium 1.5.1 (tested on Android 1.6 & 2.2).

We create a simple TableView, add it to a window & open the window. Now in a loop, we add 15 rows to the TableView with each row having the same className 'item'. Each row contains a view with 2 different Labels added to it. We use appendRow to add rows to the TableView. Expected behaviour is that the rows will be in order from 1 to 15. However we see that the rows containing odd & even numbers are grouped together on either side of the row containing item 0!

Each row also has an event handler which will alert the row number. Again, this seems to work in a weird way. There seems to be no correspondence between the row number displayed in the label & the number displayed in the alert box! Sometimes a few rows in the beginning show correlation, but this breaks as soon as we start scrolling.

However, using unique class names for each row seems to fix this problem. But that is supposed to be inefficient & isn't recommended by the documentation. Also Bug 2621 (https://appcelerator.lighthouseapp.com/projects/32238/tickets/2621-android-app-crashes-with-paged-tableview-15x-regression">https://appcelerator.lighthouseapp.com/projects/32238/tickets/2621-...) occurs occasionally when we use unique class names.

We tried pushing the rows into an array and using setData to update the TableView. This doesn't exhibit the initial odd/even grouping of rows. But as soon as we start scrolling, the rows get totally scrambled and the alerts begin exhibiting the behaviour detailed above.

In both these cases, if we change the device orientation then some rows disappear altogether! The alerts on them continue to work though.