Dockpane no longer shows up when button is clicked

JS_GilbertAZ

I have a dockpane that was working pretty well, I was testing how it might come up if I docked it, so I set dock= to "group" in the config.daml file.  The dockpane no longer shows up, when I click the button to show the dockpane it turns gray.  I changed it back to "float" (i actually used ctrl-z to undo changing it to "group", in case I typed something wrong.  It still just has the grayed out button, without opening the dockpane, so I guess I broke something?  I tried debugging code but when I break it just shows that it's in "break mode".  The code for the button is below, none of that has changed.  I put a breakpoint on the onclick event and it never hit it, so for some reason it's not being called when I click the button?

internal class dpIDTools_ShowButton : Button
{
protected override void OnClick()
{
dpIDToolsViewModel.Show();
}
}

This is in the config.daml:

<dockPanes>
<dockPane id="CustomIDDockPane_dpIDTools" caption="dpIDTools" className="dpIDToolsViewModel" dock="float" dockWith="esri_core_projectDockPane">
<content className="dpIDToolsView" />
</dockPane>
</dockPanes>

Thanks in advance for any suggestions that may help me resolve this.

 

Jeff

 

Wolf

ArcGIS Pro is using 'just in time loading' of add-ins. So when Pro starts and displays your button's icon on the tool bar, it is only the icon that is displayed, your add-in code is not running yet.  Note that this behavior can be changed in the config.daml under the module tag, but by default 'just in time loading' is enabled.  Once you click on the button though (or your dockpane is shown), your code is loaded and executed.  So if you click a button and it turns unexpectedly gray one reason can be (as already mentioned by Uma) that your code-behind cannot find the code-behind class name as referenced by name in the className attribute like in this example:

<button id="..." caption="..." 
  className="Dockpane1_ShowButton" 
  loadOnClick="true" smallImage="....png" largeImage="....png">
</button

So if you change the class name in the code-behind and not in the config.daml you get the 'gray' button effect.  You can also get a 'gray' button if you code-behind is throwing an exception on startup.  As mentioned by Kirk, I would recommend to use source control in which case you can locate your 'suspect' code changes easily be comparing you latest non-functional code with the last working version.