You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Following discussion on the recent CDT project call, I am creating this issue for the purpose of grouping a number of improvements to the presentation of debug source and header files in Project Explorer.
In cases where a CDT executable project is using a pre-built library that contains debug information, a large number of C/C++ source and header files used within the library may be presented as child nodes of the executable file within Project Explorer (see #443 (comment)). The set of source files provided by the CDT executable project itself can be difficult to locate among all the library source file nodes. In typical usage, the library source files may not be present on the local file system.
The following improvements are proposed for CDT contributions to Project Explorer:
The icons of external source and header files (those files not located within the workspace) should be presented with the external file decoration (CPluginImages.DESC_OVR_EXTERNAL_FILE) as used by the C/C++ Editor and other CDT views
External source and header files should be sorted by file name only (not by file path) - this allows for easier visual search by the user
Absent source and header files should be presented with grey text
A filter should be provided to allow the user to choose whether to hide absent source and header files
The open file action should be disabled in the context of an absent source or header file
The text was updated successfully, but these errors were encountered:
jld01
changed the title
Improve presentation of absent debug source and header files in Project Explorer
Improve presentation of debug source and header files in Project Explorer
Sep 17, 2023
With the latest CDT sources, the presentation of translation unit source files under an ELF executable that has been linked against an unstripped pre-built library is as follows:
The final improvement planned is to allow filtering of absent translation unit source files in the Project Explorer view. We have previously debated whether such filtering should be enabled or disabled by default. The distinction between absent and present source files is now much clearer, but I still think it would be preferable to hide the absent files by default.
Following discussion on the recent CDT project call, I am creating this issue for the purpose of grouping a number of improvements to the presentation of debug source and header files in Project Explorer.
In cases where a CDT executable project is using a pre-built library that contains debug information, a large number of C/C++ source and header files used within the library may be presented as child nodes of the executable file within Project Explorer (see #443 (comment)). The set of source files provided by the CDT executable project itself can be difficult to locate among all the library source file nodes. In typical usage, the library source files may not be present on the local file system.
The following improvements are proposed for CDT contributions to Project Explorer:
CPluginImages.DESC_OVR_EXTERNAL_FILE
) as used by the C/C++ Editor and other CDT viewsThe text was updated successfully, but these errors were encountered: