Hello, For me, it's still not clear why the include files (.h) are treated in such a cumbersome way in the uVision2 Project philosophy. When you have a project and you create a group -for instance- called 'Header files' then you have to specify that those files are Text documents to be able to add it to your project. The file types in the file open dialog box do not contain something separate for .h files, whereas this is the case for e.g. .c, .a* and .src files. Could someone explain me why is this? Wouldn't it be more logic, user-friendly and convenient if the .h-files would be treated the same way as .c- or .a51-files? Rgds, Geert
You'll like a new feature of the latest version, then. It has a list of all files #include'd by any compiled file as part of the project "Files" window. You click on the '+' to open up the sub-nodes, and select your include file from the list. OTOH, I can't quite follow you why the existing method is "tedious". It's a few more mouse clicks than to add a .h file to a project than a .c file --- so what?