[Octave-bug-tracker] [bug #50496] Legend and object 'interpreter' property disagree

[Dan Sebald]

Follow-up Comment #19, bug #50496 (project octave):

Attached is the change I've been using for a few days.  It adds an additional
input variable to __maybe_munge_text__(), placing the decision of what
interpreter to use at the point of the function call.  That seems the simplest
change.

I've tested that text (which doesn't appear in legends, hence no conflict of
interpreter), title, xlabel, ylabel, legend all work independently.  And the
following makes sense:


octave:20> set(kids(1), 'interpreter', 'none')
warning: 'interpreter' is deprecated and will be removed from a future version
of Octave
octave:21> ht = text(0.5, 0.5, 'e=mc^2')
ht = -80.733
octave:22> set(ht, 'interpreter', 'none')


Do you think it would be worthwhile to add a demo to "text" to show that the
text's interpreter property is working?

Note that this change means individual legend keys can have different
interpreter settings; obvious I suppose.  But if Octave wanted to supply such
capability, perhaps a clearer way would be to add a property
"displayinterpreter" to go along with "displayname", e.g.,

'displayinterpreter'  [ latex | none | tex | {legend} ]


(file #40012)
    _______________________________________________________

Additional Item Attachment:

File name: octave-legend_or_text_interpreter-djs2017mar16.patch Size:6 KB


    _______________________________________________________

Reply to this item at:

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

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