Hi Dennis, If you can find time, I would suggest figuring out whether it is the raster or vector layer that is causing problems. If it is the vector layer, then it's possible that Haris will be able to replicate the problem (given appropriate source data). If it's raster, well I think we're currently a bit stuck because Frank doesn't have enough experience with MapGuide internals to troubleshoot, and apparently nobody with core MapGuide development experience has resources available to sit in a room with him to figure out what is causing the problems.
In either case, if the problem is specific to your data and is not reported with enough detail that it can be fixed, it is unlikely to be addressed for 2.1, which is due out in alpha real soon now. Jason -----Original Message----- From: Jonio, Dennis (Aviation) Subject: RE: [mapguide-users] Could it be MGOS2.0.2 - maybe needs some tuning? Yes, that is what I am using. I guess I need to take the time and do one-thing-at-once or bail out completely for now ... I guess I had assumed too much about the "vitality" of this release. _______________________________________________ mapguide-users mailing list [email protected] http://lists.osgeo.org/mailman/listinfo/mapguide-users
