Code inspection highlighting issues with FUNCRES.XLAM and RibbonX_Code

[quentinharris]

Hi,

I am new to using RubberDuck having downloaded it today. I have looked through the tutorial material, and followed the steps recommended i.e. searching the wiki documentation, [Rubberduck] tag on Stack Overflow etc but still haven't seen anything relating to the following:

When i have a Excel VBE open and am in a procedure i have written (let's say Book 1, Module 1) and i run a code inspection i get a vast number of messages all pertaining to things that should be fixed in the FUNCRES.XLAM/RibbonX_Code e.g.

• Parameter 'control' is never used
• Parameter 'control' is implicitly passed by reference
• Procedure 'ShowATPDialog' can be written as a parameter; and so on.

Questions:

1) I don't know what to do about these messages as they pertain to something i have not created and seem to be there by default. Do i fix? Do i leave alone?

2) Is there a way i can toggle off inspection of XLAM/Ribbon ? I know i can group by location which helps enormously.

Thanks

[MDoerner]

This is related to #3041.

To explain what is happening here: RD always parses and processes all projects open in the VBE. Unfortunately, this includes all third party xlma add-ins. So, RD is presenting inspection results for these add-ins as well. As you usually do not own them, you will not want to run fixes on them.

The linked issue is a request to provide a possibility to configure which projects should be considered. So, we know of the issue and there are a few ideas out there, but we have not gotten around to implement anything, yet.

[rkapka]

Well, that clearly indicates that these add-in developers are writing bad VBA code. Let's introsuce them to RD to so they can fix their issues. :wink:

[quentinharris]

Thanks

[Vogel612]

closing as dupe of #3041