Latest Contributions by ReneRubalcava

Odd, I would think the context for this would the toolbar, but you can bind the context of your widget to the addToMap function using dojo/_base/lang. Instead of this.toolbar.on("draw-end", this.addToMap); Try this.toolbar.on("draw-end", lang.hitch(this, "addToMap")); That should make sure your addToMap method has a context bound the widget. ... View more

It's the same as I would do saving to a regular FeatureService. I have a module that is used to perform all my saves/syncs I put together a more comprehensive example of how I use perform saves/updates. // using the historyutil.js module I posted earlier var Service = declare([], { constructor: function(options) {   this.options = options;   this.map = this.options.map;   // the options will have a URL to the   // non-spatial table in my FeatureService   // for recording the history of my edits   this.editHistory = new HisotryUtil(this.options);   // this is the actual layer with spatial features that   // I will edit.   this.editLayer = this.map.getLayer('defectsLayer'); }, save: function(name, adds, updates) {   var deferred = new Deferred();   var self = this;   // first edit my spatial layer   // NOTE - Deletes not allowed in app, but you could track that if   // needed.   this.editLayer.applyEdits(adds, updates, null, function (results) {     // when spatial table successfully edited, send same     // edits to history table using the HistoryUtil     // module in previous post.     self.editHistory.save(adds, filterUpdate(updates));     self.editLayer.refresh(); // quick refresh     // I don't to see if     // history update finished because I don't care.     // History is a backend thing, not app related.     // In production I would check if this failed and     // log it somewhere else.     // Now I can resolve my results.     deferred.resolve(results);    }, function (error) {     deferred.reject(error);    });   return deferred.promise; }, }); // This function finds out if two field // values are identical function statsMatch(obj, field1, field2) { return obj[field1] === obj[field2]; } // If I'm doing an update of data, I just track status changes. // So I filter out any features where the status did NOT change. function filterUpdate(items) { return arrayUtil.filter(items, function(item) {   // helper function to see if the status changed   return !statsMatch(item.attributes, 'PreviousStatus', 'DefectStatus'); }); } return Service; ... View more

You mway want to make sure the results are in the proper spatial reference. Make sure you have this in your code some where before executing the QueryTask. query.outSpatialReference = map.spatialReference; https://developers.arcgis.com/en/javascript/jsapi/query-amd.html#outspatialreference This has bitten me on more than one occasion. ... View more

In AMD style codes, I don't understand what happens when a function is in inside the require([...], function() {}); for example, the following codes: require([...], function() { .....  function ABC () {a = c + b; } ..... }); The function ABC is very confusing to me.  When the program runs, when will function ABC be executed?  To understand this, should I go study more dojo language? Thanks a lot! The ABC function lives in the scope of the require() function, but isn't executed unless you call it in the require function. It is only accessible inside that particular require function. This isn't really a Dojo specific issue. Modules simply scope functionality. But when you define() a module, unless you return something, it doesn't provide anything. This is why you may come across errors like variable equals 3 or something odd, because maybe you forgot to place a return in the module. To help illustrate, let's look at a define() module. // ABCModule define([], function() {   function ABC (b, c) {     var a = c + b;     return a;   }    return ABC; // defined modules should return something, object or function. });  // Main JS file require(['./ABCModule'], function(ABC) {   ABC(1, 2); // returns 3; }); If you didn't actually return ABC in the defined module, you would never be able to use it, as it's not exposed to the outside world. AMD modules essentially use the revealing module pattern to share their innards (or the important parts anyway) with the everyone else. http://addyosmani.com/resources/essentialjsdesignpatterns/book/#revealingmodulepatternjavascript http://requirejs.org/docs/whyamd.html#amd Here are a couple of links that discuss scope. http://dailyjs.com/2012/07/23/js101-scope/ https://developer.mozilla.org/en-US/docs/Web/JavaScript/Reference/Functions_and_function_scope http://javascriptplayground.com/blog/2012/04/javascript-variable-scope-this/ Also, you typically only have a single require() per application, an entry point to start the application. This SO answer covers if pretty nicely. http://stackoverflow.com/questions/11559270/what-is-the-main-difference-between-require-and-define-function-in-dojo-and Hope that helps a bit. ... View more