Latest Contributions by CoyPotts1

That's what I was afraid of.  Thanks for the information, Dan.  ... View more

You are correct!  I have been trying to fix the issue with line 13, but it wasn't actually line 13 that was causing the problem.  I was missing a closing parentheses just before it. A product of copy/paste when the copied text was actually incorrect.  I've been looking at this off an on while doing other things for a couple hours lol...I knew it was going to be super basic. Thanks for taking a look . ... View more

Yes, that is very helpful.  Thank you much! ... View more

That would definitely be ideal...but I don't know how to do that either, unfortunately.  I didn't know you could do that.  Is the methodology just a lookup of the definition query value and then an error message if it doesn't exist? I'll add a little as well. Our feature classes have an initial query of "NetworkID IS NULL", so that whenever someone opens up our template map, they'll ideally see nothing.  They load the new project data, modify the fields in each feature class to match the NetworkID of their respective project, and then apply that definition query to each feature class to show only that NetworkID. The problem is that not everyone remembers to do this.  When they get to a certain point where they are to run a script that calculates/runs a lot of fields/tools, they're going to be doing so to a much wider range of data than intended. Since we already have a query applied to show NetworkID IS NULL, I am thinking something like this: class tool_name(object):      """Implementation for addin_name_addin.button_tool_name (Button)"""      def __init__(self):           self.enabled = True           self.checked = False      def onClick(self):           for layer in layers:  # will define above                if layer.isFeatureLayer:                     if layer.name == 'SampleLayer1'                          if layer.definitionQuery == """  'NetworkID = 'SampleProject' """  # I would like to add two options (as shown, and if == none)                               pythonaddins.MessageBox('Modify the ' + SampleLayer + ' definition query and retry.', 'Incorrect Definition Query', 0)                          elif:                               pass                     elif:  # going through the rest of my feature classes with this level of elif's                          pass                elif:                     pythonaddins.GPToolDialog(toolPath, 'ToolName')     I'm sure there are some issues with this, but it's just a stab in the dark.  I'm not sure if the placement of the tool run command is correct, and I'm not sure if my quoting around my definition query is correct either, just to name some that I have concerns with.  ... View more

That didn't fix the issue.  All of my buttons (not just the one I'm modifying) show up as missing.  ... View more

I can already see an error, but I'm not sure if it'll fix the issue.  I'm only using one equals sign for mbAnswer = 'Yes'.  I'll give that a go.  ... View more

Just to highlight on what you referenced above, we did actually experience an issue with the add-in with the users that were still using 10.2.  The add-in was working just fine on my machine, but whenever the others opened their maps, the buttons didn't react when clicked.  Simply saving the toolbox to the 10.1/10.2 version did the trick with no other modification needed. Thanks again for all of your help!  I'd probably still be lost in documentation somewhere trying to figure it all out .  ... View more

Yeah, there were quite a few models that we used in 10.3, that we could no longer see when re backed up to 10.2.  Research resulted in me finding out that there is no way to down-save an individual model, but rather you have to down-save the entire toolbox.  I'm sure there are little intricacies that go along with that as well.  I've been simply exporting the models to python and then trying to clean them up as they're not quite perfect once exported. In reference to creating new buttons manually...I don't even attempt to mess with that lol.  Whenever I add new things, I just add an *_1 at the end of my *_addin.py file and then re-save the project with my newly added features.  NOTE:  I realize that if you save the project, it will automatically add *_1/2/3/4 to the end your existing *_addin.py file, but I actually experienced a complete project folder reset one time when I tried that.  I ended up losing the *_addin.py file that had my tool references and everything, so I was a little agitated .  How do you roll an add-in back?  I don't see how to do so.  Is this where the target version in the XML file is used?  If so, mine creates it with a target version of 10.1 every time, so I should be good if that is the case.   ... View more

Rebecca, One last question regarding this stuff here.  You reference using a widget to edit your XML files in your comment above, but I don't think you mentioned what the widget is called.  I google search returned a lot of options for XML editors, but I like the way yours looks in the attached image above so I wanted to give that a try and see if I like it. Thanks! ... View more

I believe that I may have found the issue.  I was tinkering just a bit more and found that the button was working, and I realized that the one that was working was one that was created inside a project folder that contained no spaces. I created an identical project inside of two separate folders ("test_addin" and "test addin").  The button inside of "test_addin" worked, while the button that was inside of "test addin" did not.  Can either of you confirm that the spacing in the project folder does indeed affect the add-in? ... View more

I will circle back and summarize what I find once a solution has been determined.  No rush on getting any files to me.  I believe I will move on to something else and give this a rest until support reaches out.  Maybe the break will do some good .  ... View more

The mismatching is due to me creating a whole new project thinking that there may have been an error somewhere down the line that I didn't notice.  I created a whole new project so that the *_addin.py file would be default (thinking that the default file would eliminate any syntax errors).  I've been using the MessageBox example as shown above just to test, but the button still shows as missing even if I don't add the MessageBox function.  I can generate a completely default *_addin.py file, create/install the add-in, and ArcMap still shows a missing button.  There can't be any syntax errors if I haven't even typed anything into the file...something has to give here lol.  Thank you for your recommendations and assistance as well.  I appreciate the efforts.  ... View more