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

[Dan Sebald]

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

It looks like the "displayname" originates from legend.m.  There are three or
four lines of code that either set or get "displayname" from a listener.

This doesn't seem like a difficult fix (maybe just add another listener for
"interpreter"?), but the question is more how to handle the mods to the
graphics object.  Some rules like the following:

1) If the legend's interpreter is set, that changes all the child object
interpreters to the same value.

2) If the graphical object's interpreter is set, that should cause the
associated text object in the legend's child list to have the same
interpreter.  Hmm, but how does the legend know what graphics object is
connected to the child in its list?

Really, the better approach is to retain handle/pointer info rather than
duplicate text strings without having some form of connection.

    _______________________________________________________

Reply to this item at:

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

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