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: Rik
Subject: [Octave-bug-tracker] [bug #40064] Legend "interpreter" property not working correctly
Date: Wed, 07 May 2014 23:56:02 +0000
User-agent: Mozilla/5.0 (X11; Ubuntu; Linux x86_64; rv:29.0) Gecko/20100101 Firefox/29.0

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

I think Octave is behaving correctly.  The assumption in the script that
setting the default 'interpreter' property for Text objects will apply to all
other graphic primitives, e.g., Line or Axes, is incorrect.  From the script:


# Expectation of the following statement is that the 'interpreter' property
# for all subsequently created graphics objects will be 'none', but this does
# not seem to be the case, as the example show. Was not able to locate
# authoritative documentation on this property in the info(1) pages, but
# cargo-cult usage seems to agree with the above expectation.
#
set(0, 'DefaultTextInterpreter', 'none');


To set the default for another primitive object, such as Line or Axes, you
must use another set command.


set(0, 'DefaultLineInterpreter', 'none');
set(0, 'DefaultAxesInterpreter', 'none');


If I set the extra defaults for each type of object used then your script runs
as expected.


    _______________________________________________________

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]