|
POST
|
Jeremie Cornet What version number is the release from 10/21 or 10/22? Manifest.json says 1.3.3, as does manifest.json from a couple releases in the last two weeks of September. I've been keeping copies of the older widgets, in the event something new has problems, with titles that reflect the release number. Thanks. Adam
... View more
10-22-2015
12:51 PM
|
0
|
5
|
1463
|
|
DOC
|
Tom Sellsted Thanks, I see what you mean regarding modifying vertices of circles, etc. Knowing where to go in the code to change that setting is very helpful though. Also, I was looking incorrectly at the text editing capabilities. I thought the user could modify the appearance of an individual piece of text or label as opposed to all items. I see now that any changes a person makes in font color or size applies to all text or labels. Sorry about the confusion. Thanks again.
... View more
10-12-2015
12:28 PM
|
0
|
0
|
6800
|
|
DOC
|
Tom Sellsted The updates are great and the help doc is a really nice touch. Our users will really like being able to edit lines and polygons and the live measurement updates as well. I will also second Kevin's idea of the Lat/Long measurement. I personally don't use it, but we have surveyors that use our site everyday and many of them are looking for coordinate measurements. The Coordinate widget can provide that, but it's not as slick as what you see in the 'Measure and Draw' widget in Flex. Beyond that, is it possible for us to change anything in the configuration (widget.js maybe?) that will allow the user to modify the shapes of the other graphics? I have a feeling the majority of our users will be using the line and polygon features far more often than anything else, but am just curious to know if modifying the other features is an option by editing the code. Also, it looks like the user can only modify one piece of text/label that is generated. Am I seeing that correctly? If so, is it possible to enable editing of all text/labels or simply have the option completely removed so nothing can be modified? Thanks for all of your work.
... View more
10-09-2015
12:50 PM
|
0
|
0
|
6800
|
|
DOC
|
Robert Scheitlin, GISP Thank you. I wish I would have paid better attention to that.
... View more
10-01-2015
06:56 AM
|
0
|
0
|
9483
|
|
DOC
|
Robert Scheitlin, GISP Robert: I don't want the identify from "All Layers" to be an option for my users, so I've checked the "Only These" box in the configuration. My config_Identify.json reflects the setting that I want, but "All Layers" continues to be an option in the dropdown list on my application. Has anybody else reported the same thing? Could I have accidentally changed other settings in this process that would override "Only These"? It doesn't appear to cause any problems, meaning I don't get any results when using identifying "All Layers", but I'd like to get rid of that item from the dropdown. Below are images of my config_Identify.json, WAB configuration window and widget in my application.
... View more
09-30-2015
02:01 PM
|
0
|
0
|
9483
|
|
POST
|
Jeremie Cornet This is looking great! I've tested this weekend's release with //tasks.arcgisonline.com/ArcGIS/rest/services/Geometry/GeometryServer and my geometry service, as well as with or without "Use Geometry Engine" checked and the measurements are accurate. The only issue I see at the moment is the labels don't delete upon deletion of the polyline or polygon object. Did I read correctly that a label should automatically delete in that instance? Either way, it's easy to manually delete a label that doesn't correspond to another object. I like that you can create a polyline or polygon without the label, then edit the feature and check on "show measurements", save the changes and the label appears. And, it's great to have the label update as you edit the size/shape of the feature. Our users will really like that. Thank you very much.
... View more
09-28-2015
01:49 PM
|
0
|
1
|
2034
|
|
DOC
|
Robert Scheitlin, GISP Have you had any problems exporting results from the Attribute Table to .csv when using IE? I assume this is an IE issue and not an Attribute Table or Enhanced Search widget issue as Firefox and Chrome work as they should (and I've tested all three browsers on five different machines with only IE11 not working), but just want to check with you on that. If it is an IE issue, do you think in your next release you could have a piece of text, button, etc. available that lets the user know it is best to not use IE if the goal is to export results to .csv? Or do you have a tip or two on how to add that to the widget? Or is there a setting in the current widget I should change? I can add more details later on what happens with IE if you need them. For now I'm just curious to know if you've experienced any problems with IE and export to CSV.
... View more
09-25-2015
07:06 AM
|
0
|
0
|
10267
|