bugGNU Octave - Bugs: bug #31747, errorbar / marker type conflicts

 
 

bug #31747: errorbar / marker type conflicts

Submitter:  Ben Abbott <bpabbott>
Submitted:  Thu 02 Dec 2010 01:23:17 PM UTC
   
 
Category:  Plotting Severity:  3 - Normal
Priority:  5 - Normal Item Group:  Incorrect Result
Status:  Wont Fix Assigned to:  None
Originator Name:  Ben Abbott Open/Closed:  * Closed
Release:  * dev Operating System:  * Mac OS
Fixed Release:  None Planned Release:  None
* Mandatory Fields

Add a New Comment Rich Markup
   

Wed 28 Sep 2011 07:03:01 PM UTC, comment #1: 

I don't think this is a problem.  The errorbar() command specifically requires that it's linespec appear first.  After that, any valid line specification can appear.  Thus, there is a way to generate both xerrorbar plots and use the '>' linespec and there isn't a conflict.

Example code


errorbar (1:10, 1:10, ones(10,1), '>>b')



Rik <rik5>
Group administrator
Thu 02 Dec 2010 01:23:17 PM UTC, original submission:  

errorbars and markers share a common format spec, ">"

Should errorbar format be changed to avoid conflicts with the marker specification for line objects?

Ben Abbott <bpabbott>
Group Member

 

(Note: upload size limit is set to 16384 kB, after insertion of the required escape characters.)

Attach Files:
   
   
Comment:
   

No files currently attached

 

Depends on the following items: None found

Items that depend on this one: None found

 

Carbon-Copy List
  • -email is unavailable- added by rik5 (Posted a comment)
  • -email is unavailable- added by bpabbott (Submitted the item)
  •  

    There are 0 votes so far. Votes easily highlight which items people would like to see resolved in priority, independently of the priority of the item set by tracker managers.

    Only group members can vote.

     

    Follow 2 latest changes.

    Date Changed by Updated Field Previous Value => Replaced by
    2011-09-28 rik5 StatusNone Wont Fix
        Open/ClosedOpen Closed

    Back to the top

    Powered by Savane 3.13-758e.
    Corresponding source code