Latest Contributions by CharlesBailey

Never mind Robert I got it – curly bracket problems…thanks, cob ... View more

Ugh- thwarted at every turn. Could you look at this code when you have a chance? I’ve been working on it all day and just can’t get the syntax right in the CalcMeas code. Hate JS by the way 😮 ... View more

What about this code I found from Ken Doman – do you know him? It’s supposed to extend the measurement widget to add an item to the actionlist in the selection popup, which passes it to the widget for measurement. This would be acceptable if it would work… I placed this js file in the measurement folder in the stemapp and added the widget to my app builder project – to no effect…what else would I need to do? Thanks, cob ... View more

OK – I’m assuming the first part can’t be as simple as removing the feature index, like featureSet.features.geometry; ? Do I have to make a loop or something? When I remove it from that line and the dom.ByID lines the console logs this error. Thanks, cob ... View more

Yeah this has been an issue for a while Robert – our arc server is running on a VM on our network, and the admin was supposed to secure a DNS for it but it still didn’t work. All of our data is in AGOL anyway – we just use arc server for print templates and internal record-keeping. Moreover, the GP tools we publish to the server won’t work on data in AGOL or in SDE on the server, which would be the other big way in which server could help us…but it won’t. One that we’ve tried many times is the ‘add geometry attributes’ tool which has worked once out of maybe 50 tries, but only on data copied to the server with the GP service (i.e. it is static and doesn’t reflect future edits on the data). All I’m trying to do here is find a way for users in AGOL to select a feature set of polys or lines and have the measurements calc in a popup box (I don’t dare dream of having this updated in the attributes…) There are existing tools but every one of them requires the feature to be digitized, and of course there’s not even a trace tool for folks to follow meandering stream boundary lines, for example. Our users will usually start with imported features, then edit them in the process of map preparation, when they will need to know the new dimensions of the edited features. I can’t believe this is so seemingly difficult. ANYWAY… I got the feature action to work, displaying at the top of the select widget panel (which is fine), not using the attach-point but setting the id in the span and keeping the dom.ByID lines. I was going to try to increase the font size – I can do that in the span, correct? – but I realized that it doesn’t work for line features at all, and in fact it only measures the first poly feature when multiple features from the same layer are selected. So really not all that useful for my purposes, and I really don’t understand it well enough at this point to make all the necessary tweaks. So what we will probably do is try to use arcgis pro with the feature services we have in AGOL, so they can have the necessary tools for their workflows. I will keep working on WAB since we have so much invested, especially looking for any new custom widgets that could be deployed or modified to help our cause (hint, hint). And someday I will become knowledgeable on this subject matter (before I retire? Who knows…) We really appreciate all your help; you are an invaluable resource… hope ESRI pays you well. ☺ cob ... View more

Wait, I got it to work with sampleserver6 - Now all I need is the DOMS – would it work to put this in the widget.html file? Measurement Results Area: Length: I have to leave but will be back with this in the morning. Thanks a bunch Robert - cob ... View more

Ok that sort of works, but has to be on the network and most of our users are just in AGOL via internet. Is there any way to do it using the esri public service? ... View more

You mean, like the one on our arcgis server? ... View more

Now it has the Access-Control-Allow-Origin error – I’ve seen this before but have never been able to fix it – is it something in the index.html? Thanks, cob ... View more

Just changed computers and had to start over(again) – it doesn’t seem to like the simplify method in line 33…but when I comment out that part of the line is says unexpected token in line 36 (with the })):)). If I do anything to that line the whole thing blows up and won’t show my feature action in the ellipse dropdown (which has happened like a thousand times). I had a ? about the DOM but need to get the code working first. Thanks Robert - cob ... View more

?OK, finally got that error to disappear - back to the 'not a constructor error'- Here's the edited code too. Thanks-cob ... View more

?something about not being a constructor. here is a screen shot. Thanks Robert - cob ... View more

It just doesn't show up - the vertex count does, but not the calc meas and it's in the manifest and strings. .  ... View more

Right. If I wanted both would I have to have the 'featureActions' function twice? i.e.   "featureActions": [{ "name": "ShowVertex", "uri": "ShowVertexFeatureAction" }], "featureActions": [{ "name": "CalculateGeometry", "uri": "CalculateGeometryAction" }] OR, "featureActions": [{ "name": "ShowVertex", "uri": "ShowVertexFeatureAction", "name": "CalculateGeometry", "uri": "CalculateGeometryAction" }]  ?? But none of this is working - it shows nothing or won't load something with the manifest I think. Thanks, cob ... View more

It still won't work Robert - either it has no effect or the widget won't load. WHat I'm really trying to do is a calc geometry feature action on selected features, but I can't get past the first step for it to even show up in the dropdown. It worked in the demo as far as the sample widget but when I try to add it to the stemapp it won't load either.Here's the calculation feature action I'm trying to use - but as I said can't even get the first step...Thanks Robert - cob ... View more