Latest Contributions by AdamDrackley

Thanks Barnaby, that is super good to hear.  I am working on a new version with some slight rearchitecture under the hood, if you want to give it a test drive. GitHub - cmndrbensisko/LocalLayer at LocalLayer2.3  To Kevin's point, I'd imagine since the LocalLayer widget removes some of the 'configuration in the cloud' dependency from your app, it would skip the step that pulls down a big json object from ArcGIS Online to initiate the map.  On the other hand, it would then need to trundle through an equally large local configuration file to initialize the LocalLayer widget. Unfortunately, sublayers need to have their popups enabled individually via the Widget settings.  Fortunately, it would be possible to make a script to generate the appropriate JSON configuration 'snippet' by trundling through your service and creating popups containing all fields within each sublayer; This might be a useful tool for other folks who use enormous services. ... View more

Hey Robert, hope things are well.  Thanks for your hard work on this great widget.  I wanted to let you know of a bug I've run into; When the widget is configured to Identify a layer within a MapService whose Unique subLayer IDs don't correspond with their position within the Layer List, problems appear to arise.  For example, if I had a MapService with a collection of sublayers like the following: Layers: SubLayer0 (4) SubLayer1 (1) SubLayer2 (2) Unfortunately, I don't have a public service you can test to prove this on your end; You'd need to fiddle with an existing service to ensure that those Unique Layer Ids are preserved when the layers get reordered within the MXD.  I've tracked the bug to the removeGroupLayers section of Widget.js, though the problem is likely stemming from some deeper interactions.  I find that if I change the function as follows, which will return all Sublayers within the service that aren't grouplayers, some code further down the line seems to result in the correct operation of the widget, but there's probably a 'better' fix you could apply in a future release of the widget. removeGroupLayers: function(subLayers, layer) {    var newSubLayers = [];    //for (var i = 0; i < subLayers.length; i++) {    for (var j = 0; j < layer.layerInfos.length; j++){       //if (layer.layerInfos .id == subLayers && layer.layerInfos .subLayerIds === null){       if (layer.layerInfos .subLayerIds === null){          //newSubLayers.push(subLayers);          newSubLayers.push(layer.layerInfos .id)       }    }    //}    return newSubLayers; }, As you can see, the original code assumes that the position of the element within the subLayers array will be the same as the ID value for that layer, which will not be the case in a service with non-sequential IDs.  Hopefully this is enough info to go on; Let me know if there's any additional information you need! ... View more

I've officially released the 2.2 version of the LocalLayer widget.  I'm still fighting a (hopefully) very intermittent bug related to layer toggling, but otherwise things seem to be cooperating.  I will update the original post with a summary of the enhancements for this widget; Thanks again to everyone who helped test! For the generous folks who offered to purchase me a beverage, I unfortunately don't make it around to conferences often, but I've added a tip jar to the repository. ... View more

Hey Baba, I was able to get those environment.data.gov.uk WMS services to display fine via a proxy in my IIS-hosted application.  Is your app available publicly?  If so, I can try to remotely debug what might be happening on your end. ... View more

Just a note that I was able to get labels to display on a Feature Layer made from your service via the LocalLayer widget, Anthony.  Note that I did have to add that "showLabels":true value in the config.json file of the completed app as so: "mapOptions": { "showLabels":true, "extent": { "xmin": -8923741.74197918, "ymin": 4324631.992240296, "xmax": -8923478.98969453, "ymax": 4324889.370046397, "spatialReference": { "wkid": 102100 } } Note that showLabels belongs within the mapOptions segment.  Also note that hitting 'Save' on the app in the builder appears to blow away the value if you haven't set it in your stemapp config.json file, so always make sure to re-add this showLabels value whenever you hit 'Save'. ... View more

Hey Baba, can you paste the "httpProxy" portion of your configuration file?  Also, what is the IIS path for your proxy.ashx file? ... View more

Hey Baba; 2.2 isn't officially 'released' yet.  Once you guys give it a general checkmark that it doesn't destroy your workflows, I'll prepare a final release.  Until then, I'm keeping the candidates on a separate 'branch' of the repo. GitHub - cmndrbensisko/LocalLayer at LocalLayer2.2  ... View more

I'm going to guess (currently afk) that this is related to the proxy required by the WMS. When you deploy to IIS, check the config.json file for your application. The last few lines should refer to a proxy file (proxy.js?) that the WAB expects to be present an working in the deployed application directory. In my deployments, I believe I change this to a proxy.ashx asp file handled by IIS; Unsure if proxy.js cooperates well with IIS, but can investigate. ... View more

Hey Barnaby, I think I've got a potential fix for you to test in the candidate version.  I've re-introduced the code that I had previously commented out, but to combat the issue of the final-layer-not-toggling, I now add and remove a dummy layer  as a final step to ensure that all 'real' layers get properly initialized by the WAB.  Let me know if this seems to solve the issue on your end, or introduce anything new.  I think the very active testing you guys are putting the widget through is going to make this a great release. ... View more

This is great Barnaby, I have a feeling that the hanging issue you've found is related to the previous  issue you mentioned which was no longer being fixed by those _bindEvent hitches in 2.2. I removed that code because it was leading to the last-layer-toggling issue we found, and it doesn't seem to fulfill its intended purpose anymore of preventing redundant event binding when new layers are added. If you can keep your bugged app up, I can use it to try to pin down a proper fix for this issue. ... View more

Well,first we should pin down whether or not even adding that code does anything to help the situation you're running into.  Are you finding that adding the (old) code does anything to improve your hangs? ... View more

Groan, reintroducing that code also seems to mess with the operational layers list visibilities.  You may need to go back to the following hackaround we did back in January for your particular setup; On line 624 of the NOAA/jimu.js/LayerInfos/LayerInfoForMapServices.js file, you should see a function called _bindEvent.  Change it to match the code below (added portions bolded);     _bindEvent: function() {       this.inherited(arguments);       if(this.layerObject && !this.layerObject.empty && !this.layerObject.connected) {         this.layerObject.on('visible-layers-change',                             lang.hitch(this, this._onVisibleLayersChanged));         this.layerObject.connected = true;       }     }, ... View more

Hey Barnaby, within the Widget.js file for the LocalLayer widget, there's a chunk of code I had commented out because, sadly, I kind of forgot what it did.  I think it was related to fixing your loading problem, though, if you want to try uncommenting it within your local instance to test.  (Remove the /* and */ on either side of the code block) /* aspect.before(layerInfo.__proto__,"_bindEvent",function(){ if (this.layerObject){ if (!this.layerObject.empty){ this.layerObject.modified = true; this.layerObject.empty = true; } } }) aspect.after(layerInfo.__proto__,"_bindEvent",function(){ if (this.layerObject){ if (this.layerObject.modified){ this.layerObject.empty = false; } } },true) */ ... View more

Good observation, Barnaby, thanks for finding that.  I'm glad the tweak worked as well! I've put up what I hope to be the 'final' candidate for 2.2, barring any showstoppers.  The main change is that I've reintroduced the requirement to tweak that one line from the AttributeTable setting file to discover all layers.  I found that calling internal WAB functions to keep the AttributeTable updated was more trouble than it was worth. The manual change is 'safer' in the long run, I think. I also verified that the WMS layer properly handles transparency, among a few other settings. ... View more