NSString alloc or not?

Will avoid the need to explicitly release the string, since it is autoreleased.

Years. Text = NSString stringWithFormat:@"%0.1f", theScroller.contentOffset. Y; will avoid the need to explicitly release the string, since it is autoreleased.

However, if you are trying to avoid slowdown, consider updating the field less frequently. For example, each time scrollViewDidScroll is called, set a timer to update the field in say 0.1 seconds from now, but not if the timer is already running from a previous call. This reduces the number of calls while keeping the UI updated.

Here is an example how you could do it. Declare an NSTimer in the interface declaration of your scroll view delegate: NSTimer *timer; And methods: - (void)updateYear:(NSTimer*)theTimer { timer=nil; UIScrollView *theScroller=theTimer userInfo; years. Text=NSString stringWithFormat:@"%0.1f", theScroller.contentOffset.

Y; } - (void)scrollViewDidScroll:(UIScrollView *)theScroller { if (!timer) { timer=NSTimer scheduledTimerWithTimeInterval:0.1 target:self selector:@selector(updateYear:) userInfo:theScroller repeats:NO; } } Obviously, you don't have to use 0.1 as the time interval, you can try making it faster or slower and see what works best. Note that this example is complete as far as memory management is concerned, You should not try to retain or release the timer object yourself. Its lifetime is handled internally by the runloop.

This is just a convenience method that allocs the string behind the scenes. It is not an alternative. – Chuck Mar 16 at 9:04 I have now added a more full answer.

– Nick Moore Mar 16 at 9:08 Many thanks, I am going to set up a Timer.. – Mark Tompson Mar 16 at 9:19 Any nice Timer examples (links) would be a great help.. (I will look as well, I'm not being lazy lol) – Mark Tompson Mar 16 at 9:22 @Mark Example posted! – Nick Moore Mar 16 at 9:39.

Consider using scrollViewDidEndDecelerating method to avoid the frequent updates. Alloc-init is not responsible for the performance decrease, setting the text frequently is. Unless you really need to change it continuously (in which case solution with a timer might be an option), you should be looking for a different hook method.

Thanks Thomas I do need it all the time, so a Timer option looks good. – Mark Tompson Mar 16 at 9:18.

You've got poor performance absolutely not because of the string formatting or alloc-release. You can use some shorter form like: years. Text = NSString stringWithFormat:@"%0.1f", theScroller.contentOffset.

Y; which is equivalent to years. Text = NSString alloc initWithFormat:@"%0.1f", theScroller.contentOffset. Y autorelease; However this won't help to improve your performance at all.

– Mark Tompson Mar 16 at 11:21 @Mark sometimes you might not want to autorelease the string in which case you would alloc it but not autorelease.So alloc/release gives you more fine control but stringWithFormat is more convenient for when you would be autoreleasing the string anyway. – Nick Moore Mar 16 at 14:12.

I cant really gove you an answer,but what I can give you is a way to a solution, that is you have to find the anglde that you relate to or peaks your interest. A good paper is one that people get drawn into because it reaches them ln some way.As for me WW11 to me, I think of the holocaust and the effect it had on the survivors, their families and those who stood by and did nothing until it was too late.