Print Plus Widget Version 1.1.6 July 12, 2015
Nope 
Still doesn't work correctly for me so using standard Print widget until somebody else figures this one out.
Hi Larry,
I'm experiencing a scale related issue with this widget. I integrated this widget with our 10.5 server (is versioning a issue here ? 10.3 seems to work just fine)
An example is attached with these two pics. The left pic is what it shows on the frame, and the right side is the print. This issue happens whenever I tried to switch from the default paper size to any other page type.
I hope you can point me to a right direction to fix this issue.
Thanks Larry,
KP
PS: Sorry just realized that Larry is not monitoring this post anymore. However this reply can be an info-sharing and hope to see solutions on this! Thanks!
Ok, I think I found out why it did not work for me:
My Map uses Web Mercator. There is a function that calls the geometry service to determine the parameters to project the layout correctly. However this function was only called on startup. So it only worked for the default layout. If you copy the below section into the function _onLayoutChange all the other layouts work correct, too:
if (this.showLayout) {
this.mapUnitsToMeters.x = this.mapUnitsToMeters.y = scaleUtils.getUnitValueForSR(this.map.spatialReference);
if (!this.mapUnitsToMeters.x) {
// We cannot determine the map units, so don't show the layout.
this.showLayout = false;
} else if (this.mapUnitsToMeters.x > 10000 || this.map.spatialReference.isWebMercator()) {
// If the spatial reference is geographic or Web Mercator, call the geometry service to get the parameters to project the layout onto the map.
// This is an approximation, but adequate for small geographic areas (e.g. Hamilton County, IN - 400 Square miles)
// TODO: Check the map area to see if an approximation makes sense
var e = this.map.extent; // TODO: change this to get the initial extent???
var lineN = new Polyline(this.map.spatialReference);
lineN.addPath([[e.xmin, e.ymax], [e.xmax, e.ymax]]);
var lineS = new Polyline(this.map.spatialReference);
lineS.addPath([[e.xmin, e.ymin], [e.xmax, e.ymin]]);
var lineE = new Polyline(this.map.spatialReference);
lineE.addPath([[e.xmax, e.ymax], [e.xmax, e.ymin]]);
var lineW = new Polyline(this.map.spatialReference);
lineW.addPath([[e.xmin, e.ymax], [e.xmin, e.ymin]]);
var eDims = { x: e.getWidth(), y: e.getHeight() };
var lp = new LengthsParameters();
lp.polylines = [lineN, lineS, lineE, lineW];
lp.lengthUnit = esri.tasks.GeometryService.UNIT_METER;
lp.geodesic = true;
esriConfig.defaults.geometryService.lengths(lp,
lang.hitch(this, function(result) {
if (result.lengths.length === 4) {
var southRatio = (result.lengths[0] / eDims.x);
var northRatio = (result.lengths[1] / eDims.x);
var westRatio = (result.lengths[2] / eDims.y);
var eastRatio = (result.lengths[3] / eDims.y);
// TODO: put in a check to fail if the ratios are too different?
// var variation = [Math.abs(1 - (southRatio / northRatio)), Math.abs(1 - (westRatio / eastRatio))];
//console.log('variation:', variation);
this.mapUnitsToMeters.x *= (southRatio + northRatio) / 2;
this.mapUnitsToMeters.y *= (westRatio + eastRatio) / 2;
console.log("this.mapUnitsToMeters_layoutChange", this.mapUnitsToMeters.x ,this.mapUnitsToMeters.y);
} else {
this.showLayout = false;
console.error("Get Map Units to Layout Units Conversion Factors");
console.error("Calculating conversion factors failed. Print layouts will not be shown on the map.");
}
}),
lang.hitch(this, function() {
this.showLayout = false;
console.error("Get Map Units to Layout Units Conversion Factors");
console.error("Calculating conversion factors failed. Print layouts will not be shown on the map.");
})
);
}
}
Unfortunately I still have a problem with vector tile basemaps, that don`t display correctly. As with the above, they work finde in default layout, all the other somehow get cut off. I am not shure though if this is because of 10.5.1 or because of the app 😕
