The same information he can get with Google Chrome Developer Tool (resources
tab)...
-Original Message-
From: mapguide-users-boun...@lists.osgeo.org
[mailto:mapguide-users-boun...@lists.osgeo.org] On Behalf Of Jackie Ng
Sent: Tuesday, November 29, 2011 2:43 AM
To:
Is it on purpose that Legend items are hardcoded to 16x16 pixels in the
Maestro API?
When using dashed lines on the map, the legend image is too small to tell
the difference between different dashed or dotted lines:
http://osgeo-org.1803224.n2.nabble.com/file/n7042355/legendimage.png
I think this is indeed hard-coded. This is why Maestro API does not offer an
overload with custom sizes, because MapGuide will not respect it.
- Jackie
--
View this message in context:
http://osgeo-org.1803224.n2.nabble.com/Legend-icons-hardcoded-to-16x16-pixels-tp7042355p7042382.html
Sent from
Here is an example where the API 16x16 has been changes to 160x16. So it
works (using MapGuide 2009):
http://osgeo-org.1803224.n2.nabble.com/file/n7042538/example.png example.png
Hans...
--
View this message in context:
Hi,
my application allows it to make a new MapDefinition from the current
RuntimeMap. When trying to iterate over the RuntimeMapLayerCollection to
create the IMapLayer
mapDef.AddLayer(rtLayer.Group, rtLayer.Name, rtLayer.LayerDefinitionID);
an error occurs on layers that have a
Guess I stand corrected then :) I'll look at providing an overload in the way
you've described
- Jackie
--
View this message in context:
http://osgeo-org.1803224.n2.nabble.com/Legend-icons-hardcoded-to-16x16-pixels-tp7042355p7042682.html
Sent from the MapGuide Users mailing list archive at
Perhaps the hard coded PNG could be an option too? I don't know if anyone
would want a JPG or something else, but now that you are at it.
Hans...
--
View this message in context:
http://osgeo-org.1803224.n2.nabble.com/Legend-icons-hardcoded-to-16x16-pixels-tp7042355p7042685.html
Sent from the
When you add a layer to the Map Definition, if it is the first layer to be
added, Maestro tries to be smart and grabs the extents of that layer and
sets the extents of the Map Definition to match.
This obviously naively assumes the first layer you add has no issues and can
be queried for extents.
Most of the time, any limit is imposed by the underlying provider (I know
that ODBC definitely has some where clause size limitations). But there's no
way in MapGuide to determine what this limit is if any, hence the suggestion
of a batched querying approach which will reduce the your filters to
Hi,
I am developing a mapguide application using visual studio 2010 and C#. My
question is : I opend a page with an ajaxviewer, made some changes to the
map like change a layer visibility and filtered another layer with success.
Then I keep the first page opened and opened a second page with an
This is because your second viewer using the same session id has overwritten
the runtime map state from your first map in the process of initializing.
Using the same session id means the same resource id will be calculated for
saving the runtime map state and selection.
- Jackie
--
View this
What I have to do to replicate the actual map (with the changes made) to a
new map in another page ?
--
View this message in context:
http://osgeo-org.1803224.n2.nabble.com/Passing-the-SessionId-to-a-new-map-does-not-reflect-the-changes-made-tp7043424p7043487.html
Sent from the MapGuide Users
12 matches
Mail list logo
