[Top][All Lists]
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: image cache
From: |
Miles Bader |
Subject: |
Re: image cache |
Date: |
Tue, 16 Dec 2008 10:41:59 +0900 |
Chong Yidong <address@hidden> writes:
> Note that fixing requires changing all the functions in image.c that
> require a frame argument, so that they use a terminal argument instead.
> Otherwise, if you associate image caches to terminals, you run into
> problems with terminals that have no frame (e.g. terminals created using
> x-open-connection), because you can't supply those image functions with
> a frame argument.
Frameless terminals can't use those functions currently anyway, right?
So one could change the current implementation to put the cache in the
terminal data structure, but preserve the current interfaces. This
would yield more sharing, without losing functionality.
-Miles
--
You can hack anything you want, with TECO and DDT.
- Re: Memory leak in keyboard variables?, (continued)
- Re: Memory leak in keyboard variables?, Stefan Monnier, 2008/12/11
- Re: Memory leak in keyboard variables?, Kenichi Handa, 2008/12/14
- Re: Memory leak in keyboard variables?, Chong Yidong, 2008/12/14
- image cache (was: Memory leak in keyboard variables?), Stefan Monnier, 2008/12/14
- Re: image cache (was: Memory leak in keyboard variables?), Eli Zaretskii, 2008/12/14
- Re: image cache, Stefan Monnier, 2008/12/15
- Re: image cache, Chong Yidong, 2008/12/15
- Re: image cache, Stefan Monnier, 2008/12/15
- Re: image cache,
Miles Bader <=
- Re: image cache, Chetan Pandya, 2008/12/15
- Re: image cache, Chetan Pandya, 2008/12/16
- Re: Memory leak in keyboard variables?, Kenichi Handa, 2008/12/15
Re: Memory leak in keyboard variables?, Chetan Pandya, 2008/12/15