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.
Project Window Wish Items When you right click on "<file>.c" in the project window, add an option "Open <file>.h". Likewise, when you right click on "<file>.a51" in the project window, add an option "Open <file>.inc". It is a multistep process to add a ".h" or ".inc" as a text file to the project It should be as easy as adding a ".c" or a ".a51" file to the project. Also, add a "rename" option when you right click a Target, Group, or File in the project window.
When you right click on "<file>.c" in the project window, add an option "Open <file>.h". Likewise, when you right click on "<file>.a51" in the project window, add an option "Open <file>.inc". Not everyone uses that convention for externs and function prototypes. If you right-click on a #include <file.h> in the source code, one of the options opens the header file. It is a multistep process to add a ".h" or ".inc" as a text file to the project It should be as easy as adding a ".c" or a ".a51" file to the project. You are right. We will add this in a subsequent release. Also, add a "rename" option when you right click a Target, Group, or File in the project window. This feature already exists, however, the click-change is kinda goofy. You have to click REALLY SLOW and uVision2 will let you rename a GROUP or TARGET within the Project Window. Jon
Thanks for the "slow" double click technique. Even though it is a window's standard technique, I would not have thought of it. It sure beats editing the .UV2 file. In regards to Not everyone uses that convention for externs and function prototypes. If you right-click on a #include <file.h> in the source code, one of the options opens the header file. How about the simpler task of adding a "Open <file.h>" to the context of any file. Opening the corresponding ".h" file is just too useful of an action not to place on the context menu.
How about the simpler task of adding a "Open <file.h>" to the context of any file. Opening the corresponding ".h" file is just too useful of an action not to place on the context menu. OK. I'll add it to the list. Jon
OR: why not have the Project window automatically display all the #included files - like Borland C++ Builder does (among others) This should include the .SRC file for 'C' files with the 'SRC' option
It is a multistep process to add a ".h" or ".inc" as a text file to the project It should be as easy as adding a ".c" or a ".a51" file to the project. Go to Project/File Extensions, Books and Environment; Add "*.h" to the list of "C Source Files" and "*.inc" to the list of "Asm Source" files; Now, the "Add Files to Group" dialogue will include those extensions, and it will be just as easy as adding a ".c" or a ".a51" With uVision v2.14, this will even enable the syntax colouring for "unusual" extensions; eg, my Client also uses ".e" for some 'C' headers. It's also worth adding things like ".lst" and ".m51" to the "Document File" list - then these can be opened as plain text files. The only limitation is that this doesn't affect the filetypes shown in the File/Open dialogue. :-(