[mythtv-users] mythwelcome and shutdown/wakeup
ebenblues at yahoo.com
Mon Jan 21 02:38:02 UTC 2008
----- Original Message ----
> From: Ma Begaj <derliebegott at gmail.com>
> To: Discussion about mythtv <mythtv-users at mythtv.org>
> Sent: Sunday, January 20, 2008 4:20:22 PM
> Subject: Re: [mythtv-users] mythwelcome and shutdown/wakeup
> 2008/1/20, John Veness :
> > James Hood wrote:
> > > Hi,
> > >
> > > I'm working on building my first myth box and I'm very
with the functionality and quality of the software so far. I have
questions related to the auto shutdown/wakeup feature of mythtv.
> > >
> > > First, does mythbackend take into account the next time it
supposed to grab EPG data when it calculates the next wakeup time? I
this post from June 2007 which provides a SetAlarm script that
through the pain of searching the mythfilldatabase log for the
suggested update time, checks if
> > > it's sooner than when mythbackend wants to wake the box up
uses the closer time as the wakeup time.
> > >
> > >
> > > I'm hoping that mythbackend does this automatically in 0.20
maybe in svn)?
> > >
> > > Second, I noticed on a box that's both a frontend and backend,
mythbackend won't auto-shutdown the box if mythfrontend is
even if mythfrontend has been sitting idle at the menu screen for a
period of time. I've read about mythwelcome, but as far as I can
it seems like more of a workaround. Frankly, the mythwelcome screen
very confusing for someone who doesn't know anything about how
works, i.e., my wife. To me, the ultimate user friendly experience
be to not have mythwelcome at all, and to have some way for
to know if the frontend (or any frontend) has been sitting idle at
menu for X number of minutes and initiate shutdown of the box then.
know the coding of that may be more complex, but I think the
scheme surfaces far too much detail to the user.
> > >
> > > I couldn't find any discussion about this in the archives so I
this isn't something that's already been talked about, but if not,
be interested in discussing more user-friendly possibilities.
willing to put my money where my mouth is and contribute some code, but
didn't know if there was a good reason why it's implemented the way
> > >
> > > Thanks,
> > > James
> > When I first came across mythwelcome, I too thought that it was a
> > a kludge. Why does there have to be a separate executable, just
> > the backend know that noone is running the frontend. Couldn't instead
> > the top-level screen of mythfrontend act as a welcome/idle screen?
> > you suggest, some sort of idle timer, so it doesn't matter if
> > does not navigate up to the top-level.
> > Anyway, since then I've just accepted things are the way that
> > I've told my wife that she needs to Esc out until it will go
> > and soon the box will automatically shutdown if it's not
> > and it seems acceptable.
> > Cheers,
> > John
> I am xscreensaver and a small perl script to handle this. When the
> screensaver turns black (blank), a perl script is started which kills
> mythfrontend. there is somewhere on the list here.
> mythtv-users mailing list
> mythtv-users at mythtv.org
Thanks for the responses. I agree these are all valid workarounds. I guess I was just trying to get a discussion going on how it *should* work from a usability standpoint with no hacking or workarounds necessary. From the responses, it sounds like at least one other person feels like I do about mythwelcome being kludgy and others have to use external scripts to live without it. I'll try to look and see how difficult this would be to implement in the code.
"The humble learn the fastest because they don't waste time on defending a false image."
Never miss a thing. Make Yahoo your home page.
More information about the mythtv-users