We are running a survey to help us improve the experience for all of our members. If you see the survey appear, please take the time to tell us about your experience if you can.
Feature Request: uVision
When I am writing an application I like to have the header files in a project group so that they are easily accessible. Right clicking a group, selecting "Add New Item to Group" and creating a .c file automatically adds it to that group and I think it would be convenient to have the same functionality for a .h file. In fact all the other file types are automatically added to the selected group its just .h files that are different.
I know that the .h file is accessible once it is included in a .c file by expanding the tree in the project view. I do not find it convenient however when I have to search through about 50 .h files associated to that .c file, the majority of which are part of some 3rd party library (e.g. RTOS and STM Hal libraries), to find the one I want.
This issue will be resolved in MDKv5.22 (uVision 5.21.1.55) or later, to allow newly-created header files to be viewed in the same source group, in the Project pane. This removes the need to view all of a source file's header file dependencies in order to see one file.
I think it's both awkward and efficient...
The main thing to remember is that adding a header file to a source group this way does not affect the build tool's ability to find the header file. The header file may still require its location: -location is next to a source file (default folder path in dialog often finds header file this way) -include path supplied to the compiler -source file's include line contains the path
MDKv5.22 should be released soon, and any later version of uVision will also contain this fix.
*(default folder path in dialog often ***allows*** header file to be found this way)