This Idea applies to all Libraries but my main Use Case relates to Class Libraries
I am not sure how everyone arranges there Classes, from trolling online it seems common that non-publically scoped methods tend to get placed in their own Virtual Folder and public methods are at the top-level.
For example:
Unless my Class only has a few methods I would take a similar approach however, most of the time I like to categorize them in more detail. The reason being this is my palette from where I choose my methods, and I like to group them using the following logic so that I can get as much information visually out of the organisation / layout of the Class. I like to have the only top-level method as the constructor if there is one (so I can see that there is one or not for that Class).
I only create the Virtual Folders I need, but usually there are a mix from the follow example:
The problem I have with the current design is that I don't know whether I have scoped my public methods correctly, as I could have forgotten and they are still left not specified - which is the default when you create a new Virtual Folder.
Currently there is no way to tell the difference from the above two Virtual Folders unless you right click on them or possibly look at the contents.
This is not great as there is potential that I could have scoped things wrong which normally leads to me having to check or recheck the scope is correct.
As LabVIEW is graphical by nature, it would be much nicer if I could visually see a public scope glyph to differentiate it from a not specified Virtual Folder.
I selected the color green as it is a natural opposite to red (private) and has not been used yet.
For example:
Therefore, my original implementation would look like the below, and I can straight away see if I have scoped the public folders correctly.
I am sure there was a reason not to include it originally.
I am interested to why and if there is a good reason not to show this too.
