Latest Contributions by BarnabyRockwell

‎03-08-2016

Note that a floating "button" for an optional "click to enable saved app state from last session" has already been implemented in AGOL WAB viewers. It is safe to assume that this excellent new feature will be available in WAB Dev 1.4. When is WAB Dev 1.4 scheduled to be released?

‎02-23-2016

Robert, Thanks. Rather extensive experimentation on my part with the the ClientID/Secret method confirms what you say. Cheers, Barnaby

‎02-23-2016

Robert, Item #3 in your post, The big thing about step 3 is that the item is PUBLIC (the app item that you are registering). The webmap is still private and secured though. appears to be key. I cannot make any registered app in my organizations's AGOL group public. Do you know if it is possible to make the ClientID/Secret auth method work if the registered app is NOT public? Cheers, Barnaby

‎02-22-2016

While some users like the "cached" app state feature, most do not. Few users need to be returned to the state/extent of the last session, and it confuses people who expect to see the original extent and layer visibility settings, as they have to figure out how to go back to default extent. And of course, the original visibility settings for all the layer/sublayers in the app are gone, and will remain gone until all cookies are removed. Disabling the state saving for the app removes these issues. It is interesting to note that if the LocalLayer (LL) widget is used for a WAB Dev 1.3 app, avoiding AGOL Web Maps, the "cached state" works just for the extent of last session, and original layer/sublayer visibility settings as set in the LL widget config are maintained. This is how I would expect the "saved state" to work in apps calling AGOL web maps except that it would be better if the visibilities of ALL layers/sublayers in the Layer List would be maintained across sessions. Of course, the state saving should be optional and configurable in the WAB editing GUI, as I'll bet will be the case in the next WAB update.

‎02-11-2016

Excellent, Ryan!!!! Many thanks for the info and link. Cheers, Barnaby

‎02-11-2016

Kevin, The "remembering" functionality is quite nice, but is ruined (for me) by the auto-toggling of visibilities for layer/sublayers which weren't even touched in the last viewing session. It looks like a bug to me, and a major one. All they need is a Reset button embedded in the app by default as I mentioned. A Reset button would be great in the Layer List as you mentioned. Or they could just modify the existing Home button to clear the "data cache," resetting extent and all layer settings to default. Home button is best kept as simply an extent reset, but you could query the user after Home is clicked, asking if the layer settings should also be reset. Simplest is best IMO. I don't think a widget is a good idea for this, as it takes up a widget slot for something that should be built in. But if a widget is all they come up with, I'll take it.

‎02-11-2016

As far as I know, the only way to reset the extent is to click the Home button (at upper left in foldable theme). Now if there was only a way to also reset all the layer visibility settings as well!!!!!!

‎02-11-2016

In apps made with WAB 1.3 (AGOL) and WAB Developer Edition 1.3, zoom level, geographic location, and layer visibility settings are saved in the browser "data cache" (?) across browser viewing sessions. These settings are maintained even if browser data and memory caches are cleared. This major change was apparently conceived as a nifty way to allow users to "resume" viewing sessions. I have an AGOL Web Map with many layers. These layers have very complex visibility settings for sublayers, sub-sub layers, etc. These visibility settings were set in the mxds before the services were published. I have not changed any of those settings in the Web Map. I noticed today that if a user toggles layer and sublayer visibility in an app in a browser, closes the browser, reopens it, and returns to the app, ALL layer/sublayer/sub-sublayers in the app are TURNED OFF except for the ones which were on when the previous session was closed. This unfortunate, show-stopping problem occurs in WAB apps generated on AGOL or WAB Dev 1.3 which call the AGOL Web Map. It appears to me that the visibility settings of ALL layers/sublayers in the app should be saved to the "data cache," not just the settings of the layers which happened to be toggled on when the app viewing session closed. Or, there should be a "Reset" button in the app which resets it to "factory default" settings in all regards. This show-stopper of a problem is preventing me from distributing links to WAB 1.3 apps which call AGOL Web Maps. All WAB 1.2 apps are fine in this regard. Is this a bug, or is there a simple workaround that would enable a user to reset the app's layer visibility settings to the default (meaning those shown in the Web Map)?

‎02-05-2016

That sounds like a good idea, but it should be a select-able option, not mandatory.

‎02-04-2016

They were few, but critical. I can't go operational with WD1.3 and the LL widget until a 1.3 version is released (hopefully sooner rather than later), as LL widget 1.2.2 will not function at all for certain services. Thankfully, Adam has already developed fixes for the issues.

‎02-03-2016

Thank heavens...

‎01-28-2016

I wonder how the widget will perform in Edge?

‎01-28-2016

Note that, in IE11, although the icons will vanish as you click them, they will all return if you add one to the mashup. True for 1.2 and 1.3 versions of the widget.

‎01-27-2016

Back in February 2015, Tim Witt released a modified Coordinate widget that also shows current map scale. I took the scale-related elements of that widget and added them to the Esri Coordinate widget released with WAB Developer Edition 1.3. Here's a screenshot of the widget working in an app made using WAB Dev 1.3: To install, unzip and place "Coordinate" folder in the widget folder of your WAB Dev 1.3 app after deleting the stock Esri Coordinate widget: WABdev_1.3\server\apps\#\widgets I strongly recommend that you DO NOT replace the stock Esri Coordinate widget in the base widget folder (\WABdev_1.3\client\stemapp\widgets), as doing so will greatly complicate general app handling (e.g. duplicating, creating) and the importing of apps from WAB Dev 1.2. Update April 1, 2016: Initial testing suggests that this widget works in WAB Dev 2.0. Update July 19, 2016: Initial testing suggests that this widget works in WAB Dev 2.1.

‎01-15-2016

I see the changes to the Attribute Widget in WD 1.3 as quite problematic, almost as if Esri is moving in a direction that will make LL widget use more troublesome. Even in WB 1.2, I always have a terrible time getting layers added via LL widget to display in Attribute Table widget. Most of the time I have to manually edit the Att. widget config and remove all layers before new layers will be added to it automatically in WAB Dev editor. The Attribute Widget has major problems in that regard, and is exceedingly difficult to use smoothly, at least with LL widget. I wish Esri would allow complete control over the Att widget, including how/when layers are added and displayed. Once layers are added, it works great, of course.

Online Status	Offline
Date Last Visited	‎11-11-2020 02:24 AM

My Ideas

Latest Contributions by BarnabyRockwell

Re: "Cached" layer/sublayer visibility settings in WAB 1.3 apps calling AGOL Web Maps - MAJOR BUG?

Re: Internal ONLY Web Map Sharing Issues

Re: Internal ONLY Web Map Sharing Issues

Re: "Cached" layer/sublayer visibility settings in WAB 1.3 apps calling AGOL Web Maps - MAJOR BUG?

Re: "Cached" layer/sublayer visibility settings in WAB 1.3 apps calling AGOL Web Maps - MAJOR BUG?

Re: "Cached" layer/sublayer visibility settings in WAB 1.3 apps calling AGOL Web Maps - MAJOR BUG?

Re: Web map not defaulting to initial extent

"Cached" layer/sublayer visibility settings in WAB 1.3 apps calling AGOL Web Maps - MAJOR BUG?

Re: Enhanced Bookmark Widget Version 2.5 - 08/17/17

Re: LocalLayerWidget and AccessifizrWidget

Re: Roberts Custom WAB Widgets

Re: Enhanced Basemap Gallery Widget 2.8 - 05/1/2018

Re: Enhanced Basemap Gallery Widget 2.8 - 05/1/2018

Coordinate + Scale widget for WAB Dev 1.3

Re: LocalLayerWidget and AccessifizrWidget

Re: WAB killed by Chrome 51

Re: WAB killed by Chrome 51

Re: Internal ONLY Web Map Sharing Issues

Re: .NET proxy setup no longer working for WAB Dev...

Re: WAB Dev 2.0: How to get layer names for Attrib...