[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
[Octave-bug-tracker] [bug #66728] legend inconsistencies
From: |
Muhali |
Subject: |
[Octave-bug-tracker] [bug #66728] legend inconsistencies |
Date: |
Wed, 29 Jan 2025 08:26:30 -0500 (EST) |
Follow-up Comment #4, bug #66728 (group octave):
[comment #2 comment #2:]
> * Issue 2: Now that I read the help text for legend more carefully, I see it
> is already clearly stated that unless and axes handle HAX is specified as
> first argument, it will "Display a legend for the current axes...". Which in
> our case is the latest created axes, ax(3).
You are right. But I had expected that text near where the HOBJS are
mentioned.
> * Issue 3: I couldn't find any mention of a restriction in ML doc saying that
> a legend associated to a given axes should only label graphics objects
> pertaining to this axes. Does ML also allow graphics objects from different
> figures in a single legend? E.g., does the following work and if so what does
> happen?
Yes, apparently. But the 3 legends all appear in the first figure, although
gcf = 2. But note that Matlab only offers axis objects as a first argument, no
other graphic handles.
_______________________________________________________
Reply to this item at:
<https://savannah.gnu.org/bugs/?66728>
_______________________________________________
Message sent via Savannah
https://savannah.gnu.org/
signature.asc
Description: PGP signature