Re: Clipping of arrows buggy

[Ethan M. <merritt@u.washington.edu>]

On Tuesday 18 January 2005 11:09 am, Harald Harders wrote:
> 
> On Mon, 17 Jan 2005, Ethan Merritt wrote:
> 
> >
> > I see no difference in the output before applying your patch
> > and after applying your patch.  What, exactly, is the change
> > supposed to be?
> 
> The difference only appears in the 3d plots (both with and without
> multiplot). All arrows and labels that start outside the boundaries
> 0 <= screen coordinate <= 1 are missing. Since the screen may be larger
> using 'set size 1.4,1.4', for example, this is not okay for x>1 and y>1.

You have a different understanding of "screen" than I do.
"set size" does not change the screen. 

The documentation says:
 `screen` specifies the screen area (the entire area---not just
  the portion selected by `set size`), with 0,0 at bottom left
  and 1,1 at top right

In other words, if it is outside the area
[0 < screen x < 1][ 0 < screen y < 1]
it should never be visible.
And yes, it is true that labels whose origin is outside the
visible area will not be drawn.  That is intentional.

So I think the only case being mis-handled by the current code
is if an arrow starts from off-screen in one direction, crosses
part of the screen, and terminates at another off-screen location.

Is that the case you are concerned about? 

Here's a radically different proposal:

The command "set size x, y" should be limited to values
of x and y between 0 and 1.  It basically doesn't make sense
to set a size that is bigger than your screen.  I know some
people will dislike this because they have existing scripts
that sort of work, but I think it is a case of relying on
behavior that is undocumented and not guaranteed.


-- 
Ethan A Merritt       merritt@u.washington.edu
Biomolecular Structure Center
Mailstop 357742
University of Washington, Seattle, WA 98195