Latest Contributions by FranklinAlexander

I am updating an old flex application to WAB 2.8 and in configuring the identify widget, I cannot get it to see the layer from the eSearch results. I am using 4 map service REST layers for the search, and I have 7 other REST service layers that are being used as base layers, and connected through the Local Layer widget. All of these layers are from the same map service. The identify widget can see all of the layers connected through the Local layer widget (visible in layer list), but cannot see the query results from any of the layers that are configured in the eSearch widget. I did check the box in the widget config to 'Add Result as Operational Layer' and the search results show up on the map as expected. I compared the config settings from the xml file of the older flex app to the new file and they are identical. Not sure what I am missing, but the identify widget in the old flexviewer app can see the results from the eSearch just fine. By the way, both apps, old and new, are using the exact same map service, so I am fairly certain the issue is not with the map service, but something to do with the eSearch widget config. Any ideas of what I might be missing? Thanks! I almost forgot. When I do get results from one of the base layers, 'No Results Found' still shows at the top of the Results pane.  ... View more

Just wandering if it was possible to locate the Full Screen widget to the widget pool instead of having it appear in the top right corner of the map. I have a panel widget that opens at startup, and it covers the Full Screen widget, so I need to relocate it. I tried placing the widget in the widget pool of the config file, but this isn't working. It just places an icon in the header controller that doesn't do anything. I know I can change the position of the Full Screen widget to another location on the map, but the top right just makes the most sense, so it would be nice the header controller would be the best place.  ... View more

I want to know if anyone else has had an issue with clearing the cache in explorer. I had to make some minor changes in a widget.js file because of IE incompatibility issues, but when I cleared the cache and restarted IE, the same problem persists and the console shows the old code!! I tried the published procedure, but it is not working. Driving me nuts! lol ... View more

Does anyone know a good way to check to see if location services are enabled/disabled on a mobile device? I have tried using the following with no luck:  var isMobile = window.matchMedia("only screen and (max-width: 760px)"); if (isMobile.matches) {    if (!window.navigator.geolocation) {        this._displayWidgetError(this.nls.noGPSMobileContent);    } } ‍‍‍‍‍‍‍‍‍‍‍‍‍ I am just trying to alert the user with a popup that states that location services must be enabled to use the 'My Location' tool in the widget. I tried locating the above code in the startup() function, as well as the function where the locate button is initiated, and finally in the function that gets called when the button is clicked, but to no avail.. I am just wandering if there is a better method to do this for mobile devices, but haven't found much via Google.  ... View more

I have a details panel in my nearme widget that shows details for a particular facility which are taken from the layer attributes. A 'directions' link is located at the bottom of the details panel, so that when clicked, Google Maps opens in another browser window. As of right now, the destination autofills with the coordinates of the facility in detail, which grabs the coordinates from the 'latitude' and 'longitude' fields in the table. It is proving to be more of a challenge to get the 'origin' to autofill, since I need to grab these coordinates from the widget.js file dynamically (which is not the issue), and then insert them into the popup 'description' in the config.json file (this is proving more difficult). Below is the code from the config file and the js file. The "description" is where I need to insert the origin coordinates.  I know the href link works, because I tested in by hard coding the origin coordinates. I have tried coming at this from two ways. The first, by inserting a key/value into the config file for the originLat and originLong and then grabbing the coordinates from the 'selectedFeature, and inserting them into the config file values. This is simple enough, but I don't know how the grab them and place them into the href link in the description. I tried using a placeholder, but I cannot find the right syntax, and I am not sure that it is possible.  I also tried placing the coordinates directly into the href link by using the replace() method, but it isn't working. I think this has to do with the fact that the entire description is wrapped in quotes, and I think replace() will only work on the entire string. Am I going about this the wrong way? I am open to any suggestions!  //nearme widget config.json {   "fontColor": "#000000",   "searchLayers": [     {       "originLatitude": null,       "originLongitude": null,       "popupInfo": {         "title": "{Facility_Name}",         "fieldInfos": [           {             "fieldName": "OBJECTID",             "label": "OBJECTID",             "tooltip": "",             "visible": false,             "stringFieldOption": "textbox"           },           {             "fieldName": "Shape",             "label": "Shape",             "tooltip": "",             "visible": false,             "stringFieldOption": "textbox"           },           {             "fieldName": "Longitude",             "label": "Longitude",             "tooltip": "",             "visible": false,             "format": {               "places": 2,               "digitSeparator": true             },             "stringFieldOption": "textbox"           },           {             "fieldName": "Latitude",             "label": "Latitude",             "tooltip": "",             "visible": false,             "format": {               "places": 2,               "digitSeparator": true             },             "stringFieldOption": "textbox"           },         ],         "description": "<table width='100%'>\n<tbody>\n<tr><td width='50%'>Street Address</td><td>{popup_Address}</td></tr>\n<tr><td width='50%'>City</td><td>{City}</td></tr>\n<tr><td width='50%'>State</td><td>{ST}</td></tr>\n<tr><td         width='50%'>Zip Code</td><td>{Zip_Code}</td></tr>\n<tr><td width='50%'>Permit Type</td><td>{Permit_Type}</td></tr>\n<tr><td width='50%'>Comments</td><td>{Comments}</td></tr>\n<tr><td width='50%'>Phone</td><td><a href=\"tel:{Phone}\">{Phone}</a></td></tr>\n<tr><td width='50%'>Alternate Phone</td><td><a href=\"tel:{Alt_Phone}\">{Alt_Phone}</a></td></tr>\n<tr><td colspan='2'><br /><a href='https://www.google.com/maps?saddr= originCoordsGoHere &daddr={Latitude},{Longitude}'>Directions</a>\n</td>\n</tr>\n</tbody>\n</table>",         "showAttachments": false,         "mediaInfos": []‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍ //code from nearme widget.js file //method 1 _initWorkflow: function (evt) {       var selectedFeature, horzontalSliderNode;       //clear previous results       this._clearResults(true);       //get selected feature       selectedFeature = this._getSelectedFeatureFromResult(evt);       //console.log("selectedFeature = ", selectedFeature);       //get and configure selectedFeature lat/long for google directions       var normalizedVal = webMercatorUtils.xyToLngLat(selectedFeature.geometry.x, selectedFeature.geometry.y);       _originLongitude = normalizedVal[0];       _originLatitude = normalizedVal[1];       this.config.originLongitude = _originLongitude;       this.config.originLatitude = _originLatitude; //method 2 _initWorkflow: function (evt) {       var selectedFeature, horzontalSliderNode;       //clear previous results       this._clearResults(true);       //get selected feature       selectedFeature = this._getSelectedFeatureFromResult(evt);       var jsonDesc = this.config.searchLayers[0].popupInfo.description;       if (jsonDesc.includes("originCoords")) {           alert("originCoords found!");           var originCoords = _originLatitude + ',' + _originLongitude;           jsonDesc.replace("originCoords", "this is not working");       } else {           alert("originCoords not found");       } ‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍ ... View more

Ok, I have to ask a very stupid question because this is frustrating me and I know it can't be that hard. I added the LocateButton to the 'NearMe' widget so anyone who needs to do a search for facilities in his/her area can search from their current gps position. Simple enough, accept that in order to tie the button to a search, I need to create a buffer around the gps position, only I can't figure out how to access the actual coordinates the My Location widgets zooms to.  I won't post all of the code, just the snippets I added to the nearme widget for the LocateButton to work.  _geoLocateButton: function() {         if(this._zoomScale === null) {             var zoomScale = parseInt(this._bufferParams.BufferDistance)*1609;         } else {             var zoomScale = this._zoomScale;         }         console.log("zoomScale =", zoomScale);         this._myLocation = new LocateButton({             map: this.map,             scale: zoomScale,             highlightLocation: false,             useTracking: false,             "class": "esriCTGeoLocate"         }, domConstruct.create("div", {}, this.myLocation));         this._myLocation.startup(); }, _connectGeoLocateHandler: function () {       //handle select location button click event       on(dojo.query('.zoomLocateButton'), 'click', lang.hitch(this, function() {           this._onGeoLocateClick();       })); }, _onGeoLocateClick: function (evt) {       this.map.infoWindow.hide();       if (this._searchInstance) {         this._searchInstance.clearSearchText();       }             //the function below needs a point feature produced from an event. I may be wrong,       // but the LocateButton doesn't seem to output a point 'feature'. It can be       // configured to 'highlight' the zoomed to location, but is that the same thing?         // I guess the question is, how to I take the 'result' of LocateButton and turn it       // into a usable point feature that can be passed to the _initWorkflow(evt) function?       this._initWorkflow(evt); }, ‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍ ... View more