Screen and IActivate

Feb 11, 2011 at 11:05 PM

Just a curiosity... is there a reason that Screen implements IActivate, but hides the IActivate methods?  In other words, is there a reason it's not just public (like, it does things that aren't obvious so I should take care when using it)?

Feb 12, 2011 at 8:32 AM

Since the lifecycle of a Screen should be "externally" managed and coordinated by a Conductor, having that method private avoids accidental calls to lifecycle methods from the Screen itself.