Esri / military-symbology

A user-focused add-in for searching, creating, and editing military symbols in ArcGIS Pro.
Apache License 2.0
39 stars 10 forks source link

Military Symbol Designer disabled even after loading MilitaryOverlay1.0.1.aptx #49

Closed csmoore closed 8 years ago

csmoore commented 8 years ago

We got to be the first official bug report of against the new Military Tools.

Here is the text:

New Military Tools for ArcGIS Bug Report (MilAna-000001) Submitted. Bug Summary: Military Symbol Designer still greyed Detailed Description: After loading the MilitaryOverlay1.0.1.aptx template the Military Symbol Designer still is disabled. I am using ArcGIS Pro 1.2 on Windows 7 64bit, German environment Priority: High

I guess we should verify this isn't some problem reproducible in the English Pro before we start diagnosing Unicode or the German Pro.

We might need to ask for a screenshot of the Project Pane or more info. Is there some way for a template to be used against a non-FGDB (like can the default GDB be set to an SDE one?) but the code for this is pretty straightforward - as long as that GDB has that exact name

csmoore commented 8 years ago

I did download the addin from the early adopter site and the MilitaryOverlay1.0.1 from http://www.esri.com/apps/products/download/index.cfm?fuseaction=download.main&downloadid=1890 and was not able to reproduce the problem - so this problem may be a little harder to diagnose.

For now, on the beta site I have requested a screenshot that shows the project pane and actual name of the FGDB (sample screenshots attached) - since the addin does make an assumption that this FGDB will be named "militaryoverlay.gdb" (since that is the name from the template) - but maybe this name or file extension is being localized somehow in the German version of Pro.

image

se-mo-screenshot2

csmoore commented 8 years ago

This was reported by the user as fixed with the latest (Pre) Release at: https://github.com/Esri/military-symbol-editor-addin-wpf/releases/tag/v1.1.0pr (that added a check for feature classes vs. particular GDB name)

http://betacommunity.esri.com/project/feedback/view.html?cap=BF895E010443421BA1E73F4383F8A21D&uf=1DA1A6E2FF3D445186980CF7DE61F03E&a=v&t=1

We just need to generate the official MVP-2 release and update on the beta site to fully finish/close this one.

csmoore commented 8 years ago

The user confirmed that the latest release solved this problem