[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
[Octave-bug-tracker] [bug #61591] set: inconsistent / incompatible behav
From: |
Nicholas Jankowski |
Subject: |
[Octave-bug-tracker] [bug #61591] set: inconsistent / incompatible behavior when modifying figure data |
Date: |
Tue, 30 Nov 2021 12:21:49 -0500 (EST) |
User-agent: |
Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/96.0.4664.45 Safari/537.36 |
Update of bug #61591 (project octave):
Release: dev => 6.4.0
Operating System: Any => Microsoft Windows
_______________________________________________________
Follow-up Comment #1:
summarizing:
1 - patch - set does not enforce x/y/zdata as columns like creation does
(warning trigger and matlab incompatibility)
2 - patch - set does not trim y/zdata to match when xdata is trimmed (matlab
incompatibility), and trimming in multiple steps would produce intermediate
warnings.
3 - patch - lets you create a patch with mismatched x/y/zdata, issuing a
warning instead of error (matlab incompatibility, but technically allowing a
superset of matlab function, so not critical)
4 - patch - replacing mismatched patch from (3) with a matched one doesn't
stop the persistent warning.
5 - line - mismatched x/ydata for plot still produces empty figure window.
6 - line/patch - octave behavior appears inversely to match matlab behavior on
what works and what produces warnings/errors.
7 - the opengl warning repetition interacts strangely with the interpreter and
repeats even after replacing problem causing the warning. (appended this and
(4) to bug #61088 about opengl warning repetition)
(all of this on 6.4.0 with windows using qt graphics_toolkit)
_______________________________________________________
Reply to this item at:
<https://savannah.gnu.org/bugs/?61591>
_______________________________________________
Message sent via Savannah
https://savannah.gnu.org/