ahhh ajax. the secret deadly ninja of web apps. On Thu, Feb 21, 2008 at 7:34 PM, Paul Spencer <[EMAIL PROTECTED]> wrote:
> The exception is corrupting the json formatted response so when > Query.php returns there is a (likely suppressed) javascript error that > prevents Fusion from processing the selection and hence other widgets > from responding to it to load the selection. > > Mike, we should be able to reproduce this with some of Jason's data. > > Cheers > > Paul > > On 21-Feb-08, at 3:14 PM, Jonathan Manafi wrote: > > > This is the response from a query: > > > > Object not foundERROR: The specified object was not found. > > The specified object was not found. > > Exception occurred in method GetItem at line 117 in file d: > > \buildforgeprojects\mapguide_open_source_v2 > > .0\build_22.4\mgdev\common\foundation\Data/NamedCollection.cpp > > - GetItem line 117 file d:\buildforgeprojects > > \mapguide_open_source_v2.0\build_22.4\mgdev\common\foundation > > \Data/NamedCollection.cpp > > general exceptiongeneral exception{"hasSelection":true,"extents": > > {"minx":-1841749.109647,"miny":10697190 > > .314625,"maxx":-1611134.1984211,"maxy":10745845.651758},"layers": > > ["obstructions","platforms","wellbores" > > ,"pipelines","blocks"],"obstructions":{"featureCount":1},"platforms": > > {"featureCount":3},"wellbores": > > {"featureCount":15},"pipelines":{"featureCount":6},"blocks": > > {"featureCount":4}} > > > > > > Mike Adair wrote: > >> What response are you getting from Query.php for your maps? > >> > >> Mike > >> > >> Jonathan Manafi wrote: > >>> We realized about the Selection widgets, and we went ahead and > >>> included those in the ApplicationDefinition.xml files that we > >>> used. We also noted that the selection does indeed work with the > >>> Sheboygan maps, and as soon as you select parcels, the map > >>> refreshes to indicate your selection, as well as the SelectionInfo > >>> widget shows your selected objects. However, we used the included > >>> Aqua ApplicationDefinition.xml template and only changed > >>> the .MapDefinition files to reflect our maps instead of Sheboygan > >>> and added our custom scripts/urls as widgets to test, and we are > >>> having the selection issues. I even removed everything external to > >>> the initial Aqua template except for one of our maps to load, and > >>> the same thing occurs. > >>> > >>> Also of note: > >>> I used the FireBug extension to see the GET and POST commands, and > >>> when running the Sheboygan sample, the selection command issues a > >>> POST of .../fusion/MapGuide/php/Query.php followed by POST .../ > >>> fusion/MapGuide/php/Selection.php, whereas our maps only issue > >>> POST of .../fusion/MapGuide/php/Query.php. I don't know if that > >>> has anything to do with the SelectionInfo showing selected objects > >>> for Sheboygan and not for us, or if all of these issues are just > >>> interrelated. > >>> > >>> Jonathan > >>> > >>> Mike Adair wrote: > >>>> Note that if you are testing with the fusion/samples/mapguide/ > >>>> standard example, the SelectionPanel and SelectionInfo widgets > >>>> aren't enabled in the ApplicationDefinition.xml file as shipped. > >>>> You have to uncomment those widgets in the file. We should > >>>> probably change that so those widgets are included by default. > >>>> In RC4 with the Sheboygan map, the selection should be appearing > >>>> highlighted as soon as it is selected. > >>>> > >>>> Mike > >>>> > >>>> > >>>> > >>>> Jason Birch wrote: > >>>>> Oh, looking at your contribution to that thread, it looks like > >>>>> that problem is Fusion-specific, which is different than ary's > >>>>> problem (which is PostGIS-specific). > >>>>> I'm seeing this Fusion selection problem myself on Windows2k3, > >>>>> IIS installation. > >>>>> Jason > >>>>> > >>>>> ________________________________ > >>>>> > >>>>> From: [EMAIL PROTECTED] on behalf of Jason > >>>>> Birch > >>>>> Sent: Thu 2008-02-21 8:32 AM > >>>>> To: MapGuide Users Mail List > >>>>> Subject: RE: [mapguide-users] MG 2.0 RC4 selection ALMOST working > >>>>> > >>>>> > >>>>> Is that just for PostGIS, or is it happening for other feature > >>>>> providers too? > >>>>> Currently Tom has moved that RC4 be tagged as release, so if > >>>>> this is something that is not specific to the PostGIS provider > >>>>> and it is critical, you should make sure to create a ticket in > >>>>> Trac with enough information (data, MGP package, operating > >>>>> system, web server, which viewer you're using) to replicate the > >>>>> problem. > >>>>> If it is PostGIS-specific, then it likely won't be fixed in > >>>>> MapGuide. Bruno Scott is doing a bunch of work on the PostGIS > >>>>> provider currently, so hopfully it will be fixed through his > >>>>> efforts. > >>>>> Jason > >>>>> > >>>>> ________________________________ > >>>>> > >>>>> From: J Manafi > >>>>> Subject: [mapguide-users] MG 2.0 RC4 selection ALMOST working > >>>>> > >>>>> > >>>>> I was previously having issues with selection ( > http://www.nabble.com/Postgis-Selection-Problem-%28additional%29-tt15466067s16610.html > >>>>> ) where it looked like my objects were selected, but nothing > >>>>> actually was, and RC4 has made great strides to remedy this. > >>>>> However, my current situation is this: > >>>>> > >>>>> I can use the selection tool to make selections on the map. But, > >>>>> they don't show up unless I click the 'Refresh Map' button. And > >>>>> even then, the statusbar still shows No features selected. But > >>>>> when I run our script, the output is correct and formatted > >>>>> accordingly. Yet, If I make a selection programmatically like > >>>>> stated in the linked post, the selection is highlighted, and the > >>>>> statusbar reads {0} features selected on {1} layers, yet shows > >>>>> that two layers are selected in the selection panel, wells and > >>>>> blocks. And, no matter which block I select--even if the block > >>>>> has nothing inside--the selection panel always shows the same > >>>>> two wells selected. Also, if I make a selection with the tool, I > >>>>> cannot use the 'Clear Selection' tool, but it is available when > >>>>> objects are selected programmatically. > >>>>> > >>>>> I don't know what is causing this behavior, but these are my > >>>>> observations so far. If I come across anything new, I will > >>>>> update here. At least the selections are working enough to use > >>>>> and test our scripts, and for that, I am glad. > >>>>> > >>>>> > ------------------------------------------------------------------------ > >>>>> > >>>>> _______________________________________________ > >>>>> mapguide-users mailing list > >>>>> mapguide-users@lists.osgeo.org > >>>>> http://lists.osgeo.org/mailman/listinfo/mapguide-users > >>>>> > >>>> _______________________________________________ > >>>> mapguide-users mailing list > >>>> mapguide-users@lists.osgeo.org > >>>> http://lists.osgeo.org/mailman/listinfo/mapguide-users > >>> _______________________________________________ > >>> mapguide-users mailing list > >>> mapguide-users@lists.osgeo.org > >>> http://lists.osgeo.org/mailman/listinfo/mapguide-users > >>> > > _______________________________________________ > > mapguide-users mailing list > > mapguide-users@lists.osgeo.org > > http://lists.osgeo.org/mailman/listinfo/mapguide-users > > -- > Paul Spencer > CTO, DM Solutions Group Inc > http://www.dmsolutions.ca/ > > > > > _______________________________________________ > mapguide-users mailing list > mapguide-users@lists.osgeo.org > http://lists.osgeo.org/mailman/listinfo/mapguide-users >
_______________________________________________ mapguide-users mailing list mapguide-users@lists.osgeo.org http://lists.osgeo.org/mailman/listinfo/mapguide-users