|
POST
|
Note that Chrome Dev Channel has moved from 52.0.2743.10 to 52.0.2743.0, indicating a reversion of some sort. bd9df7c452f9a6aadc49214a4a09451fc726be92 - chromium/src - Git at Google
... View more
05-27-2016
09:21 AM
|
0
|
11
|
2449
|
|
POST
|
Oddly, my WAB behavior with Chrome Stable 51 has changed slightly. Locally-hosted WAB Dev apps will not fully load. - Updated 5/27/16 AGOL-hosted WAB apps will not fully load, unchanged from yesterday. - Updated 5/31/16 WAB Dev 2.0 will not load, showing no apps, unchanged from yesterday. - Fixed with patch by Junshan Liu 6/1/16 I cannot reach my organization's Portal at all. For example, I cannot reach http://myexampleorg.maps.arcgis.com/home/content.html - Updated 5/27/16 AGOL-hosted WAB apps cannot be edited using my organization's Portal. The editor hangs with perpetually-spinning progress indicator. Uncaught ReferenceError: normal is not defined - Added 5/27/16 - Updated 5/31/16
... View more
05-26-2016
11:27 AM
|
0
|
0
|
2449
|
|
POST
|
Exactly, Thomas! Most users here will be auto-upgraded for "security" purposes.
... View more
05-26-2016
09:53 AM
|
0
|
0
|
2449
|
|
POST
|
I just upgraded Chrome to version 51 (51.0.2704.63 x64), and now none of my WAB apps, even AGOL-based apps, will fully load. They partially load and the progress thingy just keeps spinning. On my server, WD 1.2 and 1.3 will load into Chrome and show apps, but none of the apps will load fully when launched. WAB Dev 2.0 will only partially load into Chrome, and no apps are shown. I can see that I am logged in to my organization's Portal, so that is not the issue. Does anyone else see this? Is there some way I can configure Chrome 51 settings to allow WD 2.0 and apps to load fully? All is normal with Firefox 46.0.1 and IE11. My organization's default enterprise browser is Chrome, so if anyone upgrades to current version, they won't be able to use any of my apps. Chrome 51 includes many security fixes: Chrome Releases
... View more
05-25-2016
02:49 PM
|
6
|
44
|
30107
|
|
POST
|
Robert, You are correct. I just checked my config.json to see if my values matched yours. I mentioned the importing as perhaps Thomas' config.json got messed up if he created a new app from scratch in 2.0. Cheers, Barnaby
... View more
05-24-2016
10:01 AM
|
0
|
1
|
2452
|
|
POST
|
Thank you, Robert! The "left" is 200 in all my apps, which I presume is the default, and I never changed that setting, or anything else in the app's config.json, for that matter. { "uri": "widgets/Coordinate/Widget", "position": { "left": 200, "bottom": 20, "relativeTo": "map" }, "id": "widgets_Coordinate_Widget_4", "positionRelativeTo": "map", "name": "Coordinate", "label": "Coordinate", "version": "2.0.1", "keepConfigAfterMapSwithched": false }, Note that I imported the app (including Coordinate widget) from WD 1.3, and thus didn't create it from scratch in WD 2.0. Cheers, Barnaby
... View more
05-24-2016
09:49 AM
|
0
|
3
|
2452
|
|
POST
|
I've never seen that behavior and can't duplicate it. You could try removing/re-adding the widget and playing around with the scalebar widget also.
... View more
05-24-2016
09:33 AM
|
0
|
0
|
2452
|
|
POST
|
Which outcome? The coords/scale overlying the ruler? Yes, the widget is installed as per first post.
... View more
05-24-2016
09:03 AM
|
0
|
8
|
2452
|
|
POST
|
Hi Tom, In my WD 2.0 apps, the coords and scale are always just to the right of the scalebar ("ruler") in Chrome, IE 11, and Firefox, and look exactly the same as you show for WD 1.3. Here is one of my WD 2.0 apps: ArcGIS Web Application I did not reconfigure anything. Which theme are you using? I have only tested and used the widget in the Foldable theme. Cheers, Barnaby
... View more
05-23-2016
02:56 PM
|
0
|
12
|
4673
|
|
DOC
|
An option to disable the Google Street View coverage visibility would be good for some apps, I imagine...
... View more
05-12-2016
11:20 AM
|
0
|
0
|
13340
|
|
DOC
|
Fantastic! It works perfectly. This is a great enhancement of Robert's widget. Without it, users have to load a basemap containing streets (Open Street Map, esri Streets) to know where to drop the man, and even then can waste time dropping the man on streets not covered by Google Street View coverage. Most WAB apps already use Web Mercator to get the basemaps to display as fast as possible, I expect.
... View more
05-12-2016
10:18 AM
|
0
|
0
|
13340
|
|
DOC
|
Very well done, Ian. Your widget shows users where they can drop the man. Could be very useful when a basemap (like Imagery) not showing roads is used. Could you update your demo app to include the esri Imagery basemap? Cheers, Barnaby
... View more
05-12-2016
10:03 AM
|
0
|
0
|
13340
|
| Title | Kudos | Posted |
|---|---|---|
| 1 | 05-27-2016 12:48 PM | |
| 1 | 04-05-2017 09:52 AM | |
| 1 | 10-29-2015 12:59 PM | |
| 1 | 03-31-2017 12:33 PM | |
| 1 | 04-07-2016 10:08 AM |
| Online Status |
Offline
|
| Date Last Visited |
11-11-2020
02:24 AM
|