Advanced
Mailing List Archive

Mailing List Archive

  1. Home >
  2. MythTV>
  3. Dev
Is CheckForChanges() going to stay put?
mythtv at lamedomainname
Sep 10, 2002, 2:33 PM
Post #1 of 2 (1827 views)
Permalink
Isaac (et al.),

Was pulling my hair out trying to understand why things programmed from the
GUI were getting recorded but stuff done from the web interface wasn't. Had
been assuming that mythfrontend just rebuilt the recording list every few
minutes. Ooops.

I'm planning to just toggle RecordChanged in the settings table so that the
scheduler will return CheckForChanges() as TRUE. Make sense? Or do you have
any plans to change the logic in main()?

BR,

Thor



--
----------------------------------------------------------------
Thor Sigvaldason <thor@sigvaldason.com>
For my PGP/GnuPG public key, send an e-mail to thorskey@sigvaldason.com
----------------------------------------------------------------
Re: Is CheckForChanges() going to stay put? [ In reply to ]
ijr at po
Sep 10, 2002, 3:14 PM
Post #2 of 2 (1623 views)
Permalink
On Tuesday 10 September 2002 05:33 pm, Thor Sigvaldason wrote:
> Isaac (et al.),
>
> Was pulling my hair out trying to understand why things programmed from
> the GUI were getting recorded but stuff done from the web interface wasn't.
> Had been assuming that mythfrontend just rebuilt the recording list every
> few minutes. Ooops.
>
> I'm planning to just toggle RecordChanged in the settings table so that
> the scheduler will return CheckForChanges() as TRUE. Make sense? Or do you
> have any plans to change the logic in main()?

Nope, that won't be changing. Letting a running mythfrontend process know of
any changes is what that's there for.

Isaac

©2024 GT.net. A Gossamer Threads company.
5th Floor, 455 Granville St., Vancouver, BC V6C 1T1, Canada | Legal