Latest Contributions by TracySchloss

There were multiple people participating in this thread.  The sample code I posted has been working for me.  Since I wasn't the person who originally asked the question, I can't mark any particular response as the correct answer. ... View more

I've tried it both ways, autoResize:true and autoResize:false.  Neither yields a map that draws correctly.  The 2nd time I toggled the view, from About to Map, using autoResize:true, the map didn't display anything at all. I'm hoping someone on your end can eventually address this issue in the API itself, so we don't all have to do these workarounds.  At first I thought the issue was the fact that I chose to use dojo rather than something like jQuery.  But the threads in these forums related to this issue mention several different JS libraries.  As I read them, it doesn't seem to matter which of those you choose, the problem is in the ESRI JS library we're all trying to use.  Very frustrating. ... View more

I guess I don't know what "you have to handle the resize yourself" really means.  In one thread I saw that adding the autoResize:false parameters to the map definition was suggested.  So I did.    But in this example there seems to be code to handle the resize, without having to do anything more.  Isn't what these functions are for?         function mapLoadHandler(evt) {           resizeMap();           registry.byId('mapView').on('AfterTransitionIn', resizeMap);         }         function resizeMap() {           mobile.hideAddressBar();           adjustMapHeight();           map.resize();           map.reposition();         } What else is there to it?  This looks to me that it should fire the resizeMap function every time it transitions to the mapView, which contains map.resize and map.reposition.  But it doesn't display right.  Plus it often generates errors on some of the tiles in the streets base map, which I also think is weird. ... View more

I don't know if you can make use of how I did mine, but I needed to do something similar.  I had a township layer and I needed to generate a drop down list with all the choices, using a filteringselect.  I think you are better off first creating an array to hold all your selections and then using that to populate a Memory and then define that as the store to your filteringSelect. First I keep all my tool in a right hand pane inside titlePane's so the location of the filteringSelect looks like this:        <div id="tp_twpSearch" data-dojo-type="dijit/TitlePane"        data-dojo-props="title:'Find Township / Range', closable:false, open:false">        <div id="searchDiv">          <select id="pickSelect" data-dojo-type="dijit/form/FilteringSelect"  placeHolder="Select a township"          data-dojo-props="title:'Find points in selected township/range',maxHeight:200, size: 30, queryExpr:'${0}*', ignoreCase:true">             </select>        </div>    </div> Since I figured I might want to use this functionality later, I made a function that would accept a layer name and the field it needed to use.  This is executed on map load. populateDropDownList(twpRngLayer, "LABEL_1"); These are the functions that run the query and populate the dropdown.  You'll need to make sure to have all the appropriate requires defined. //Populates pick list function populateDropDownList(dropdownLayer, pickField){     pickAttr = pickField;     pickLayer = dropdownLayer;     var queryTask = new QueryTask(pickLayer.url + "/0");     var query = new Query();   query.outFields = [pickField];     query.where = "1=1";     query.returnGeometry = false;      query.outSpatialReference = spatialReference;     queryTask.on('complete', populateResultsHandler);     queryTask.on('error', errorHandler);     queryTask.execute(query); } function errorHandler(err){     console.log("Error executing queryTask: " + err.details); }     function populateResultsHandler(results){     var select = registry.byId("pickSelect");//my filteringSelect dijit     pickList.length = 0;     var numResults = results.featureSet.features.length;       for (var j = 0; j < numResults; j++) {           var pickCode = results.featureSet.features .attributes[pickAttr];         pickList.push({id: pickCode, label: pickCode});       }       pickList.sort(function(item1, item2) {         var label1 = item1.label.toLowerCase(),         label2 = item2.label.toLowerCase();              return (label1 > label2) ? 1 : (label1 < label2) ? -1 : 0;     });    var dataStore = new Memory({data:pickList, idProperty:"id"});     select.set ("searchAttr", "id");     select.set("labelAttr", "id");     select.set("store", dataStore); } ... View more

Yes, I am selecting points, but I have an if statement that sets the map to center and zoom if there is only one feature returned.  I thought maybe my queryTask wasn't done executing, so I changed it to have a queryTask.on('complete') trying to make sure the executing is done before it finishes. The queryTask is also populating a dGrid, which looks just fine, so I know the queryTask is executing and returning what I would expect.  The problem looks to be limited to extent of the results.  The idea of a union isn't going to work with points.  I wonder if my problem is that the map is in a floating pane, and that there is some sort of delay.  Even after that pane is open, it still doesn't set the extent correctly.  From what I can see, it is almost always centered on the first point returned from the query. I've seen a few other threads with people having the same problem, I have to wonder if there is an issue with graphicsExtent itself.  http://jsfiddle.net/schlot/9zv22/1/ ... View more

I'm mistaken, it doesn't work properly in Firefox either.  It seems to be moving to the general vicinity of my featureSet, but it isn't set to the extent.  Instead, if I zoom out several times manually, I can see the points.  I'm wondering of the features returned as the results of a queryTask are the same as the results of a selectFeatures on a featureLayer.  Both say they are a featureSet. ... View more

I'm having problems with this too, especially in IE 8, which is still our version for IE.  In the code var selExtent = graphicsUtils.graphicsExtent(featureSet.features); the variable selExtent is not found, it returns null.  There are features in my featureSet, which is a result of a queryTask.   This works just fine in Firefox, but not in either Chrome or IE. ... View more

The user says it was working yesterday, which makes me think it is internal to us.  But my other JS sites are all working.  Of course this is just about the oldest one, so there could still be an issue with the JS library. ... View more

I can believe that, they are constantly pushing patches and updates with no notice.  That isn't going to be satisfactory answer for the user, though.  It just so happens that I've been working on updating it, since it's not styled to be mobile-friendly, but I'm not ready to push it out today! ... View more