> @hecon5 Max is basically ***the*** person to ask about the resolver around these parts. He diagnosed the problem to be in a feature that was introduced in 2.5.2 which is required for more advanced capabilities for Rubberduck.
Unfortuntately most of the folks working on RD have been somewhat inactive recently (what with the pandemic and this basically being a hobby for all involved), so until someone can locally reproduce the issue with a development build (and write a corresponding failing
> That's what I've done (downgrade); just wondered if there was something I could do to help. 2.5.1 is still way better than nothing; just wanted to take advantage of some of the speed and other features that have been boosted since.
I might actually have a look, but that will have to wait till next week since I am away over the weekend.
@this Would you mind if I give EM a shot? I don't want to steal it from you, but I guess what you have implemented so far is already a bit behind the current structure of the refactorings.
My idea would be do it in multiple steps and to start with the actual refactoring action, then to follow up with the logic to a produce safe refactoring model and finally to add a gui.
> I might have look at this some time next week. Even if we cannot reproduce the issue directly, I think we might be able to get this working by being a bit more permissive or flexible. Bailing out entirely seems a bit excessive.
VBA Rubberducking
VBA Rubberducking