Latest Contributions by AdamGebhart

Ian Peebles​ This is what I've done for lines 94-96 in my apps: 94.  //onBeforeUnload: function() { 95.  //  this.appStateManager.saveWabAppState(this.map, this.layerInfosObj); 96.  //}, I don't recall what problem I was having earlier (see my post 10:29 a.m. on 1/6/16) but everything works fine now. ... View more

Glenn, See this discussion for how to disable the setting: How to turn off new "auto saved map extent and layer visibility" in Nov 2015 update? ... View more

Thank you.  That worked. ... View more

Robert Scheitlin, GISP​, Chris Mathers​ Will we want to comment out the lines that Kim Bülow referenced below (see December 14th)?  I tried Kim's lines in jimu.js\MapManager.js with a hosted/deployed app but the previous state or extent was preserved after refreshing, reopening and clearing the cache.  Or do I have the wrong lines and/or wrong file? ... View more

Robert: Thanks for the suggestions.   I restarted ArcGIS Server and it didn't have any (noticeable) positive impact on the error as some attempts still don't return any results and essentially lock up the widget. I have had "Only These" checked throughout the entire configuration.  One thing I have noticed with the layers from my default basemap is they tend to work with the widget when I'm zoomed into the community level or better.  If I try them at the county or township extent it locks up, even with the one layer that's visible at all extents. It looks like this will require a tech support call next week. Thanks for your help. ... View more

Checking the Logs in Server Manager I see the following errors: Error performing identify Wait time of the request to the service 'service name here' has expired. Instance of service 'service name here' failed to process a request. Error performing identify Error handling service request: java.lang.OutOfMemoryError: Java heap space Processing request took longer than the usage timeout for service 'service name here'.  Server request timed out.  Check that the usage timeout is appropriately configure for such requests. The above error messages refer to the same service.  If it means anything this specific service is my default basemap.  There are two layers in this basemap that I want configured in the Identify widget.  Sometimes the identify action works on them, sometimes it doesn't.  I don't see any error messages for the unsuccessful attempts to identify within a different service though.  Additionally, I'm now experiencing instances where the widget works in a specific layer, but then when I pan/move and attempt to identify another feature within that same layer the blue status bar runs until I refresh the browser. I am wondering if the basemap service mentioned above is somehow holding up the progress of the Identify widget, but I can't say that for sure or know how to resolve the issue. ... View more

Robert: Below is the console error I saw when checking at least three different layers (point, line and poly).  Is this what you need?  Can you read it clearly?  The error also refers to init.js:182:169 and widget.js:704:11. FYI, the Identify widget did work when checking a few other layers, but still gets hung up on others. ... View more

Robert Scheitlin, GISP​ I'm encountering another problem that I believe I experienced with the Identify widget in WAB 1.2.  I have many instances of a) the Identify widget not identifying a feature, and b) not responding with the "No Results Found" message.  The blue status/progress bar simply runs without stopping.  I have tried to identify other features or identify from a different layer, but neither method will clear the previous request.  In order for me to clear the request I have to refresh my browser. I test each Identify layer after I add it to my configuration.  While I haven't been 100% successful in getting each layer to work upon configuration (problems = those listed above) I have had success in setting up probably 18 of the 20 layers in my widget.  When I launch the application (from WAB, not hosted) I then have the problems I mentioned above.  And more often than not, it's the line and point layers that have the problems, regardless of what kind of graphic I use to identify the feature.  The problem has occurred with polygon features as well. I have adjusted the identify tolerance and that seemed to help with some layers, but I still experience inconsistent results (or no results) across all layers. I don't know if there is something problematic with my services or not as they'll work, just not all of the time.  Do you know of anything for me to check with my services or configuration to enable the widget to work on the desired layers? ... View more

Great, thank you for updating that.  One more thing to make note of for the 1.3.0.2 release is your help doc (Learn more about this widget) shows version 1.2.0.4.  I know similar configuration steps apply but I figured you'd like to update that to 1.3.0.2 at its release. ... View more

Robert Scheitlin, GISP​ I am having trouble getting the Identify widget to work when I add a link or links to the item's results window.  I don't recall having this problem in your 1.1 or 1.2 versions, and I don't think I'm doing anything differently in the general configuration, but perhaps I'm skipping an important step that you notice right away. Example: one of the layers I want to identify is parcels.  I want the assessor's report and school information links to appear in the results window.  If I add them and try to identify a parcel I get the "No Results Found" message.  If I remove the links from the config the results appear as they should (minus any links, of course).  I've experienced this same problem with other layers whose results display should include a link. My setup: All of the link fields are esriFieldTypeString.  Should they be something else?  As far as I know that's what we've had all along.  Those same fields work fine in the eSearch results display. ... View more

Kevin MacLeod​ I have in my WAB 1.2 setup notes that div.jimu-preload-widget.icon changed to PreloadWidgetIcon dijit (or something along these lines) between WAB 1.1 and 1.2.  I was able to get CSS in 1.2 and now 1.3 to work with the following changes: arcgis-web-appbuilder-1.2\server\apps\#\jimu.js\css\jimu.css arcgis-web-appbuilder-1.3\server\apps\#\jimu.js\css\jimu.css (line 702).jimu-widget-onscreen-icon{   position: absolute;   cursor: pointer;   border-radius: 4px;   background-color: rgba(0,0,0,0.5); I added this line and 0.5 is what I want for the default widget background color } What now appears at lines 714-726 is what I added to match the code for this widget: .jimu-preload-widget-icon {   position: absolute   cursor: pointer   border-radius: 4px;   background-color: rgba(0,0,0,0.5); } .jimu-preload-widget-icon:hover{   background-color: rgba(0,0,0,1.0); } .jimu-preload-widget-icon.jimu-state-selected{   background-color: rgba(0,0,0,0.9); } I don't know if this is the best or most efficient way of getting this to work, but it works for me.  Please let me know if you have any suggestions or tips to make it an easier fix. ... View more

Jeremie Cornet​ Thanks for the tip on snapping.  I haven't had time to look into it yet but hopefully will soon. ... View more

Robert, As always, thanks for the information.  I don't think I'll mess with the north arrow just yet.  I was able to switch my default "Preserve" setting per your tip though, and that will help our users. Again, thank you very much. ... View more

Stan: Have you been able to debug the issue with each widget remaining active until clicking on it to unselect or deactivate it? ... View more