[mythtv] Re: [mythtv-users] Pre-scaling theme images (fwd)

Isaac Richards ijr at po.cwru.edu
Wed Sep 15 19:43:59 EDT 2004


On Wednesday 15 September 2004 06:17 pm, Neil Whelchel wrote:
> On Wed, 15 Sep 2004, Joseph A. Caputo wrote:
> > On Wednesday 15 September 2004 07:10, Thomas Börkel wrote:
> > > HI!
> > >
> > > Joseph A. Caputo wrote:
> > > > It appears that every time you run mythfrontend *at a different
> > > > resolution*, it removes the 'stale' themecache and generates one
> > > > for the current resolution.  For instance, I normally run at
> > > > 800x600, and I *never* get the "generating scaled-images..."
> > > > progress bar.  Today I ssh-ed in from work and ran with a remote
> > > > 1280x1024 display.  I saw the progress bar (as expected), but I
> > > > also saw a terminal message "removing stale cache blue.800.600".  I
> > > > checked, and sure enough, I now have a blue.1280.1024 cache and NO
> > > > blue.800.600 cache.  I fully expect that the next time I fire up my
> > > > main frontend I will see the progress bar.
> > > >
> > > > Perhaps it would be a good idea to have myth *not* delete a
> > > > themecache just because it's not the current resolution?
> > >
> > > I write protect the cache dir and sub dirs after they have been
> > > created.
> >
> > Hmmm, not a bad idea, but won't that cause problems as themes get
> > updated and images get added/removed/changed ?  In any event it would
> > be nice for the code to do the right thing.
> >
> > (to the -dev list):  is there a good reason for this behavior?  If not,
> > I'll look into patching it to not delete the theme cache, or at least
> > maybe to come up with a better way of determining if a theme cache is
> > truly 'stale'.
>
> [SNIP]
> Simple..
> Find the latest file modification date in the selected theme directory, if
> it is newer than the cached image, replace it, if not skip it.

Please read the thread before replying.

Isaac


More information about the mythtv-dev mailing list