Latest Contributions by BarnabyRockwell

Adam, I have found something strange.  In the two WAB Dev 2.2 apps for which I am using your LL widget 2.2 beta, the name of the Attribute Table config file is: config_AttributeTable.json For my older apps which use LL widget 2.0 (and all apps from older WAB Dev versions), the name of that file includes a space thus: config_Attribute Table.json So it looks like when a new Att. Table widget config is produced by WAB Dev 2.2, it is produced without the space in the name.  Do you find that to be true?  So I guess the config file name will always be without the space in the future? If I comment out those chars from the _ResourceManager.js file in my app, you are correct that the names of Att. Table layers are correctly read from the Att. Table config file!!!  This is great, many thanks!  I think what happened is that a new Att. Table config file was written in my app when I was configuring LL and Att. Table widgets, overwriting all my layer names in the config file.  When I updated those names in the config file and made your suggested edit to _ResourceManager.js file, all is good. Cheers, Barnaby ... View more

Adam, No, an AGOL WAB app does not have the same issue with visibility toggling with similarly-named layers. Regarding your suggested edit to _ResourceManager.js file, return layerInfo.show && mLayerInfo //&& //(layerInfo.name = mLayerInfo.name || mLayerInfo.title); do you mean that everything after the first mLayerInfo should be commented out (everything in BOLD above commented out)?  If so, then it still doesn't read names from config file. ... View more

Hi Adam, With new beta, the attribute table now shows all layers properly without the edit to the settings.js file of the Att. Table widget! However, the edits to the Att. Table widget shown here now do not work: https://community.esri.com/message/599544  so there is no way to have Att. Table layer names read from the Att. Table config file as in LL widget 2.0.  This is a very important issue for me, and it is unfortunate that esri removed the ability to control layer names in Att. Table using the config file starting with WAB Dev 2.0.  Would it be possible for you to make a change to LL widget, or suggest another edit to Att. Table widget, that would again make names for Att. Table layers readable from Att. Table config file? Also, the two image layers always both turn on when the Landsat 8 dynamic layer is turned on, as in previous betas.  However, if I change the name of the image layers so that they do not start with "Landsat 8," then the layers do not turn on when the Landsat 8 dynamic layer is turned on, and all is good.  Perhaps you could edit the LL widget so that layer names do not affect layer visibility toggling? Also, when I changed image layer names and switched around layer ordering in LL widget editing GUI and clicked OK, I'm occasionally getting endless hangs of the editor accompanied by CPU thrashing, as happened in old versions of LL widget in the past. Cheers, Barnaby ... View more

Adam, With new beta, my Attribute Table looks good in WAB Dev editor with data from all layers loaded.  However, after I save the app and then launch it, only one layer shows in Attribute Table.  After saving, if I enter app editor again, the Attribute Table again shows data from only one layer.  So somehow the changes to the Attribute Table are not being saved properly. I'm still getting the issue in the Layer List when I turn on the bottom-most dynamic layer, the underlying two image service layers also turn on. -Barnaby ... View more

Sent! ... View more

Without the edit to Att. Table settings.js, my Att. Table config file is not read, and no layers show in Att. Table widget editing GUI, just as with earlier WAB and LL widget versions.   I already configured the LL widget using the GUI and exited with OK before opening Att. Table widget.  I did it again, and I get same results, shown below, for which the Att. Table widget is clean and default, no edits at all. No layers show in Att. Table widget editing GUI Only one dynamic layer shows data in Att. Table widget I may have to somehow make Att. Table widget start from scratch and read layers, requiring a laborious reconfig of my Att. Table config.   ... View more

Also, I am having major problems with the Attribute Table after I add image layers.  If I make the change to the settings.js file in the Att. Table widget as for previous LL widgets (note that this edit is not shown in LL widget 2.2 instructions), the layers show in the Att. Table widget editing GUI, and it is reading my Att. Table widget config file, but attributes for only one dynamic layer show in the Att. Table for the app.   I have been using the Att. Table widget edits described here WAB Dev 2.0: How to get layer names for Attribute Table widget to be read from config file  but with or without those edits, my Attribute Table only displays data for one dynamic layer (it is configured to show about 6).  This is a showstopper issue, and I haven't been able to find a workaround. ... View more

Adam, I'm still getting the issue in the Layer List when I turn on the bottom-most dynamic layer, the underlying two image service layers also turn on. Cheers, Barnaby ... View more

Note that WAB Dev 2.2 was just released.  I hope the font fix is in it, also. ... View more

Thanks, Robert!!!! I was also looking at this: Setting Mime Type for WOFF Files on Windows Servers  Adding .woff mime fixed the problem! ... View more

I'll bet Robert removed the page since the widget has been discontinued..... ... View more

Ok, Robert.  I am out of my depth here, but I will look into it. Many thanks, Barnaby ... View more

The widget works for me in Firefox 49.0.1 if I enable popups.  It also works in all other browsers. ... View more

Hi Robert! I'm checking now in IE11 console...... Thanks, Barnaby Edit: @font-face failed OpenType embedding permission check. Permission must be Installable. jimu.js init... What the.....  ?????????????????? Edit2: From jimu.js: @font-face {   font-family: "Avenir Light";/*LT W01 35*/   src: url("./fonts/3511a780-31ca-4ee1-9083-89b1b7185748.eot?#iefix");   src: url("./fonts/3511a780-31ca-4ee1-9083-89b1b7185748.eot?#iefix") format("eot"), url("./fonts/c4352a95-7a41-48c1-83ce-d8ffd2a3b118.woff") format("woff"), url("./fonts/3e419b5b-c789-488d-84cf-a64009cc308e.ttf") format("truetype"), url("./fonts/ca038835-1be3-4dc5-ba25-be1df6121499.svg#ca038835-1be3-4dc5-ba25-be1df6121499") format("svg"); Offending file in bold. ... View more