PointDisplay release; Counteracts UIImageView* pointDisplay = UIImageView alloc initWithFrame:CGRectMake((p. X - 15), (p. Y - 35), 76.
F, 40. F); Then adding the subview self addSubview:pointDisplay; has increased the retain count of pointDisplay; the corresponding release will be sent to pointDisplay automatically when it is removed from its superview or when self is deallocated (UIView releases it's subviews automatically in its dealloc). The fact that it has 0.0 alpha, or is hidden doesn't make any difference.
This wouldnt cause a memory leak, the memory management looks ok on it... if you would call this 100 times, your memory would keep increasing, but this wouldnt be considered a leak, because if you release the view you are adding on, the UIImageViews will be released as well... A memory leak occurs when you allocate some object or data and then have no way to release is later...for example -(void)blah { NSString *s=NSString alloc init; } the above will cause a memory leak because the method creates a string with a +1 ref count, when the method exits you no longer have a reference to the string, therefore you won't be able to release it and the system will not reclaim the memory allocated for the string..in your example, the UIView you add on retains the UIImageView, but when you release the UIView all the UIImageViews on it will be released as well. Hope this helps.
If you want get rid of pointdisplay from you're view, below refer code pointDisplay removeFromSuperView.
IF you copy, alloc or new once then you only release once. developer.apple.com/library/mac/#documen....
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.