Latest Contributions by DavidColey

Hi Robert - In finally beginning my task to migrate my large flex-based app, I was just thinking along the lines of a data extract widget as well. On the otherhand, if there is a geoprocessing task widget that I haven't come across yet, that obviously would work as well.... Thanks-- David ... View more

Thanks Thejus, yes helpful for sure.  Yes, we've been sort of trial and error on this for some time. Anytime we set an info or popup window as part of the map or search constructer it completely hoses the attribute inspector and it's functionality.  You are likely correct in we will have create a specific AI.   ... View more

Hi Thejus - @michael Stranovsky and I work together - hence my reply to you... yes I want to get our project up in a fiddle and will let you know when - thanks.  One thing we did try and thus far has produced mixed results it adding a click event to our edit layer that calls a tolerance function to set up an extent, like what I did here function pointToExtent (mapMain, point, toleranceInPixel) {         var pixelWidth = mapMain.extent.getWidth() / mapMain.width;       var toleranceInMapCoords = toleranceInPixel * pixelWidth;           return new Extent(point.x - toleranceInMapCoords,                                 point.y - toleranceInMapCoords,                                 point.x + toleranceInMapCoords,                                 point.y + toleranceInMapCoords,                                 mapMain.spatialReference);             }    lyrAddresses.on('click', function (event) { //mapMain    console.log("im here");          var query = new Query();            query.geometry = pointToExtent(mapMain, event.mapPoint, 10);            var deferred = lyrAddresses.selectFeatures(query, //featurelayer                FeatureLayer.SELECTION_NEW);               //mapMain.infoWindow.setFeatures([deferred]);               //mapMain.infoWindow.show(event.mapPoint);             }); The thinking being that an extent has to be accessed in order for the popup to know that there is more than one feature -- but  I don't know.  As soon as I interact with the search dijit and try to go back to the edit tools no paging occurs- David ... View more

Sure thing. We're doing something similar so if/when we get something working I'll post back- ... View more

Way to go thejsu, that's it - thanks! David ... View more

Michael, Thejus - I am experiencing the same problem.  If you go to the jsapi sample at: Editor widget with simple toolbar | ArcGIS API for JavaScript and perform a selection on more than one feature using the edit toolbar selection tool>open attribute inspector, only the first-selected features' attributes are populated in the attribute inspector with no paging controls. Does the attribute inspector need to be instancicated seperatly from the editor widget so that paging controls will display?  If so, do we have to calll in attribute inspector events to move to a next feature? Any help is appreciated- David ... View more

Hi William - did you ever get this figured out? David ... View more

Actually this might not be so much a bug as an oversight(?) in that a where expression can't operate against a parent graphic class? ... View more

Right, see I think it's a bug in that the API reference for the labeling info property on a feature layer reads - 'Label definition for this layer, specified as an array of label classes. Use this property to specify any changes to the structure of the label'. For my particular need what I am doing is specifying one label class based on an AddressNumber and a second class based on an AddressStatus and then positioning the first at upper right and the second at lower right . . . Thanks for looking into this all- David ... View more

Robert,  I'm not certain I have made this situation clear. In your sample above, you're basically jsut adding a lable layer after a setDefinitionExpression has been applied to the feature layer that is passed into the label layer, then adding that label layer to the map which is totally doable.  What I am trying to do is set up two label classes with where clauses based on the REST API sample thusly: var acClass =  new LabelClass({   labelPlacement: "esriServerPointLabelPlacementAboveRight",   labelExpression: "[AddNum]",   symbol: {     type: "esriTS",       color: [38,115,0,255], //255,0,0,255],       font: {       family: "Arial",       size: 7,       style: "italic",       weight: "bold",       decoration: "none",     },     },     minScale: 2401,     maxScale: 0,     //where: "AddressStatus LIKE 'A%'" }); var iaClass =  new LabelClass({   labelPlacement: "esriServerPointLabelPlacementAboveRight",   labelExpression: "[AddNum]",   symbol: {     type: "esriTS",       color: [255,0,0,255], //[38,115,0,255],       font: {       family: "Arial",       size: 7,       style: "italic",       weight: "bold",       decoration: "none",     },     },     minScale: 2401,     maxScale: 0,     //where: "AddressStatus LIKE 'I%'" }); Then add the label classes to an array: var labelArray  = [acClass,iaClass]; and lastly set the labeling info on the feature layer per it's labeling info property accessed via setLabelingInfo method (per the jsapi): lyrAddresses.setLabelingInfo(labelArray); All of the value changes per label class optoins such as a placement change or a font style or color change are immediatly visible EXCEPT the where clauses.  Whenever I un-comment them, the labels will no longer render as graphics David ... View more

Thanks Robert.  I wasn't actually specifiying a labelClass reference as I wasn't sure I needed to  - - that's likely what I am missing. David ... View more

Phu- sorry for the delayed response.  Anecdotally, yes I reccomend disabling hyperthreading on Windows Servers hosting SQL Server 2005 or 2008R2.  We found that performance was impacted when hyperthreading was enabled.  However, without performing tests and research, I can only speculate as to why.  Perhaps hyperthreading can cause an I/O or disk contention issue?  David ... View more

great, glad to help ... View more

Check all your directory permissions, SDE privileges, model parameters and pathways, tool input and output parameters.  GPs that run well on the desktop with physical output locations do well, but when publishing as a GP service locations must be reset to in_memory so the input and jobs directories can access them.  Lastly, back your model up to  the first point of failure and solve from there ... View more