|
From: Ethan M. <merritt@u.washington.edu> - 2005-11-09 22:48:37
|
On Wednesday 09 November 2005 02:32 pm, Harald Harders wrote: > > I once have provided a patch that worked, storing both the term boundaries > as they are now and the canvas size. It wasn't applied to cvs. I remember > that you were one of the people that complained that this was not the > right way to do it. But it worked. I do not recall seeing such a patch. Could you remind me which one that is? I don't see anything on SourceForge that seems to match your description. > term->xmax means the position, where the screen coordinate is 1 > term->ymax means the position, where the screen coordinate is 1 > term->xcanvas is the maximal screen coordinate in the canvas > term->ycanvas is the second maximal screen coordinate in the canvas > > This has been provided by my rejected patch, to remind you once again. I would be glad to look at such a patch. As I said, I don't recall seeing anything like that. So you extended the TERM_TABLE entries for all terminal types to hold canvas size values? That sounds like a lot more work than attempting to maintain the canvas size in the core code, but you may be right that in the long run it is the only approach that can succeed. Too bad it means revisiting every single terminal driver. -- Ethan A Merritt merritt@u.washington.edu Biomolecular Structure Center Mailstop 357742 University of Washington, Seattle, WA 98195 |