> Addendum: It does not appear that Rubberduck will correctly resolve the enum reference if the enum is not in the same module. In this case, it used a class's enum even though it should be resolving to the `Module1`'s enum.
If it's in same module, then Rubberduck is able to resolve it. The problem seems to be that when it's in other module, it needs to give `Module1` higher priority over `Class1`, especially considering that a class (by default) is not globally accessible anyway.
![image