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
>
>
>
>
>