Talk:C++ Class Explorer Window
> Source Window "Displays the source code, and focuses on the declaration of the item currently selected in the Type List"
Currently the Source Window displays the last item selected either in the 'Type List' or the 'Member View'. IOW, it works off the last item that was selected. Babetb
> Type List Tree Structure "Double-clicking a node (or pressing Enter) loads the corresponding source file into the Source Window and focuses the window on the declaration of the selected item"
Currently Double-clicking or pressing Enter does nothing in particular. We rely on single click selections or 'Up / Down' arrow selection.
I know you're already aware of this: the icons are slightly out of date. The main ones that need to be updated are:
- Source File (I would suggest breaking this into two: The 'Custom File Node' took the previous 'Source File' icon; and 'Source File' now has its own (smaller) icon.
- Event or Property (there are two separate icons now)
> "Group types by inheritance hierarchy. Types are shown under their namespace nodes"
Actually the types are shown under their base type nodes; or flat, if there's no base type. We don't how any namespace nodes when in 'Inheritance Hierarchy' mode/grouping. (That's a big change from Delphi's explorer where the units are the base nodes).
> "Configre custom file groups" ... " Establish the display order of the groups in the Type List"
The order of the groups only apply to the order in which we filter. The order in which the groups are displayed is still alphabetical. IOW, when we see a declaration we'll search the 'File Groups' in the order that specified to determine where it should go. Babetb
> "Note: The context menu commands are enabled only for elements that are declared in a managed unit; that is, the element must be declared in the .CPP or .H file that you are exploring with the C++ Class Explorer"
The real definition of Managed unit is that it must be a source file that's part of your project and it accompanying header file. Although all .cpp files are typically added to the project, a user may have one .cpp file in the project included another .cpp that's *not* part of the project. In that case the first one is considered a managed unit while the second is not. When it comes to headers now things are trickier. The IDE has strict rules about when it considers a header to be the matching file of a source:
- The header's name/location must match that of the source file.
- The header must use a very specific style of header guards.
(NOTE: I'm not sure we need to go into the details of what the IDE considers as the matching header... ). Babetb
Changes made in the help topic. Thanks! - Kris Houser
The "Member of Enum or Union icon" applies only to Enums. Members of a union use the same icons as the members of a class or struct. Babetb
Thanks for the additional comments -- got 'em! - Kris 7/20/09
This is minor but the Description of the "Member View" reads:
Displays the local and global members...
Global variables and functions will show up in the Type List (LHS tree). I can't imagine when they would show up in the Member View. And Global members is a little confusing. Babetb
In the section Icons Used in the Type List and Member View, the Member of enumeration icon is old. It's the greenish one. In order to be consistent with the Enumeration icon, the CE now uses a blueish version of that icon. Babetb
Response
I have incorporated your suggestions. Many thanks!
KrisHouser 14:41, 10 November 2009 (PST)