Thanks again Jackie. Not a major issue but it does offer more control over
default output.
To prevent breaking existing client viewers that rely on this information,
the default setting could be left to output the bounds data, with a
server-side variable that disables it if desired. As you said, p
That's great advice Martin, I try not use Composite unless I have to (like
blocks).
--
Sent from: http://osgeo-org.1560.x6.nabble.com/MapGuide-Users-f4182607.html
___
mapguide-users mailing list
mapguide-users@lists.osgeo.org
https://lists.osgeo.org/ma
Support for omitting bounds information in QUERYMAPFEATURES:
a) Is an API change
b) Would break our existing client viewers that relied on this information
(eg. Zoom to selected feature) if omitted by default. It would also require
some modification from our viewers to gracefully operate in the
Thank you Jackie. I suspected that was the case, as I looked in many places
for evidence of that parameter, although I did not consider the
webconfig.ini.
On a related note, it would be nice to turn off sending Bounds as part of
the Feature data provided in the JSON to mapagent.fcgi request, i.e.
