Re: [Gnuplot-bugs] small defects in 4.2

[<HBB...@t-...>]

pl...@pi... wrote:

> 1.
> resizing the wx window the graph scales well but so does the text. Once  
> the drag is finished it remains too large until a replot is done.

Done on purpose by the implementors of the wx driver.

> 2.
> Dragging the window by any size handle or corner does resize the graph but  
> it remains at the same aspect ratio. Again hitting the replot button (or  
> reloading the .gnu) will resize to fit the new window fully.

Ditto.

> 3. colours do not come out the same in outputting to png , for example.  

The same ... as what?

> It's rather confusing seeing different output stored as an image and  
> annoying in transmitting to others since I cant say "look at the green  
> line" because it's probably blue in the other output format.

You _could_ look at the actual file you're sending them, though ;->

There's a price to be paid for having a tool that just works, without 
you having to rewrite the entire script, for so many different output 
formats.  One part of that price is that while gnuplot will try to do 
something useful for a given script regardless of the terminal driver 
it's run over, it can't be guaranteed that it'll do the _same_ for all 
of them.

> 4. I had a lot of time wasted trying to get y2 scale markings. I found the  
> label readily enough but could not understand why I was not getting the  
> tics and numerical markings. I now realise it required that I explicitly  
> set y2tics . What confused me is that this is not the case with y1 they  
> just come up automatically.

That's because every graph has *some* data on the y1 axis, while most 
graphs neither neither nor want a y2 axis.  There's also historic 
precedent to be maintained.  y2 axes were added to gnuplot a long time 
after the default behaviour of y1 axes was defined to have the tics 
mirrored to where the y2 axis would go.  This default behaviour would 
get in the way of y2 tics.

> It would seem more logical and consistant if y2tics behaved in the same  
> way as the main y-axis, ie as soon as there is a y2scale defined the  
> default tics and numerical label come up as well.

That's not actually how the y1 axis behaves, so why should y2?  The 
trick being that "there is a y1scale defined" is a non-event.  It's 
always defined.