Good news..

[John Sutherland]

I just checked in a new Utilities that should fix the app switching
issues..

First, I made it switching to the app faster. No more long fade out..
And next, and the biggie, I got it to return to the controller where
you left off.

The magic: Instead of calling _hideFrontRow or whatever, I found
another routine _continueDestroyScene_(None).. This gives us the fast
exit to our app.

Coming back into FrontRow, I call _makeScene, which seems to rebuild
everything for us, where we left off... For my AppLauncher controller,
I override that FRWasShown, and call the popController to return back
to my fileBrowser...

I haven't attempted yet to see if I can remove that 'ping' stuff, that
brings the app forward.. We might be able to remove that.

Let me know how this works for you in your EyeTV stuff.

--John

[Jon Christopher]

You rock.  I'd seen _continueDestroyScene, but never thought about what it might do.

[Jon Christopher]

John,

using _continueDestroyScene is much faster, but I have two issues, one trivial, one really bad.

First, the waitDone method of WaitController used to pop the wait controller (spinner) for you; now
unless you do it in FRWasShown, you're just going to be stuck looking at a spinner.

The second isue is that after returning from EyeTV (that is, the AppShouldExit function returns true)
Front Row no longer has control of the remote, so even though you're back in FR, you can't *do* anything.

Do you get the same behavior for your app launcher?

-Jon

[Jon Christopher]

And using _showFrontRow instead of _makeScene seems to do the trick; the remote is returned to FR, and we're back were we left.

The only real issue I have now is aesthetic.  After returning to FrontRow via _showFrontRow, the text "Launching EyeTV" and the
spinner are still visible for a moment before the wait controller is popped.  It'd be nicer if it was just a blank screen at this point. 

Perhaps very last thing before we hide Front Row we can zero out the text and spinner here so we just get a black screen when we come back to it?  I tried removing those controlls after we've hidden FR, but that didn't work.  Any other ideas?

[John Sutherland]

On Jan 24, 2008, at 2:21 AM, Jon Christopher wrote:

> And using _showFrontRow instead of _makeScene seems to do the trick;
> the remote is returned to FR, and we're back were we left.

Heh.. I've been working on my laptop, without a remote, just using the
keyboard... So I hadn't notice that problem.. At least that works for
us..

> The only real issue I have now is aesthetic. After returning to
> FrontRow via _showFrontRow, the text "Launching EyeTV" and the
> spinner are still visible for a moment before the wait controller is
> popped. It'd be nicer if it was just a blank screen at this point.
>
> Perhaps very last thing before we hide Front Row we can zero out the
> text and spinner here so we just get a black screen when we come
> back to it? I tried removing those controlls after we've hidden FR,
> but that didn't work. Any other ideas?

Hrm.. You removed the controls via BRPanel.removeAllControls? There's
also BRControl.setHidden.. Maybe that will work? Another thought is
to pop the controller, make a new blank one. Or just do a new blank
one (without popping first), and then pop 2x when needed.

> First, the waitDone method of WaitController used to pop the wait
> controller (spinner) for you; now
> unless you do it in FRWasShown, you're just going to be stuck
> looking at a spinner.

Yeah, I'll have the FRWasShown call the WaitDone method. Since i'm
'wrapping' the wait controller, thats probably the 'more correct' way
of doing it.

--John