I'm having a problem with using the CrownSequencer on a page-based watch app, where I can't find the right way to get the WKCrownSequencer to be active on the first page right after launching. The app's interface storyboard has two WKInterfaceController objects connected with a nextPage relationship segue. Here's the summary of events that happen at app launch:
- -awakeWithContext: is called on page 1
- -awakeWithContext: is called on page 2
- -willActivate is called on page 1
- -willActivate is called on page 2
- -didDeactivate: is called on page 2 (because page 1 is the visible page)
The problem -- I'd like to access the WKCrownSequencer on both pages, but where do I put the call to -focus? If I put it in -awakeWithContext: or -willActivate, then when first launching, page 1 is visible, but the crown is always active on page 2, since these methods are called on all pages in order. Even if I called -resignFocus in -didDeactivate of page 2, that doesn't give the focus back to page 1. With the page based interface, the context in -awakeWithContext: is always nil and there's no way to provide one. -contextForSegueWithIdentifier: is not called when using the nextPage relationship segue. So, there's no way for the two pages to have a reference to one another, or to communicate with each other. -willActivate: is not called again on page 1 until I navigate to the second page and back to the first. Is there some offical way to do this, some method for page 1 that will allow me to activate the CrownSequencer at the right time, or do I just need to treat the inital launch as a special case and prevent the second page from stealing the focus and/or set a timer or something to get the first page to steal it back?
