Comments on: Combining multiple UITextFields and a UITableView in a nice way for an iPhone app http://blog.d-17.com/2009/08/combining-multiple-uitextfields-and-a-uitableview-in-a-nice-way-for-an-iphone-app/ About hardcore technology and softcore business Fri, 18 Jun 2010 02:03:13 +0000 http://wordpress.org/?v=2.9.2 hourly 1 By: Paula http://blog.d-17.com/2009/08/combining-multiple-uitextfields-and-a-uitableview-in-a-nice-way-for-an-iphone-app/comment-page-1/#comment-4784 Paula Fri, 14 May 2010 02:24:56 +0000 http://blog.d-17.com/?p=85#comment-4784 > Wont doing that mean it all stays in memory and results in slow scroll performance? "Using more memory" and "slow scrolling"... are NOT the same things. Which sounds faster: 1. Drawing it once... use a little memory... and just scroll it around. 2. Save a little memory... and alloc ever cell... over and over... or dealloc... and reuse... and redesign ever cell... countless times. > Wont doing that mean it all stays in memory and results in slow scroll performance?

“Using more memory” and “slow scrolling”… are NOT the same things.

Which sounds faster:
1. Drawing it once… use a little memory… and just scroll it around.

2. Save a little memory… and alloc ever cell… over and over… or dealloc… and reuse… and redesign ever cell… countless times.

]]> By: admin http://blog.d-17.com/2009/08/combining-multiple-uitextfields-and-a-uitableview-in-a-nice-way-for-an-iphone-app/comment-page-1/#comment-4756 admin Wed, 12 May 2010 12:28:20 +0000 http://blog.d-17.com/?p=85#comment-4756 Yes, that would keep the actual data in memory. I do not think the 50 lines of input causes the problems, that's with UTF-8 maybe 50 * 60 * 2 = 6k of data. Any given moment an app will use 10-20mb of memory, so 6k is not a lot. Look at incorrect overlaps/sizes of subviews in views, too many transparent views etc to fix your problems. dirk Yes, that would keep the actual data in memory. I do not think the 50 lines of input causes the problems, that’s with UTF-8 maybe 50 * 60 * 2 = 6k of data. Any given moment an app will use 10-20mb of memory, so 6k is not a lot.

Look at incorrect overlaps/sizes of subviews in views, too many transparent views etc to fix your problems.

dirk

]]> By: patty http://blog.d-17.com/2009/08/combining-multiple-uitextfields-and-a-uitableview-in-a-nice-way-for-an-iphone-app/comment-page-1/#comment-4749 patty Tue, 11 May 2010 16:33:38 +0000 http://blog.d-17.com/?p=85#comment-4749 50 lines of input???? Who is going to type in all of that??? 50 lines of input????

Who is going to type in all of that???

]]> By: Andyong http://blog.d-17.com/2009/08/combining-multiple-uitextfields-and-a-uitableview-in-a-nice-way-for-an-iphone-app/comment-page-1/#comment-4693 Andyong Fri, 07 May 2010 08:53:55 +0000 http://blog.d-17.com/?p=85#comment-4693 Just a question. Wont doing that mean it all stays in memory and results in slow scroll performance? I have an app that requires up to 50 lines of input involving UITextFields, and a switch and am currently using a UIScrollview but the scrolling is no longer smooth as soon as you start adding UITextfields as subviews. Just a question. Wont doing that mean it all stays in memory and results in slow scroll performance? I have an app that requires up to 50 lines of input involving UITextFields, and a switch and am currently using a UIScrollview but the scrolling is no longer smooth as soon as you start adding UITextfields as subviews.

]]>