@RubberDuck do you have registry keys for Rubberduck.UI._SettingsDialog or it's just me? @Hosch250 can you confirm that there's no registry key / GUID for Rubberduck.UI._SettingsDialog?
it's fine if it's the installer registering it (uninstalling would remove them), but my manual registration of debug builds has generated a shitload of keys
What is happening is that it correctly sees several references inside of a method in ThisWorkbook but double clicking tries to go to the wrong ThisWorkbook (in another file) that is open in the VBE
I have a few addins which load.
mostly the built in ones.
I suspect that the bug might be related to things you already know about.
FindModule extension needs to check the reference of the VBProject in the QualifiedName - I think it only goes by name and returns the first it's finding... which is dumb
Because the context menu doesn't activate the right clicked node - and yes that's another bug ;)
I mean a right-click doesn't activate the clicked node before showing the context menu despite the selection highlight seemingly selecting the correct node
I'm trying to navigate to some modules in the explorer and it isn't going anywhere. I assume that its searching for the item to open and not finding it. There is no user message, is it logging somewhere?
I'm passing a QualifiedModuleName to a CodePane extension method that resolvesshould be resolving the module using the VBProject reference in the QualifiedModuleName
@RubberDuck The projects can be resolved simply with reference equality (.Equals)
That's just by memory though, I'm not in front of the code atm
public static void SetSelection(this VBE vbe, QualifiedSelection selection)
{
//not a very robust method. Breaks if there are multiple projects with the same name.`