G.axes.range function unintuitive

[GoogleCodeExporter]

When you call the

G.axes.range(0, 1)

twice, the range items get _added_ to the range. This is unexpected
behaviour. Normally, one expects a function called 

G.axes.range(0, 1)

to act like

G.axes.set_range(0, 1)

and not like

G.axes.add_range(0, 1)

If this is not fixed, then the documentation should be clear on this point,
as it caused me a lot of headache.

Original issue reported on code.google.com by markess...@gmail.com on 23 Aug 2008 at 9:22

[GoogleCodeExporter]

It all starts w/ typing. You call G.axes.type first then for each subsequent
G.axes.range call it adds them IN ORDER depending on the types you declare. An 
example:

G.axes.type('xy')
G.axes.range(0,360) # x range
G.axes.range(0,180) # y range

Original comment by justquick on 23 Aug 2008 at 8:21

• Changed state: Invalid

[GoogleCodeExporter]

After much thought, it turns out you were right, i hate the way it does axes 
index
assignment. Now for all axes functions, you must pass in your index as the 
first argument
{{{
G.axes.type('xy')
G.axes.range(0, 0,360) # x range
G.axes.range(1, 0,180) # y range
}}}

Original comment by justquick on 21 Apr 2009 at 2:29

• Changed state: Started

[GoogleCodeExporter]

Fixed in version 0.8!

Original comment by justquick on 1 May 2009 at 10:01

• Changed state: Fixed