Armin- Back on October 14, someone posted a problem with zoom2extent, but he apparently got it working on his own before you could answer. I just got the same exact behavior when I recently upgraded to 4.1.1... never seen it before in 2 years of using pmapper. The function call to zoom2extent from the Result window is putting a number and @ in front of the second parameter.
For example, looking up layer=pipeline gid=14563, the function call is constructed as zoom2extent('pipelines', '4...@14563',...) rather than the expected zoom2extent('pipelines', '14563',...) Curiously, this only happens when the Result window is derived from the Identify or Select menu bar. The same Result window derived from a Search works just fine. Your help would be much appreciated!! Chris Domangue ------------------------------------------------------------------------------ Increase Visibility of Your 3D Game App & Earn a Chance To Win $500! Tap into the largest installed PC base & get more eyes on your game by optimizing for Intel(R) Graphics Technology. Get started today with the Intel(R) Software Partner Program. Five $500 cash prizes are up for grabs. http://p.sf.net/sfu/intelisp-dev2dev _______________________________________________ pmapper-users mailing list pmapper-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/pmapper-users