[Top][All Lists]
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
[Octave-bug-tracker] [bug #31747] errorbar / marker type conflicts
From: |
Rik |
Subject: |
[Octave-bug-tracker] [bug #31747] errorbar / marker type conflicts |
Date: |
Wed, 28 Sep 2011 19:03:01 +0000 |
User-agent: |
Mozilla/5.0 (X11; Linux x86_64; rv:5.0) Gecko/20100101 Firefox/5.0 |
Update of bug #31747 (project octave):
Status: None => Wont Fix
Open/Closed: Open => Closed
_______________________________________________________
Follow-up 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')
_______________________________________________________
Reply to this item at:
<http://savannah.gnu.org/bugs/?31747>
_______________________________________________
Message sent via/by Savannah
http://savannah.gnu.org/
[Prev in Thread] |
Current Thread |
[Next in Thread] |
- [Octave-bug-tracker] [bug #31747] errorbar / marker type conflicts,
Rik <=