[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
[Octave-bug-tracker] [bug #53214] area.m needs update to implement ShowB
From: |
Nicholas Jankowski |
Subject: |
[Octave-bug-tracker] [bug #53214] area.m needs update to implement ShowBaseline and other properties |
Date: |
Wed, 25 Aug 2021 21:58:55 -0400 (EDT) |
User-agent: |
Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/92.0.4515.159 Safari/537.36 |
Follow-up Comment #10, bug #53214 (project octave):
in area.m, then patch.m, the axis limits are set in the call to __go_patch__
(line 176)
in plot.m, then __plt__.m, the axis limits are set in the call to __go_line__
(line 435)
both are compiled functions in libinterp/corefcn/graphics.cc, both are passed
x-data consisting of [1:10]. so both are internally deciding to set the left
limit to 0 rather than the lowest value. As before patch hands off the job it
has set the xlim to [-1 1], it seems to be a case of resetting axes min to 0,
rather than just neglecting to update it to x_data_min.
not set up to step through compiled functions to verify, but taking a quick
peek at graphics.cc, both call GO_BODY(patch/line). that's where i get lost
in the 14k line file, so someone familiar will maybe need to see where it's
not setting the left xlim to be 1.
I would suggest both plot and area get a compatibility test added such as:
## test default plot limits
%!test
%! h = plot(rand(10))
%! assert(xlim(gca),[1 10])
_______________________________________________________
Reply to this item at:
<https://savannah.gnu.org/bugs/?53214>
_______________________________________________
Message sent via Savannah
https://savannah.gnu.org/