[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
[Octave-bug-tracker] [bug #50041] Setting non-valid values for graphics
From: |
Markus Mützel |
Subject: |
[Octave-bug-tracker] [bug #50041] Setting non-valid values for graphics properties should throw an error |
Date: |
Thu, 12 Jan 2017 19:47:01 +0000 (UTC) |
User-agent: |
Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:51.0) Gecko/20100101 Firefox/51.0 |
URL:
<http://savannah.gnu.org/bugs/?50041>
Summary: Setting non-valid values for graphics properties
should throw an error
Project: GNU Octave
Submitted by: mmuetzel
Submitted on: Thu 12 Jan 2017 07:47:00 PM GMT
Category: Plotting
Severity: 3 - Normal
Priority: 5 - Normal
Item Group: Incorrect Result
Status: In Progress
Assigned to: None
Originator Name:
Originator Email:
Open/Closed: Open
Discussion Lock: Any
Release: dev
Operating System: Any
_______________________________________________________
Details:
Setting non-valid values for some properties leads to un-expected results
(e.g. bug #49755: axis equal clears plot). These should instead throw an error
(as they do in Matlab).
Attached is a work in progress patch that adds new constraints (finite_type)
for array_properties, row_vector_properties and double_properties. It also
expands the support of min-max-constraints that we already have for
double_properties to array_properties and row_vector_properties.
I added these constraints to some of the properties to which they apply.
However, I would like to know whether this is the correct approach before I
continue.
I am adding Pantxo to the CC list since this is very similar to what he did in
task #11311. Pantxo, could you please comment when you have the time?
I also changed "plotboxaspectratio" and "dataaspectratio" from
array_properties to row_vector_properties since this is how they are handled
in Matlab. Should this change be made in a separate bug report?
_______________________________________________________
File Attachments:
-------------------------------------------------------
Date: Thu 12 Jan 2017 07:47:00 PM GMT Name: wip_constraints_finite_type.patch
Size: 11kB By: mmuetzel
<http://savannah.gnu.org/bugs/download.php?file_id=39452>
_______________________________________________________
Reply to this item at:
<http://savannah.gnu.org/bugs/?50041>
_______________________________________________
Message sent via/by Savannah
http://savannah.gnu.org/
- [Octave-bug-tracker] [bug #50041] Setting non-valid values for graphics properties should throw an error,
Markus Mützel <=
- [Octave-bug-tracker] [bug #50041] Setting non-valid values for graphics properties should throw an error, John W. Eaton, 2017/01/12
- [Octave-bug-tracker] [bug #50041] Setting non-valid values for graphics properties should throw an error, Markus Mützel, 2017/01/13
- [Octave-bug-tracker] [bug #50041] Setting non-valid values for graphics properties should throw an error, John W. Eaton, 2017/01/17
- [Octave-bug-tracker] [bug #50041] Setting non-valid values for graphics properties should throw an error, Pantxo Diribarne, 2017/01/18
- [Octave-bug-tracker] [bug #50041] Setting non-valid values for graphics properties should throw an error, Markus Mützel, 2017/01/18
- [Octave-bug-tracker] [bug #50041] Setting non-valid values for graphics properties should throw an error, Markus Mützel, 2017/01/20
- [Octave-bug-tracker] [bug #50041] Setting non-valid values for graphics properties should throw an error, Pantxo Diribarne, 2017/01/31