Latest Contributions by BarnabyRockwell

widget [widgets/Query/Widget] created.  WidgetManager.js:112:21 ReferenceError: LayerInfos is not defined[Learn More]  Widget.js:767:15     .createIdentifyParams/< http://myserver/usminmaplocal2.3test/widgets/Identify/Widget.js:767:15     .cache["dojo/_base/lang"]/</e.hitch/< http://js.arcgis.com/3.19/init.js:63:207     .cache["dojo/_base/array"]/</e.forEach http://js.arcgis.com/3.19/init.js:70:383     .createIdentifyParams http://myserver/usminmaplocal2.3test/widgets/Identify/Widget.js:736:9     .identifyFeatures http://myserver/usminmaplocal2.3test/widgets/Identify/Widget.js:683:22     ._onDrawEnd http://myserver/usminmaplocal2.3test/widgets/Identify/Widget.js:547:9     .cache["dojo/_base/lang"]/</e.hitch/< http://js.arcgis.com/3.19/init.js:63:207     k/</c http://js.arcgis.com/3.19/init.js:119:70     ._onDrawEnd http://myserver/usminmaplocal2.3test/jimu.js/dijit/DrawBox.js:483:7     .cache["dojo/_base/lang"]/</e.hitch/< http://js.arcgis.com/3.19/init.js:63:207     .cache["esri/Evented"]/</r<._onArr2Obj/< http://js.arcgis.com/3.19/init.js:646:175     k/</c http://js.arcgis.com/3.19/init.js:119:70     h<._drawEnd http://js.arcgis.com/3.19/esri/toolbars/draw.js:18:257     h<._onClickHandler http://js.arcgis.com/3.19/esri/toolbars/draw.js:31:324     .cache["dojo/_base/lang"]/</e.hitch/< http://js.arcgis.com/3.19/init.js:63:207     k/</c http://js.arcgis.com/3.19/init.js:119:70     .cache["esri/MouseEvents"]/</r<._fire http://js.arcgis.com/3.19/init.js:1276:13     .cache["esri/MouseEvents"]/</r<._fireClickEvent http://js.arcgis.com/3.19/init.js:1282:130     .cache["dojo/_base/lang"]/</e.hitch/< I'll check the syntax again now. Edit:  no obvious syntax errors introduced... ... View more

Robert, with that code, I get no ID results at all for any layer.  Widget just hangs and chugs.....  But I did not edit app or update ID widget config, just added the code to the widget.js. ... View more

Hi Robert, PM sent. Cheers, Barnaby ... View more

I entered Adam's new code into the widget.js of a deployed app, and the ID results show entries for every sublayer of a huge MapService, even if those sublayers are not visible (not clicked ON in Layer List: visibility settings set in mxd prior to publishing). Results are also shown for every sublayer (visible or not) in every service (layer) which is turned on in the app, not just the huge MapService.  So it appears that the new code creates serious problems for me. In another geographic area, the ID widget hangs when I click on the map.  Not good.  My huge MapService (100s of sublayers), is one of many layers in the Layer List, so I think that the MapService unique subLayer IDs don't correspond with their position within the Layer List, if I am understanding what Adam is referring to. Edit:  note that I did not edit the app or change the ID widget config, I just added the new code to the ID widget.js. ... View more

Hi Robert, I'm using ID widget 2.1 in a WAB Dev 2.2 app with LocalLayer widget.  I noticed that if a sublayer in a dynamic map layer has a scale visibility range set in the mxd prior to publishing, the ID widget will show results for that sublayer even when the sublayer isn't displayed due to current viewing scale (when that sublayer is grayed out in the LayerList).  Do you also see this behavior?  If so, perhaps there is a ID widget config (or even in LocalLayer widget config) setting I am missing that would change the behavior?  Currently the ID widget is configured to show results for visible layers. Interestingly, the issue only occurs when I am zoomed in beyond the maximum visible scale for the sublayer.  If I am zoomed out beyond the minimum visible scale for the sublayer, no ID widget results are shown (this is good). This behavior is not present in Flex using your ID widget for Flex, which only displays ID results for visible layers that are "on" (not grayed out) in Layer List.  The issue also occurs with a locally-hosted WAB Dev 2.2 app which calls an AGOL Web Map (LocalLayer widget not used, but ID widget is).  I have an active, public app that you can use to see this behavior if you want. Cheers, Barnaby P.S.: I'm running Server 10.5, if it matters... ... View more

Adam, First tests suggest that new beta works perfectly!  No issues found, and it's lightning fast. Good job, Barnaby ... View more

Robert, This is great.  I guess I'll have to try out eSearch! Cheers, Barnaby ... View more

I'll keep the bugged app up for as long as you want.  Since it appears that you may release another beta, I will suspend testing of current beta. ... View more

I have found a showstopper issue.  Using latest beta in a deployed WD 2.2 app, I am getting unresponsive browser (hangs) when I try and turn on sub- and sub-sub layers in a dynamic service.  These hangs did not occur in LL 2.0, which works perfectly.  Here is a test app using latest beta: ArcGIS Web Application  Use bookmarks to zoom to Tintic mining district, UT.  Then, in Layer List, turn on Regional Studies dynamic layer, then turn on Tintic mining district, UT (you may see a delay even here after clicking on), then try and turn on one or more of the layers under that.  There are delays of up to 10 seconds after you toggle a sublayer on, resulting in a temporarily hung browser. I don't know if these hangs are related to the hangs I mentioned earlier that occur sometimes when you click OK in LL widget editing gui when edting an app in WD 2.2. Here is perfectly functional WD 2.2 app using LL widget 2.0: ArcGIS Web Application  It appears that lots of code has been removed for LL 2.2, including code to stop hangs.  Apparently this code was removed to mitigate layer visibility toggling issues perhaps related to the addition of new functionality in LL 2.2 (e.g. image/wms layer capability).  From my current perspective, removing this code was a mistake, as it is apparently causing other severe issues which degrade core app functionality. I will again (groan) test my apps with latest beta to see if there is something I can do on my end to fix the issue, including adding back in the code which Adam removed. ... View more

Groan is right.  I have no desire to change that code just for my apps.  May be best to live with the hangs...  But I'll check to see if commenting out the code results in any issues with operational layer visibility. Edit: Adam, does adding that (old) code on your end have a downside? ... View more

Adam, Uncommenting that code does not seem to fully eradicate the hangs, but it could possibly reduce it a little, sometimes, anyway. After more testing, I think that uncommenting the code does help.... ... View more

Robert, It appears that I cannot PM a non-image file.  It says my json file is in an unsupported format.  What should I do? Cheers, Barnaby ... View more

Yes, I am getting heinous errors in console, 80 of them for one hang.  I'll try Adam's suggestion now. TypeError: Unable to get property 'tables' of undefined or null reference TypeError: Unable to get property 'tables' of undefined or null reference    at Anonymous function (http://internal1.gs.doi.net:3344/webappbuilder/apps/7/jimu.js/LayerInfos/LayerInfos.js?wab_dv=2.2:581:15)    at Anonymous function (http://js.arcgis.com/3.18/init.js:63:200)    at h (http://js.arcgis.com/3.18/init.js:107:273)    at k (http://js.arcgis.com/3.18/init.js:107:205)    at resolve (http://js.arcgis.com/3.18/init.js:109:280)    at Anonymous function (http://internal1.gs.doi.net:3344/webappbuilder/apps/7/jimu.js/LayerInfos/LayerInfoForMapService.js?wab_dv=2.2:519:9)    at c (http://js.arcgis.com/3.18/init.js:103:387)    at d (http://js.arcgis.com/3.18/init.js:103:182)    at errback (http://js.arcgis.com/3.18/init.js:105:163)    at c (http://js.arcgis.com/3.18/init.js:104:61)    {       [functions]: ,       __proto__: { },       description: "Unable to get property 'tables' of undefined or null reference",       message: "Unable to get property 'tables' of undefined or null reference",       name: "TypeError",       number: -2146823281,       stack: "TypeError: Unable to get property 'tables' of undefined or null reference    at Anonymous function (http://internal1.gs.doi.net:3344/webappbuilder/apps/7/jimu.js/LayerInfos/LayerInfos.js?wab_dv=2.2:581:15)    at Anonymous function (http://js.arcgis.com/3.18/init.js:63:200)    at h (http://js.arcgis.com/3.18/init.js:107:273)    at k (http://js.arcgis.com/3.18/init.js:107:205)    at resolve (http://js.arcgis.com/3.18/init.js:109:280)    at Anonymous function (http://internal1.gs.doi.net:3344/webappbuilder/apps/7/jimu.js/LayerInfos/LayerInfoForMapService.js?wab_dv=2.2:519:9)    at c (http://js.arcgis.com/3.18/init.js:103:387)    at d (http://js.arcgis.com/3.18/init.js:103:182)    at errback (http://js.arcgis.com/3.18/init.js:105:163)    at c (http://js.arcgis.com/3.18/init.js:104:61)"    }    "TypeError: Unable to get property 'tables' of undefined or null reference    at Anonymous function (http://internal1.gs.doi.net:3344/webappbuilder/apps/7/jimu.js/LayerInfos/LayerInfos.js?wab_dv=2.2:581:15)    at Anonymous function (http://js.arcgis.com/3.18/init.js:63:200)    at h (http://js.arcgis.com/3.18/init.js:107:273)    at k (http://js.arcgis.com/3.18/init.js:107:205)    at resolve (http://js.arcgis.com/3.18/init.js:109:280)    at Anonymous function (http://internal1.gs.doi.net:3344/webappbuilder/apps/7/jimu.js/LayerInfos/LayerInfoForMapService.js?wab_dv=2.2:519:9)    at c (http://js.arcgis.com/3.18/init.js:103:387)    at d (http://js.arcgis.com/3.18/init.js:103:182)    at errback (http://js.arcgis.com/3.18/init.js:105:163)    at c (http://js.arcgis.com/3.18/init.js:104:61)" ... View more

Latest version works for me, but I am getting substantial (several minute) hangs when I click OK on LL widget editing GUI. So the issue with visibility toggling of similarly-named layers in Layer List is a WAB Dev issue?  In Layer List widget perhaps?  Again, there is no such issue in AGOL WAB apps or in local WAB Dev 2.2 apps which call AGOL Web Maps. ... View more

For WAB Dev 2.2, Adam Drackley found that Attribute Table layer names will be read from config file if the following edit is made to _ResourceManager.js file in the WABdev_2.2\server\apps\#\widgets\AttributeTable folder.  For the change to be applied to the Attribute Table in future apps, make the change to the _ResourceManager.js file in the WABdev_2.2\client\stemapp\widgets\AttributeTable folder. Edit:  This change also works for WAB Dev 2.3. Change this return layerInfo.show && mLayerInfo && (layerInfo.name = mLayerInfo.name || mLayerInfo.title);   To this,   return layerInfo.show && mLayerInfo //&& //(layerInfo.name = mLayerInfo.name || mLayerInfo.title); ... View more