octave-bug-tracker
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

[Octave-bug-tracker] [bug #30461] legend should work for lines with diff


From: David Bateman
Subject: [Octave-bug-tracker] [bug #30461] legend should work for lines with different parents
Date: Sat, 18 Sep 2010 20:32:13 +0000
User-agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.9.0.14) Gecko/2009091010 Iceweasel/3.0.14 (Debian-3.0.14-1)

Follow-up Comment #8, bug #30461 (project octave):

Well after a bit of testing of my legend code with the gnuplot backend and
the terminals wxt, x11 and eps and using a number of different fonts it became
evident that although the text extents calculation is ok for the wxt with my
default font, its pretty bad in most other cases and there is no easy fudge to
get the text extents code working with gnuplot.

The next choice is to keep the new fltk compatible legend code, but ignore
the legend axes in the gnuplot backend while recovering the information for
use with the gnuplot legend code. I have this working now with two issues

- The first is this bug report. Yes I have fixed this for the fltk backend,
but the gnuplot "set key" code doesn't allow elements of the key to be taken
from two different plots. My solution for this is going to be that I'll add a
line to the figure but outside the axes so that it is not visible, and then
I'll have an invisible line that I can add the key to.

- My second issue is that the gnuplot code positions the axes with code like

set origin 0.13, 0.149823076082663;
set size noratio 0.775, 0.775176923917337;

and this plays havoc the "set key outside" option of gnuplot. That is the
axis size is modified by the "set key outside" option, but the  key remains
inside the  axis. I don't see a good way of fixing this.

As this code doesn't seem to break anything, I can fix the first issue with
an incremental fix, it adds support for fltk legends (addressing this bug in
that case) and address the bug #29348 I applied my changeset in 

http://hg.savannah.gnu.org/hgweb/octave/rev/e81914f3921f

Ben do you have any ideas of how to treat the second issue?

D.


    _______________________________________________________

Reply to this item at:

  <http://savannah.gnu.org/bugs/?30461>

_______________________________________________
  Message sent via/by Savannah
  http://savannah.gnu.org/




reply via email to

[Prev in Thread] Current Thread [Next in Thread]