[mapguide-users] Re: Can I use a local language to display in the properties box?

2010-11-08 Thread Jackie Ng
To localize the flexible layout, you have to edit the raw XML document. Locate all Widget instances in the document, and look for the Label and ToolTip elements. Replace this text in these elements with your translated text and repeat for all the widgets. There may be a way to do this in MapGuide

[mapguide-users] Re: Calculating map meters per unit without MgCoordinateSystem

2010-11-08 Thread Jackie Ng
Well that makes the Rendering Service API mostly useless for client-side created runtime maps :( The workaround is of course knowing the actual meters-per-unit value beforehand when creating the runtime map client-side, but workaround is a far too generous a word to describe that! - Jackie --

Re: [mapguide-users] Re: Calculating map meters per unit without MgCoordinateSystem

2010-11-08 Thread Zac Spitzer
I had this problem with using MG with openlayers too. Solution would be a new http method which returns a json config document which covers everything required, MPU, extent scales etc for a given map def z On Tue, Nov 9, 2010 at 12:18 AM, Jackie Ng jumpinjac...@gmail.com wrote: Well that

[mapguide-users] SESSION() in layer filter

2010-11-08 Thread doggybs
Hi There I am trying to create a layer which filters on the SESSION() function to compare the mapguide session id to something else. If I use the syntax SESSION() = SESSION() in the layer filter, you would expect it the show all objects, but instead nothing is shown. Using SESSION() for the

Re: [mapguide-users] GoogleMap on MGOS

2010-11-08 Thread Jason Birch
I don't remember the details, but there's an outstanding defect in Fusion for the commercial layers. On 2010-11-08, ar_gaeta ar_ga...@yahoo.it wrote: Hi, I have a problem loading a GoogleMap layer on my flexible layout on MGOS v2.2. In a lot of forum I've got a lot of solution but they

[mapguide-users] Re: SESSION() in layer filter

2010-11-08 Thread Jackie Ng
I think you might have exposed a limitation of FDO filters. These filters are ultimately translated into something the underlying datastore can understand (eg. A SQL where clause). As such, I think at least one side of the filter has to contain an identifier of some sort. How about this