Latest Contributions by DavidElies

‎08-21-2015

You might be able to test your print service by going back to your original error message (the XMLHttpRequest error), and copying the full URL in that message into the Firefox address bar. If it you get an HTTP error, you know what to troubleshoot (the print service). If the print server gives you a message, you probably need to configure your print widget. If you get a print image or document, it's probably a proxy config error.

‎08-21-2015

Unfortunately, the .NET proxy provided by ESRI turns every HTTP error into a 500 InternalServerError. Some things to check: Is the URI for the print service reachable? Any typos in the path? Have you tested the print service before? Is there a way to test it without the proxy? Can you debug the proxy.ashx? I usually put a breakpoint in where to 500 error is generated (I forget where it is, I just search for '500' in the file). Then I can see what the actual error is. If you're able to and comfortable changing it, you can also, just for debugging, change the proxy to pass on the original error code/text/etc, rather than creating the 500 error.

‎08-20-2015

It looks like you've turned off alwaysUseProxy, (a good idea in my book), but that means you have to specify a proxy rule for your print server, something like this: urlUtils.addProxyRule({ "proxyUrl": "http://myURL/DotNet/proxy.ashx", "urlPrefix": "https://myURL/rest/services/CustomPrint" });

‎05-12-2015

Thanks for your efforts, Chris Smith, I was able to replicate your process, but I don't know how to get the returned data onto a map. Is there a way to make the esri/layer/KMLLayer load this info?

‎05-12-2015

I noticed that the KML utility service at https://utility.arcgis.com/sharing/kml is able to convert a KML (XML) string. Is it possible to use this ability to create a KMLLayer using the contents of a file rather than a URL?

‎04-09-2015

Thanks Ken Buja, I had to refactor a bit so that my drawtoolbar code could see the click handler, but it works a treat!

‎04-09-2015

I just recently realized that my Map.graphics click handler has been interfering with the Draw Toolbar. When I draw polylines and I click to start a new line in the same poly, the click (which always falls on the line) causes errors because my handler only expects to handle the graphics that I have added, not those from the draw toolbar. My first instinct is to use a distinct graphics layer for the draw toolbar. This would cause the least changes in my code. If not possible, the only other solution I see is to use a distinct graphics layer for my graphics. This would take a lot more work on my part. Is it possible to use a different graphics layer than the map's default graphics layer for the draw (and edit) toolbar? If not, is there maybe another solution I'm not considering? My click handler code could be changed, but I don't know what would always distinguish my graphics from those created by the draw toolbar.

‎04-08-2015

That's a clever way of adjusting the infowindow size. I was hoping there was a way for a layer to request that on its own (similar to the way the info template works). I will do this if there is no API way of making this happen.

‎04-08-2015

A layer (or even individual graphics) can have an info template that describes the content of the infowindow, but I want different layers to have different size info windows. Is it possible for layers to specify the size of the info window used when clicking on their graphics? Mostly I want to make sure that layers that don't specify a size don't get the super-wide info window I want for one of my layers.

‎11-17-2014

Thanks for your response Ken Buja‌, Okay, so "multiple worlds" doesn't work...I'm sure it's with good reason. Does the tile thing work different with the silverlight API? It seems that we can zoom to arbitrary extents with our silverlight application, but we're limited to specific LODs in the javascript API. Do you know if this is the case?

‎11-17-2014

I noticed that the API seems to treat extents as a loose suggestion more than a strict request. I want to show a map that extends from -180 to 180 longitude and floats the y values and just uses the corresponding latitudes for the size of my map div. I tried setting an extent like (-180,-45,180,45), but it still zooms out enough to show the entire -90 to 90 degrees of latitude and leaves blank spaces on the left and right of the map. Is it possible to do this?

‎11-17-2014

I don't know what's causing your error in particular, but I know this happens if your <script> tag that loads the Javascript API is reached and processed more than once. This is because the dojo define/require functions are loaded after they have already been loaded. I'm guessing that if you're not loading the code in more than once place (or running the code more than once from the same place), that firebug might be "caching" the call for the esri library, so it actually loads more than once. I know that I don't see this error in the esri samples when using the Chrome developer tools.

‎11-14-2014

Is is possible to have the map zoom out but still fill it's container from left to right if the container is much wider than it is tall? Many of us have widescreen monitors these days, and I either have to limit the minimum zoom level of the map, which seems to only limit the latitude and leaves too much off the north and south or have white bars to the east and west. What I'd like is for the map to show more than just 360 degrees longitude if I zoom out far enough to show most of the 180 degrees of latitude. Is this possible? Or can I limit the longitude to 360 and show a corresponding latitude for my map size?

‎10-31-2014

Does anyone, (especially at ESRI), have a solution to this that doesn't require using a completely different build of the API or having an interval that hides the popup after the fact? Is there really no way to stop it? If our credentials expire or the layer cannot load for some other reason, we certainly don't want our users to get an ugly, clear popup that has absolutely no meaning to them (the users certainly don't have access to the username and password, heck, I don't even have access to them), we just want it to fail gracefully so we can show the user that the layer has failed and log it so someone who does have access to these things can fix it. It seems silly to show this login box by default, since the consumer of the layer (ostensibly me) and the consumer of the website (our clients) are completely different and showing this failure to properly authenticate on our part to our customers is very unprofessional. Is there a way to fix this?

‎09-23-2014

Thanks for your reply Artemis Fili, I'm very familiar with addProxyRule. We use it to force proxying for those layers which need it. What I'm looking for is a way to force *not* proxying for esriRequests.

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

My Ideas

Latest Contributions by DavidElies

Re: Print dijit, CORS error

Re: Print dijit, CORS error

Re: Print dijit, CORS error

Re: Is it possible to load KML from a file?

Is it possible to load KML from a file?

Re: How can I keep my Map click handler from responding to the Draw Toolbar?

How can I keep my Map click handler from responding to the Draw Toolbar?

Re: Can a layer change the infowindow size?

Can a layer change the infowindow size?

Re: Zooming out limits width to 360, leaving blank spaces on left and right

Re: Zooming out limits width to 360, leaving blank spaces on left and right

Re: Multiple define error when debugging Javascript in Firebug

Zooming out limits width to 360, leaving blank spaces on left and right

Re: Catching IdentityManager prompt when loading ArcGIS Online webmap

Re: Is it possible to force the javascript api _not_ to use the proxy?

KML utility service error without requesting file

Re: Is it possible to load KML from a file?

How do I take advantage of single sign-on (SSO) wh...

Re: WebTiledLayer blank, never downloads

Re: Is it possible to load KML from a file?