nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

No GUI components found in this Add-in - what does this mean?

IanBroad1

I made a Python add-in for ArcMap, and one person is having trouble with it. They are using ArcGIS Desktop 10.1 SP1.

They get the following message:

What exactly does this mean? No one else who has used the add-in has had a problem. Could this mean that Python is not installed on their machine? I did a few searches, but couldn't find what exactly causes this error.

Thanks for any input.

Najděte více příspěvků označených jako

Accepted answers

OwenEarley

I have found that this issue can be caused by a configuration setting in the add-in file.

Check the config.xml for the add-in for the following section:

</Targets>

As long as your add-in code is compatible with 10.1 functionality, then changing this setting to 10.1 should make the add-in available to the user.

All comments

ToddBlanchette

Hi Ian,

I can't be 100% sure, but it seems like it's trying to reference something that isn't available on the client's install. I doubt it would be Python itself, as 2.7 gets installed by default with ArcGIS (unless they removed it?). I would check to see that any scripting/tools provided as part of the addin reference anything that is only available at 10.2 if it was created on a 10.2 install. That being said, Python addins don't allow for GUI manipulation anyways, so I suspect some form of incompatibility on the client machine, as it looks like it's describing a .NET addin. My next step would be to try it on another 10.1 machine and see if the same problem shows up, or if it's local to the one machine only.

DanPatterson_Retired

check the backward compatability statement in the link ArcGIS Help (10.2, 10.2.1, and 10.2.2) which see whether they followed the correct procedures

OwenEarley

I have found that this issue can be caused by a configuration setting in the add-in file.

Check the config.xml for the add-in for the following section:

</Targets>

As long as your add-in code is compatible with 10.1 functionality, then changing this setting to 10.1 should make the add-in available to the user.

IanBroad1

Thanks, this seems to have solved the problem. It'd be nice if the Add-in Wizard had a parameter where you set the lowest version the tool works with. But I guess it's an easy fix, as long as you know about it.

Připojte se ke konverzaci

Přihlášení členové mohou přispívat, sledovat aktualizace a další. Jste tu noví? Zaregistrujte si bezplatný účet.

Rychlé odkazy

Community Help
Find useful guides, FAQs, and documents to help you navigate and make the most of Esri Community.