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

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

[Octave-bug-tracker] [bug #40064] Legend "interpreter" property not work


From: Mike Miller
Subject: [Octave-bug-tracker] [bug #40064] Legend "interpreter" property not working correctly
Date: Sun, 01 Jun 2014 04:56:11 +0000
User-agent: Mozilla/5.0 (X11; Linux x86_64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/34.0.1847.132 Safari/537.36

Follow-up Comment #35, bug #40064 (project octave):

> Are there any other text rendering functions aside from legend() which
presently obtain their interpreter default via the DefaultLineInterpreter
property?

I don't know. But legend no longer obtains its interpreter value from the
DefaultLineInterpreter property, this is incorrect behavior in 3.8.1 but is
fixed for future releases (as Rik noted in comment #25 and I missed when I
posted my last comment).

> Are there presently any other DefaultXxxxInterpreter properties other than
Line, Text, and Axes?

As far as I can tell, the following objects have the interpreter property:
axes, line, text, patch, and surface. So there is a default interpreter
property for each of these object types.

> Are there presently any plans to add any other DefaultXxxxInterpreter
properties beside those three?

I don't know. Specifically there will be no DefaultLegendInterpreter, because
a legend is, by Matlab's definition, an axes object that inherits some of its
properties from axes, but explicitly not the Interpreter property.

Does that answer your questions?

    _______________________________________________________

Reply to this item at:

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

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




reply via email to

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