Hi all,
I would like to use TomLUX's Advanced Print Solution but have run into a problem when trying to print with graphics drawn on the screen. I get the following error message when the graphic is a polygon:
Similarly I get errors when the graphics are lines:
...Property textFormat not found on lu.etat.pch.gis.widgets.pchPrintWidget.json.AgsJsonSimpleLineSymbol...
and point:
...Property textFormat not found on lu.etat.pch.gis.widgets.pchPrintWidget.json.AgsJsonSimpleMarkerSymbol...
But NOT if the graphic is text. This happens before the printSelectedExtent function is called, so I can't figure out where I can toggle a breakpoint in debug mode to figure it out. Can someone with experience with this widget help deduce where I can make the code change to prevent this from happening? I am using the uncompiled version of the widget in a 3.0 viewer.
Thanks!
I would like to use TomLUX's Advanced Print Solution but have run into a problem when trying to print with graphics drawn on the screen. I get the following error message when the graphic is a polygon:
Code:
ReferenceError: Error #1069: Property textFormat not found on lu.etat.pch.gis.widgets.pchPrintWidget.json.AgsJsonSimpleFillSymbol and there is no default value.
at lu.etat.pch.gis.widgets.pchPrintWidget::PchJSONUtils$/encodeGraphic()
at lu.etat.pch.gis.widgets.pchPrintWidget.utils::MapUtils$/getPrintLayers()
at lu.etat.pch.gis.widgets.pchPrintWidget::PchPrintWidget/calculateWebMapJson()
at lu.etat.pch.gis.widgets.pchPrintWidget::PchPrintWidget/btnPrint2_printSelectExtent()
at lu.etat.pch.gis.widgets.pchPrintWidget::PchPrintWidget/__btnPrint2_click()...Property textFormat not found on lu.etat.pch.gis.widgets.pchPrintWidget.json.AgsJsonSimpleLineSymbol...
and point:
...Property textFormat not found on lu.etat.pch.gis.widgets.pchPrintWidget.json.AgsJsonSimpleMarkerSymbol...
But NOT if the graphic is text. This happens before the printSelectedExtent function is called, so I can't figure out where I can toggle a breakpoint in debug mode to figure it out. Can someone with experience with this widget help deduce where I can make the code change to prevent this from happening? I am using the uncompiled version of the widget in a 3.0 viewer.
Thanks!