Several Issues with 1.4 to point out...
I'm going through my app after compiling using the new SDK and noticed a couple things…
- focus event doesn't refresh my window. I have a focus event wrapping an ajax request to the server. It worked before the update but with 1.4, it no longer works. I narrowed down that the xhr request's send and onload running before anything is done.
i.e. This is part of my xhr method http://screencast.com/t/ODZjOTY5N but this runs before the xhr is done. http://screencast.com/t/MGM5MjhiND
It didn't do that before.
- Some table rows are blank, though data is present and inside the row. Actually, by scrolling up and down, they become visible right at the edge of the screen, but as soon as I scroll to the middle they're gone. This was working fine before too. Here's a video of it happening: http://screencast.com/t/NWU1ZmNj
Here's part of the table code (minus the xhr stuff…the code here is part of the callback): http://pastie.org/1064654
6 Answers
-
Accepted Answer
As long as you have identical rows ( from the layout point of view ), use the same classname for these. It will tell the device to use the same template for these rows and the rendering will be improved a lot( less memory, etc )
Another thing that I see in your code is that you use try to use in the same time declarations for standard rows( like leftImage ) and then you add elements to that row.
Try to create a custom row completely.
Here is a tutorial that might help youhttp://cssgallery.info/custom-row-for-tableview-in-appcelerator-titanium/
Take care that you have rows with different layout( w/out checkbox, w/out timer, etc). For each situation you need a unique className ( ugly, I know :) )
-
Looks like #1 is a consistent issue: http://developer.appcelerator.com/question/47851/titaniumnetworkcreatehttpclient-no-longer-working-with-14-sdk
-
Not sure about #1 but #2 is definitely an error between your chair and the keyboard…. Table rows working great in 1.4
-
Not sure about #1 but #2 is definitely an error between your chair and the keyboard…. Table rows working great in 1.4
-
#2 is broken too, you're right.
Add a className to the tablerow and wil fix the issue, for iphone at least, for the ipad it's still broken
-
@Tamas - Thanks for the tip. Added a className to each row but didn't affect it at all. I've known about the className for table rows but haven't used it. is it considered best practice to use this?
@Ringo - What's that supposed to mean?