Re: frontpython timeout

1 view
Skip to first unread message

Jon Christopher

unread,
Apr 7, 2008, 2:52:07 AM4/7/08
to John Sutherland, frontpyth...@googlegroups.com
Hi John,

I think I've found why frontpython quits after 20 minutes.

@interface FRAutoQuitManager : NSObject
{
   NSTimer *_autoQuitTimer;
}

+ (id)sharedManager;
- (void)dealloc;
- (void)setAutoQuitEnabled:(BOOL)fp8;

@end

Now, it ought to be a simple matter to get the sharedManager instance and disable the auto-quit.  However, this class is defined in the front row application itself, and not the BackRow framework, so I don't know how to tell python about it.  Do you have any suggestions?

Thanks,
Jon

On Sun, Apr 6, 2008 at 1:34 PM, John Sutherland <gari...@gmail.com> wrote:
> I too haven't been doing much with it lately, as work has been hellish..
>  
>  I've run into similar issue, but never tried to track it down..
>  
>  One thing I just started watching is the OSX XBMC  stuff.. It Intel only
> right now, but it certainly looks nice.. And they are working on Python
> modules :)..
>  
>  --John
>
>
>  
>  On Apr 5, 2008, at 12:26 AM, Jon Christopher wrote:
>  
> > Hi John,
> >
> > I haven't had time to touch my PyeTV plugin for a while, but there's
> > one thing which has been bugging me that I finally had a chance to try
> > to track down.
> >
> > Normal operation for PyeTV is that it uses a PyFR WaitController to
> > launch EyeTV, and it installs a function for AppShouldExit which
> > checks to see if the recording is still playing.  If not (i.e. the
> > user has pressed pause) then AppShouldExit returns true, and we return
> > to PyeTV.
> >
> > This works fine *unless* I've been watching the recording for a while,
> > at which point this just stops working and I basically have to enter
> > FrontRow again.
> >
> > Added a call to log() inside AppShouldExit, and found something
> > interesting---AppShouldExit simply stops being called after almost
> > exactly 20 minutes.
> >
> > Do you have any ideas as to why that might be?  My first thought was
> > some sort of screensaver timeout kicking out FR, but I changed my
> > screensaver timeout and still got the same 20 minute delay.
> >
> > In fact, from what I can tell, FrontRow itself has stopped.  It no
> > longer shows up in the process list after that time, whereas it was
> > there before.
> >
> > Any ideas at all?
> >
> > Thanks,
> > Jon
> >
>  
>  --John
>  
>  
>  
>  
>  

Jon Christopher

unread,
Apr 7, 2008, 4:32:27 AM4/7/08
to John Sutherland, frontpyth...@googlegroups.com

I think I've figured it out:

        # FR automatically quits after 20 minutes.  This should disable that behavior...
        foo=objc.lookUpClass("FRAutoQuitManager")
        foo.sharedManager().setAutoQuitEnabled_(False)

-Jon

Polar Bear

unread,
Apr 7, 2008, 8:38:15 PM4/7/08
to frontpython-discuss.
FrontRow has some "secret" preference settings.

Besides one for running on the second display
(FrontRowUsePreferredDisplayID), there is also one called
"AutoQuitTimeout". I haven't tried it yet, but assume if you set that
to 0 it will not auto quit any more. So try something like:

defaults write com.apple.frontrow AutoQuitTimeout 0

On Apr 7, 4:52 pm, "Jon Christopher" <jon.christop...@gmail.com>
wrote:

Jon Christopher

unread,
Apr 8, 2008, 1:22:22 AM4/8/08
to frontpyth...@googlegroups.com
Thanks for the reply.  I looked all over my system for a frontrow preferences file, and all I found was this:

gala:PyeTV jchrist$ /usr/libexec/PlistBuddy ~/Library/Preferences/com.apple.frontrow.plist
Command: print
Dict {
    Muted = false
    MainMenuSelection = Music
    MusicStoreFrontID = 143441
    ScreenSaverEnabled = true
}

I've got this problem solved now, but for future reference, can you tell me where/how you found this your information?

Thanks,
Jon
Reply all
Reply to author
Forward
0 new messages