# HG changeset patch
# User Shai Ayal <shaiay@users.sourceforge.net>
# Date 1203969037 -7200
# Node ID d3dcfdfdc43457be6b6025fc6c59e94e7fbc8907
# Parent  1357bcae6e29a95fc1d71d0e623c2352398c77be
handle unsorted limits when calculatin gticks and limits

diff -r 1357bcae6e29 -r d3dcfdfdc434 src/ChangeLog
--- a/src/ChangeLog	Mon Feb 25 21:45:11 2008 +0200
+++ b/src/ChangeLog	Mon Feb 25 21:50:37 2008 +0200
@@ -1,5 +1,8 @@
 2008-06-04  Shai Ayal  <shaiay@users.sourceforge.net>
 
+	* graphics.cc (axes::properties::calc_ticks_and_lims): Make sure
+	that lo <= hi.
+
 	* graphics.h.in (axes::pixel2coord, axes::coord2pixel): New functions.
 
 	* graphics.cc (convert_position): No longer static.
diff -r 1357bcae6e29 -r d3dcfdfdc434 src/graphics.cc
--- a/src/graphics.cc	Mon Feb 25 21:45:11 2008 +0200
+++ b/src/graphics.cc	Mon Feb 25 21:50:37 2008 +0200
@@ -2607,6 +2607,13 @@
 
   double lo = (lims.get ().matrix_value ()) (0);
   double hi = (lims.get ().matrix_value ()) (1);
+  // FIXME should this be checked for somewhere else? (i.e. set{x,y,z}lim)
+  if (hi < lo) 
+    {
+      double tmp = hi;
+      hi = lo;
+      lo = tmp;
+    }
   
   double tick_sep = calc_tick_sep (lo , hi);