|
From: Aapo L. <aap...@gm...> - 2005-11-11 11:41:27
|
On Wed, 2005-11-09 at 16:13 -0800, Ethan Merritt wrote:
> Well, in this particular case it is caused by the fact that when
> post.trm expands its drawing limits, it does not change the values
> of term->xmax and term->ymax. Therefore if you clip against them,
> it doesn't work. So far as I know, other terminal drivers
> correctly report what their actual limiting coordinates are.
What is the exact reason that prevents fixing post.trm (and maybe other
broken terminals) so that it would correctly update term->xmax and
term->ymax? I would imagine that it wouldn't be terribly difficult to
change accordingly the values of these two variables when the postscript
internal canvas grow. Is it somehow a problem with backward
compatibility?
I wonder if the problem with the inconsistencies between different
terminals and backward compatibility is so severe that a new global
option "set terminalmode {old|new}" is needed. I believe that option
would be quite horrible from the maintaining point of view.
Aapo
|