Thank you bob133 for helping me work through this can of worms.
I have a convention that I name something according to what it does. The purpose of this property is to call the hideBirthFrameOutlet2 method in XTBMainViewController1.m from XTBMainViewController2. Therefore I feel callHideBirthFrameOutlet2Method is a good one (a bit long, I admit but a good one).
Now your second observation about using the name XTBMainViewController2 when the method I want called is in XTBMainViewController1 is absolutely spot ON! I changed the 2 to a 1 and it compiles and the 2 error messages are gone! Unfortunately, you were also correct with the "Yes, it compiles now but that won't do YOU any good" prediction. It doesn't do me any good. The BirthFrameOutlet2 is still visible covering the animation (which starts to play again, under BirthFrameOutlet2) when I leave page 2 to go back to Page1. Do you have to be right all the time?
Your following question has me totally mystified. Quote: "Why are you creating a brand-new view controller that will never be used in your interface?"
I don't see how I am creating a new view controller. To my understanding, I have created a view controller for each page of the comic book. Each view controller is made up of a view controller in the storyboard and a corresponding view controller class. When I call the - (IBAction)goBackToPage1) method, I thought I was simply doing that - going back to Page1 with its one storyboard viewcontroller and its accompanying viewController class.
Are you saying that by coding:
self.callHideBirthFrameOutlet2Method = [[XTBMainViewController1 alloc] init];
I'm creating a whole new view controller!? I know I am revealing the profound depths of my noobie-ism here but I simply don't understand.
We'll get back to that one later. I see you suggest some code that I should key in instead. To me, it looks just like Greek but you seem to know what you're talking about so I'll try it out...
OMG!! It works....almost! This is what happens. I turn to page one from the Cover Page and the animation kicks in as it should. I leave Page 1 to Page 2 in the middle of the animation and then I go back. Your code hides BirthFrameOutlet2! Then it comes back again.😮 Sometimes, it comes back in 3 seconds; other tries, it comes back in 6 seconds. I think that when I go back to Page 1, the code I have written for that page starts to work again unhiding BirthFrameOutlet2. I think I can work this out myself. I think you solved it bob!
If you just explain to me how I am creating a new view controller that will turn this into a real learning moment for me. And... ( I know I'm asking a lot here)
if you could explain the code (you know - the Greek code) you gave me solving the problem, that would be really helpful so I can place that into the comments within my code.
JR