| Author |
 Topic  |
|
|
Ady
New Member
United Kingdom
3 Posts |
 Posted - Jun 07 2006 : 06:47:06 AM
|
| It would be handy if the suggested include filenames could also include files ending with '_i.c'. The MIDL compiler defaults to this filename format for the UUID file. |
|
|
feline
Whole Tomato Software
United Kingdom
19024 Posts |
Posted - Jun 07 2006 : 3:09:49 PM
|
assume i know nothing about COM  i try to avoid it
the file name suggests these generated files are C code files, normally people do not include these into their code.
is it easy for me to just generate one of these, to try and understand what you are doing? |
zen is the art of being at one with the two'ness |
 |
|
|
Ady
New Member
United Kingdom
3 Posts |
Posted - Jun 08 2006 : 04:29:52 AM
|
To create a COM obj in C++ 6.0:
1. New project, ATL COM App Wizard, enter name MyCOMApp
2. Click all finish/ok accepting all defaults
3. Build - the _i.c will not be created until you do this step
4. Look at the file MyCOMApp.cpp this should have a line #include "MyCOMApp_i.c"
5. The file MyCOMApp_i.c is auto created, see the settings for MyCOMApp.idl, UUID File
Once this COM obj has a few interfaces etc when you reference the obj in another app you sometimes need access to the elements in the _i.c file
|
|
|
|
feline
Whole Tomato Software
United Kingdom
19024 Posts |
Posted - Jun 08 2006 : 3:24:12 PM
|
*follows steps*
i see the file, it looks rather like a header file to me, which makes sense since you are including it.
my concern here is how many non COM header files will also match the pattern "*_i.c", and will thus turn up in completion lists when typing #include lines.
is this something you do that often? i am wondering if there is a good alternative solution. the VA wizard bar will show you the full file name of the current file, which is very useful sometimes, allowing you to quickly and easily copy this information from the wizard bar into the clipboard. |
zen is the art of being at one with the two'ness |
|
|
|
Ady
New Member
United Kingdom
3 Posts |
Posted - Jun 09 2006 : 03:47:59 AM
|
You generally need to include a file of this format whenever you reference a COM obj in the app. However it is only needed once as it is an "include" file you can put it in stdafx.
I doubt you will get many false hits as the "*_i.c" is unusual and can't include .cpp files.
Maybe an option in VA to add additional file name filters to display in the suggested included file names. |
Edited by - Ady on Jun 09 2006 03:48:47 AM |
|
|
|
feline
Whole Tomato Software
United Kingdom
19024 Posts |
Posted - Jun 09 2006 : 3:23:34 PM
|
i have put in a feature request, so we can see what the developers think of this
case=1261 |
zen is the art of being at one with the two'ness |
|
|
| |
Topic |
|
#include list to show COM support files
