[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

[Octave-bug-tracker] [bug #34119] plotyy more restrictive that plot

From: anonymous
Subject: [Octave-bug-tracker] [bug #34119] plotyy more restrictive that plot
Date: Sat, 27 Aug 2011 20:31:57 +0000
User-agent: Mozilla/5.0 (X11; U; Linux i686; en-GB; rv: Gecko/20110822 Gentoo

Follow-up Comment #9, bug #34119 (project octave):

OK , lets assume I have some meteo data for two sites: wind speed and direct
at each site as a time series.

common x axis is time . I have four datasets for y two with units of direction
(degrees) ; two with units of speed (mph).

With your suggested solution in #5 it seems I can only plot three of these
with octave since there is no way to get two plots onto y1 using plotyy.

As for how plotyy could know, as I already stated, plot seems to manage for
example, to set marker and legend for any number of plots. It is done by
order. Why is this a show stopper for plotyy?

while many of the special case format marker used in plot() seem a bit arcane,
it could be done in a similar way. At least it would be easier to remember if
the two fns were to work in a similar way. 

Maybe if the two could be unified it would be more consistent and easier. 

If plot() could take an argument similar to gnuplots axes=x1y2 the plotyy
could be redundant. 

Most octave functions seem to have very flexible argument handling, I'm
surprised that you see this a problem.


Reply to this item at:


  Message sent via/by Savannah

reply via email to

[Prev in Thread] Current Thread [Next in Thread]