Access Scope based removal of the Actor Framework pop-up in Project Explorer

[njk42]

Describe the bug
The Actor Framework pop-up menu (which provides access to the "Create Message" script) is removed on method VIs in .lvlibs/folders with Access Scope of Private/Community, even though the method VI has Access Scope set to Public.

To Reproduce

• Create a class which inherits Actor, and a method VI for which you want to "Create Message".
• Set that class's .lvlib to Private or Community, but keep the method with Public.
• Right-click on the method and expect the Actor Framework menu, but find that it has disappeared

Expected behavior

• Right-click on the method and find Actor Framework menu so that "Create Message" can be selected and a message class can be scripted for that public method.

Desktop (please complete the following information):

• OS: Windows 10
• LV 2023 Q3

Additional context
See community discussion at:
https://forums.ni.com/t5/Actor-Framework-Discussions/Why-quot-Actor-Framework-quot-menu-in-Project-Explorer-is/td-p/4424178

[niACS]

I assume from the discussion that the actor's library is contained in another library to restrict access to the actor, which is not an arrangement we anticipated when we designed the providers.

The provider tools validate message construction based on the access scope of the target method; the access scope is determined by a call to the VI Server method 'VI.Get Library access Scope'. This method seems to be overriding the access scope defined by the actor with the access scope of the actor's library.

Changing this behavior may require a change to the VI Server method, which is outside the scope of this open source effort.

[svelderrainruiz]

I will convert this into a discussion, so we can referr to this on further issues.

[CaseyZS]

I'm curious about the 'VI.Get Library access Scope' method. Is there no more specific method for a particular item or is the property always and only tied to its containing library?