Latest Contributions by JonathanUihlein

Indeed! Great find Corey. This is a major change that will affect many users who decide to update to 3.11. The updated SDK (and What's New? page) will highlight all major changes to the API. It's coming soon! ... View more

Using position relative is fine but you didn't position its container (mapContainer) so your position:relative doesn't mean anything. You need to add rules to parent elements if you want to use position:relative. Also, in the console: TypeError: dom.byId(...) is null dom.byId("map").style.height = availHeight + "px"; There is no dom element with the id of map. You use "mapDiv". There's a map class though. On second look, the following snippet doesn't do anything at all because you are assigning this to a dom node with an ID of map, not a class of map. #map {   position:relative;   width: 100%;   height: 100%; } ... View more

My advice is to create a smaller sample of the drag and drop, without all of your extra application code. When you get it to work on a smaller scale, and understand *how* it works, it should be easier to implement in your main application. That TypeError is very clear in describing an eventing issue. Copy and pasting large chunks of code and expecting it to work is not recommended or feasible in an already-large application. ... View more

What does your CSS look like? What javascript-specific fixes have you tried so far? I've seen a few threads about this over at the DOJO community site. ... View more

It's been a while since I've used jQuery but according to the documentation, you would want to hook up your callback functions to the select event emitted by the autocomplete widget. It looks like the event is named 'autocompleteselect' so that should be all you need. Autocomplete Widget | jQuery UI API Documentation ... View more

There are many ways to accomplish what you are trying to do, several of them highlighted in our documentation with complete samples and tutorials. If you haven't read through our documentation, I highly suggest doing so. If you don't want to use the infoTemplate defined in your FeatureService, you can create an infoTemplate client-side in your application. The infoTemplate class also has a setContent() method. Sample: Format info window content | ArcGIS API for JavaScript SDK Reference: infotemplate-amd | API Reference | ArcGIS API for JavaScript ... View more

Hi Alex, It's hard to tell what is causing your issue without seeing the code in action. Have you seen this sample about query tasks?: Query data without a map | ArcGIS API for JavaScript If that doesn't help, could you generate a working (public) jsfiddle that showcases the first problem only (remove ALL other irrelevant code, please). Thanks! ... View more

Ryan, the version you are using came out in March 2013, and the first stable release of IE10 came a month before that. You may want to try upgrading to a newer version of the API. ... View more

I need to see more of your code, and preferably in action. Can you post a complete sample using jsfiddle? Thanks! ... View more

No worries! I'll take another look later today when I free up a bit and let you know what I find. In my opinion, I think the undoManager needs a splice function that doesn't reset the stack. This may be something that we end up implementing in the future ... View more

Hey Tim! I had a few minutes to check out the logic in undoManager and you are right that the add() function calls this.clearRedo() after. However, this is expected and not the cause of your issue. You changed up the order of operations I suggested in my previous post. remove() add() undo() Remove uses splice for the historyStack. add() will add your graphic back onto the front of the stack, and undo() should step back to the appropriate position. You are using add, undo, remove and add remove undo, in those orders respectively. Logically, this will break the code, as you are seeing. I also ran your application against a newer internal version of the API, which uses a newer DOJO, and found an issue with the following: registry.forEach(function (d) {     // d is a reference to a dijit     // could be a layout container or a button     if (d.declaredClass === "dijit.form.Button") {         buttonclick = d.on("click", activateTool);     } }); You might want to change the above to this to avoid having to do it later. The reason for this is Registry is an object, not an array, and at certain points the forEach function might not be scoped. array.forEach(registry.toArray(), function (d) {     // d is a reference to a dijit     // could be a layout container or a button     if (d.declaredClass === "dijit.form.Button") {         buttonclick = d.on("click", activateTool);     } }); ... View more