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

[Glenn Golden]

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


I understand that the legend object's interpreter property defaults to 'tex'. 
But there's still something wrong: It's inconsistent that with
DefaultAxesInterpreter set to 'none' the legend object reports its interpreter
as 'tex', and yet renders its text as though the interpreter is 'none'. 
That's what I reported in the previous comment. Are you seeing that also?
Please answer that question first so we can at least figure out whether we're
even observing the same behavior.

If you're also seeing this behavior, then I claim that it is nonsensical,
because it implies that one of the following unpleasant states of affairs must
be the case:

Either:

  1. The function get(h, 'interpreter') on a legend object returns a value
('tex') which is known not to agree with its actual text rendering
functionality ('none'),

OR

  2.  The text rendering functionality of a legend object has nothing to do
with its reported interpreter value, but only with the value of its parent
axes object.

To me, either of the above interpretations seems inconsistent and misleading.
A user has the reasonable expectation the text rendering functionality of an
object agrees with its reported interpreter property. If you're seeing what
I'm seeing, it doesn't.

If this doesn't seem inconsistent to you, can you explain slowly and carefully
why? I'm not getting it.



    _______________________________________________________

Reply to this item at:

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

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