Latest Contributions by AdrianMarsden

OK - I updated to the latest version of the proxy page (1.1 beta - previous version didn't have numbers on) and so far it is looking better.  ( a quick Notepad++ compare shows lots of extra stuff in the newer version) For info, in the logs there seemed to be w3wp.exe Information: 0 : 2014-10-15 09:22:21 Sending request! w3wp.exe Information: 0 : 2014-10-15 09:22:21 Sending request! w3wp.exe Information: 0 : 2014-10-15 09:22:21 Sending request! w3wp.exe Information: 0 : 2014-10-15 09:22:21 Sending request! When it failed, but nothing else. I'll keep watching ... View more

I don't think so, as the issue seems tied up with the proxy and the proxy settings.  I'll see if I can make a cut down version available ... View more

branched to IE fails to use proxy on first load - site stops ... View more

I'll give that a shot, but from testing yesterday it seemed that; With any parameters I always get this error and then the app failed to load my TOC (Nliu's) fails to load only when URL is entered directly or from shortcut A refresh works Sometimes I get these errors without any URL parameters and TOC fails to load. I've modenized my cade with the init code wrapped in a require(["dojo/ready"], function (ready) {     ready(1000, function () { Rather than doing it the old way - this didn't work, but at least I have a bit mre control. Cheers ACM ... View more

A bit more digging (I'm not too good with the IE debug tools) the function that is throwing the first error is                     _onZoomHandler: function(b, e, c) {                         b = this._startRect;                         var d = b.width * e,                             f = b.height * e,                             g = this._img,                             h = a("ie");                         g && (h && 8 > h ? k.set(g, {                             left: b.left - (d - b.width) * (c.x - b.left) / b.width + "px",                             top: b.top - (f - b.height) * (c.y - b.top) / b.height + "px",                             zoom: e * b.zoom                         }) : k.set(g, {                             left: b.left - (d - b.width) * (c.x - b.left) / b.width + "px",                             top: b.top - (f - b.height) * (c.y - b.top) / b.height + "px",                             width: d + "px",                             height: f + "px"                         }))                     }, the actual line is  03 above. ... View more

Not really, the code I have is quite complex.  I've just tested it on a public example of my site and it was fine.  Very strange. ... View more

Have a read of https://community.esri.com/message/342697?sr=search&searchId=e912b943-0f92-4cca-9ce3-093c5d40d80e&searchIndex=10#342697 A lot there about styling floating Panes ... View more

mmm - I think the issue will be the fact that the ArcMap side of this may try to get the extent in, rather than prioritize the scale.  beyond me now I'm afraid. ... View more

No, as I don't use a tiled base map so I have no set zoom scales (well, actually, my base map is a dynamic service, but that dynamic service has, for most scales, a set of tiles, only lower than 1:3,000 does it then hit the fine detailed vector maps) So, my pull down just has a list of common scales the users want, plus allows type in of values ... View more

I've not had any problems here (that I recall) I have a drop down list for scale too, and my print function is below.  It reads in a few extra user stuff, like template, quality, notes (the varibles returned by the various dijit.byId and Dojo.byID).  But seems to work.  I'm sure I did some tweaking, but cannot remember what. function DoPrint() {     graphicsClear();     var legendLayer = new esri.tasks.LegendLayer();     legendLayer.layerId = "mainmap";     SelectedTemplate = dijit.byId('templateselect').attr('value');     vPrintTitle = dojo.byId("PrintTitle").value;     vPrintComments = dojo.byId("PrintComments").value;     vQuality = dijit.byId('quality').attr('value');     var printTemplate = new esri.tasks.PrintTemplate();     if (SelectedTemplate == "maponly") {         printTemplate.format = "JPG";     } else {         printTemplate.format = "PDF";     }     printTemplate.layout = SelectedTemplate;     printTemplate.exportOptions = {         width: 2125.98,         height: 2362.2,         dpi: vQuality     };     // console.debug(printTemplate);     var layoutOptions = {         "copyrightText": currentcopyright,         authorText: vPrintComments,         titleText: vPrintTitle,         scalebarUnit: 'Miles',         legendLayers: [legendLayer]     };     printTemplate.layoutOptions = layoutOptions;     var printParams = new esri.tasks.PrintParameters();     printParams.map = map;     printParams.outSpatialReference = map.spatialReference;     printParams.template = printTemplate;     var printURL = "http://zzzzzzzzzzzzzzzzzzzzzzzzz/rest/services/PrintService2/GPServer/Export%20Web%20Map";     var printTask = new esri.tasks.PrintTask(printURL);     printTask.execute(printParams, function (result) {         window.open(result.url + "?timestamp=" + (new Date().getTime()), '', 'toolbar=0,scrollbars=0,location=0,statusbar=0,menubar=0,resizable=0,width=620,height=600');         printbox.hide();     }); } ... View more

Jonathan Uihlein wrote: Thanks for the feedback. I was able to recreate this issue and it is indeed a bug. This will be fixed in the next release. Promise?  As it's been well and truly documented here on numerous threads since IE10 days, so not a new issue in anyway. previous threads https://community.esri.com/message/334727?sr=search&searchId=e386cdbb-ca50-435e-b70b-6847d8485f0e&searchIndex=10#334727‌ https://community.esri.com/message/78133?sr=search&searchId=e386cdbb-ca50-435e-b70b-6847d8485f0e&searchIndex=1#78133‌ https://community.esri.com/message/387162?sr=search&searchId=e844ff85-f58e-42ff-9975-61f3f4122b2e&searchIndex=11#387162‌ ... View more