Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

DataFrame issues for users that add non projected data first #7

Open
topowright-zz opened this issue May 23, 2018 · 4 comments
Open

Comments

@topowright-zz
Copy link

Background

When we try to use the graphics container to draw graphics on a map when a unprojected data source has been added first the graphics container does not added the graphics to the data frame.

Full repo steps and history of issue can be found here:
Esri/visibility-addin-dotnet#248

@csmoore
Copy link
Member

csmoore commented Jun 26, 2018

Additional Note: this issue has also been reported as: "BUG-000114828 : ArcMap graphics disappear during on-the-fly re-projection when the map coordinate system changes."

Here are just the SDK repro steps from Esri/visibility-addin-dotnet#248 (comment) :

Build the Graphics Container SDK sample - Net/Framework/CustomUIElements :

  1. Launch ArcMap
  2. Add a local basemap: C:\Program Files (x86)\ArcGIS\Desktop10.6\TemplateData\TemplateData.gdb\World\continent
  3. Change/set the Data Frame coordinate system to Projected | WGS 1984 Web Mercator (aux sphere)
  4. Use the "Dharma Toolbar" from the SDK Custom UI elements sample to draw a line
  5. Line does not draw after being added to GraphicsContainer
    a. Note: if you draw the line big enough (size of US) you can see a much bigger mis-projected line

image

@csmoore
Copy link
Member

csmoore commented Jul 30, 2019

This issue seems to be resolved at ArcMap 10.7.1.

This was an issue for us from 10.5.1-10.7.

@sindizzy
Copy link

Good news! The BUG-000114828 has been fixed at 10.7.1 https://downloads.esri.com/support/downloads/other_/1071-IssuesAddressedList-06212019.pdf
So from my testing it looks like this bug is present from 10.5.0 to 10.7.0 inclusive. After I reported the bug it took 16 months to fix.

@csmoore
Copy link
Member

csmoore commented Oct 29, 2019

@sindizzy - many thanks for testing+verifying

This issue can be closed (by someone with write access to repo) as resolved at 10.7.1

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants