Ch. 6 - ScrollView

sirab33 · May 27th, 2011, 11:11 PM

this is regarding the program that makes the view scroll up when the Keyboard appears, so that it (the Keyboard) doesn't cover-up and hide what's already on-screen: at the bottom of page 173 the code is:

Code:

// When the keyboard appears:
-(void) keyboardDidShow: (NSNotification *) notification {
	if (keyboardIsShown) return;
	
	NSDictionary *info = [notification userInfo];
	NSLog(@"Here's our Notification: %@" , notification);

etc.

Well what's the very first statement all about?

Code:

if (keyboardIsShown) return;

What is it returning? The method itself is of type (void) so its not relating to that.
Nor is it causing the method to exit at that point - so what is it doing? why do we need it?

thepianoguy · June 1st, 2011, 09:13 AM

Nothing is returning, it is simply a way to exit the method. The "if" statement could be structured to avoid it. However, in this example, keyboardIsShown is never going to be YES in this method, so it can be omitted.
The keyboardDidShow method is called when a textField is clicked on - keyboardIsShown is NO
If the view is rotated while the keyboard is visible, the keyboardDidHide method is called setting the keyboardIsShown back to NO and then immediately calling keyboardDidShow. In this example the if (keyboardIsShown) statement is not needed.

Also note in the project, that there is an error in the removeObserver code in the -viewWillDisappear method. The method names should match those in the addObserver registrations. This has been brought up in a previous thread.

Bob

sirab33 · June 1st, 2011, 04:32 PM

starting at the end - yes, I did notice the errors in the removeObserver code (removing the "WillShowNotification" and "WillHideNotification" methods when what was actually added earlier were the "DidShow" and "DidHide" notifications - a glaring mismatch) - and it threw me for yet another frustrating loop till I figured it out.

(I must say, I'm becoming more and more "impressed" with how little care the Author or Publishers of this book seemed to have had when putting it out. SO MANY code errors... Or Apps that crash even though the code was typed in exactly as appears in the book...)

In terms of the "return" statement - understood :-)
I also looked it up in the Kochan Objective-C book (a wonderful, error-free book

) - and right there in Appendix B it goes through all the different type of "Statements" there are and for "The Return Statement" it states: "Execution of the return statement causes program execution to be immediately returned to the calling function or method."

So I was like "oh....duh!!!..."

Well, hopefully someone else down the line will benefit from this and all our other posts and "duhs"

I'm now on Chapter 15 and currently experiencing one of those inexplicable App-crashes - even though I typed the code in exactly as it appears in the book...

May be posting about that soon - stay tuned