Latest Contributions by thejuskambi

Try to move the parser.parse outside the ready function. As per the doc dojo/ready — The Dojo Toolkit - Reference Guide  it says, its has been replaced by AMD API. so you dont exactly need to use ready  unless there is a special requirement. I also see you are loading a huge list of objects in the require. try to avoid it, load only the ones you are going to use are used in Html. I understand you are migrating from legacy to AMD style. try to be more modulaized and divide the code into smaller modules and widgets. Hope it was helpful. ... View more

It shouldn't matter which projection system you use. The 1.5 and 1.1 is a factor like 1.5 times the existing width. its a matter for selecting the correct factor for your need. ... View more

What is this ready function?. Can you share the code. It should be as Tim shown below require ... View more

I believe it is the first thing you need to call before all the other dijits and widgets initialization. There are many ways to setup the dojo config you can use the legacy way like this <script>   dojoConfig= {   parseOnLoad: false,    async: true   }; </script> of use script tag <script src="http://js.arcgis.com/3.13/ " data-dojo-config="parseOnLoad: false,  async: 1"> </script> Read more here: Configuring Dojo with dojoConfig - Dojo Toolkit Tutorial ... View more

I check the implementation for 3.13 api and there is no reference of start or num. My guess is good as yours, Its still being implemented. Wonder why they have it updated in the document. ... View more

The Query object has property num which takes in values for the number of records to be returned. It should be used alson with start. check the api reference for Query object. ... View more

You can not query on multiple layers at the same time. What you could do is query on each layers and combine the results together using the dojo/promise/all as discussed in this thread How to nest dojo async calls and wait until all are complete Only instead of layer.queryFeatures your need to use QueryTask for each of the layers. ... View more

Glad, I could help. you could help me by updating the status of this discussion. ... View more

Your Basemap are they a single layer or multiplelayers with isReference=true? ... View more

Did you make the change on line 31 as well? ... View more

Try this... define(["dojo/_base/declare", "dojo/promise/all", "dojo/_base/lang", "dojo/_base/array", "esri/tasks/query"], function (declare, all, lang, array, Query) {     var sdcAddressSelector = declare(null, {         constructor: function () {             this.addresses = [];         },         addAddressesToList: function (response) {             response = array.filter(response, function (r) { //filter out any failed tasks                  return r.length > 0;             });             array.forEach(response, function (r) {                 this.addresses.push(r);             });         },         callAPI: function () {             //api calls here          },         executeSelect: function (selectedParcels) {             var _this = this;             var selectList = array.map(selectedParcels, function (parcel, index) {                 qry = new Query();                 qry.geometry = parcel.feature.geometry;                 //async loop over the address layers to get the  addresses that intersect the current parcel                  var addressList = array.map(esriMap.addressServices, function (layer, index) {                     layer.queryFeatures(qry, lang.hitch(_this, _this.addAddressesToList));                 });                 return addressList.promise;             });             return all(selectList).then(lang.hitch(this, this.callAPI)));     },     }); return sdcAddressSelector; }); ... View more

Are you sure. It works for me when I remove the margin 1% from the html page. ... View more