Opened 23 years ago

Closed 23 years ago

#33 closed defect (fixed)

PHP_MAPSCRIPT - ZoomPoint confused when YMax < YMin

Reported by: dmorissette Owned by: assefa
Priority: high Milestone:
Component: MapScript-PHP Version: 3.5
Severity: normal Keywords:
Cc:

Description

Date:         Thu, 09 Aug 2001 16:13:23 -0600
   From:         "ANDREW WOOLEY" <AWOOLEY@mountainland.org>
     To:         <mapserver-users@lists.gis.umn.edu>

Folks,

I am getting what seems to me to be strange results on my zoompoint method.  I 
feel like I have
followed the docs pretty closely and have even tried an example that I found in 
the email archives, but
still have yet to get a useable result.

I am using MapScript Version (Aug 1, 2001), a nightly build and when executing 
the code: 

$ptClicked = ms_newPointObj(); 
$ptClicked->setXY($mainmap_x,$mainmap_y); 

$extent = ms_newRectObj();
$extent->setextent($map->extent->minx, $map->extent->miny, $map->extent->maxx, 
$map->extent->maxy); 

$map->zoompoint(2, $ptClicked, 600, 600, $extent); 

When I echo the extent minx, etc. it gives reasonable coordinates for the map 
extent (1800193, 825044,
2115496, 542882), however, after this code executes and I echo the new extent, I 
get good values for
some of the coordinates but not others (1877442.235, -78702.92, 2035093.735, 
78702.92).  Can someone
explain to me what I am doing wrong and why the negative values show up?  
Thanks.

Change History (3)

comment:1 by dmorissette, 23 years ago

You wrote that your original extents were:
  (1800193, 825044, 2115496, 542882)

I notice that YMin > YMax ... maybe that confused the ZoomPoint()
function... try again with YMin < YMax ... and if it works this time
then please file a bug in the MapServer bugzilla about this and we'll
fix ZoomPoint() to deal with this properly.


comment:2 by dmorissette, 23 years ago

ANDREW WOOLEY wrote:
> 
> This is the correct answer:  For my rect extent, I changed the maxy and the 
miny and it worked as advertised.  Thanks very much for the assistance.
> 

comment:3 by assefa, 23 years ago

Resolution: fixed
Status: newclosed
Added an error message when the extents are wrong. I think it is better to 
inform the user than "flipping" the coordinates.
Note: See TracTickets for help on using tickets.