Closed andrewphilipsmith closed 7 years ago
Having only had a brief look at this, a couple of observations:
I have reverted merge #132 from the master branch.
To re-merge file changes form this branch some point in the future will require "reverting-the-revert". ie
git revert 09cee17d0ac7b9993c0da83d9aff6290e4278b80
Doing this revert seems to have fixed this bug, based on the master branch. I've removed the "Critical" priority label as a result.
@kes1 , Is it possible/helpful to merge branch map-template-tests
into one of your working branches as you continue to work on this?
Digging around this problem, it seems that this issue seems to be related to the presence of characters related to markup (but not used as markup) in the text. Known problematic characters are &<>
, but this list is not exhaustive. See ArcObjects - Using text formatting tags for more details.
It may be possible to handle individual problem characters with something like:
temp = System.Text.RegularExpressions.Regex.Replace(temp, "&(?!amp;)", "&");
However we might want a more general string sanitation method. Also we should add tests to prevent regressions on this.
Closed by a93d764d87b7f1a01a332d6db32c52e8b1255bab
Using this commit: https://github.com/mapaction/mapaction-toolbox/commit/473cec9a91639078e265f2b32e032a313c4a8198
The FormLoad event for both the Layout tool and the Export tool fails with a
System.NullReferenceException
. In both cases exception occurs after a reference toMapAction.PageLayoutProperties.getLayoutTextElements(_pMxDoc, target_mapframe);
On FormLoad for the Layout tool
On FormLoad for the Export tool