Thomas,
thanks for the hint, but as I am using MGOS 2.1 (which maps more or less to
MGE 2010) and it is working fine on a Windows 2003 server it should be
something different.
Most annoying is the fact there is no error message indicating in what
direction I have to search (is it a problem with
It appears that stack trace comes from 2.0 web extension dlls. You should be
using dlls from your 2.1 installation. Or is this not the case?
- Jackie
--
View this message in context:
http://osgeo-org.1803224.n2.nabble.com/Help-with-sample-application-setup-tp5286721p5286970.html
Sent from the
Hi All
I am using the following code in the Mapguide API to return a
MgFeatureReader to my postgis data source.
featureService.SelectFeatures(featureSourceId, classId.QualifiedClassName,
queryOptions);
I am using Mapguide2011 with FDO 3.5
When this command is executed I can see from postgis
James,
Closing the reader doesn't close the connection on the server side - this is
due to the connection pooling.
If you want to ensure that it does get closed you could add the postgis
provider to the list of excluded providers. Doing so will have a negative
impact on performance though.
hi at all!
I read this thread and I'm very pleasure!
I understand a problem about zoom wheel on firefox 3.6 and chrome 5.0
If I use zoom wheel on firefox or chrome my map on ajax viewer zoom it
wrong. I want zoom in a particular feature, but the result is a overflow
zoom in a another place of
I would like to query the mapagent.fcgi directly, that is through a GET query
string like this:
/mapguide/mapagent/mapagent.fcgi?OPERATION=QUERYMAPFEATURESVERSION=1.0.0.
I have been able to do this, but note that when multiple features are
selected on the map, the response XML shows the IDs
Good find!
both chrome 5 and firefox 3.6 where released during the period between
2.1 and 2.2
can you file a ticket and attach a patch?
http://trac.osgeo.org/mapguide/
Chrome has extremely high updates rates, circa 98% of users are on the latest,
firefox users do lag behind at times so we do
Update...
I have finally had time to get back on this issue. After much playing
around, I have found that the problem is not where I thought it was. By
using the separate fields and a double property join, I have found that by
previewing the joined data in Maestro that the columns from the DB
Have you tried the 2.2 beta? I ask because the property pane has been
revamped to display properties of multiple selected features, and the
processing of selected features is done using standard MapGuide APIs.
- Jackie
--
View this message in context:
