UINavigationBar.tintColor life on own?
UINavigationBar.tintColor life on own?
- Subject: UINavigationBar.tintColor life on own?
- From: Hado Hein <email@hidden>
- Date: Tue, 07 Jan 2014 17:26:46 +0100
I have an app where the navigation bar tint color starts to have an life on its own.
Basic setup is that the app loads a document and in this document there is a key/value for the navigation bar tint color.
In my basic “make up the content view” i also set the navigation bar color with self.navigationbar.tintcolor = something.
That works as it should be.
Now the user navigates around, pushes and pops other view controllers. Child view controllers of the root controller corectly inherit the tint color.
At some time the user loads/exchanges another (second) document from the root view controller. Now I do my “make up the content view” again and set the navigation bar tint color to a new value. All child view controllers aren’t visibile but their nibs should be still loaded from the first document. (I have no memory warnings that would indicate an unload/purge).
When the user now starts navigating again the child view controllers still have the tint color from the first document.
This is also true if i do a second call on the UINavigationController appearance proxy. The child view controllers still have the color from the first document.
Is there a reasonable way to correct this behaviour besides passing on the navigation bar color when pushing and popping child view controllers. Actually I do not have a reference to that vars in child view controllers, so it is not that easy for me to just read and set the tint color again an again.
thx,
_______________________________________________
Cocoa-dev mailing list (email@hidden)
Please do not post admin requests or moderator comments to the list.
Contact the moderators at cocoa-dev-admins(at)lists.apple.com
Help/Unsubscribe/Update your Subscription:
This email sent to email@hidden