As for user types, you can't. VB does not accommodate you, you must accommodate VB. You have to declare the structs in IDL syntax in the IDL file. The MIDL compiler will then create a struct definition that you must use. This will also be visible in VB.
ms-help://MS.VSCC/MS.MSDNVS/automat/htm_hh2/chap12_2bqr.htm
I fear enums are completly impossible as VB doesn't understand the concept of enums (or does it? I'm not sure). But you can define a series of constants in the IDL file (that's what DAO does).
What do you mean by modules?
All the buzzt CornedBee
"Writing specifications is like writing a novel. Writing code is like writing poetry."
- Anonymous, published by Raymond Chen
Don't PM me with your problems, I scan most of the forums daily. If you do PM me, I will not answer your question.
I don't get it... i've been trying to make this work for hours...
Your saying to make changes in the idl file, but in the readme.txt it says that the file is created everytime I buid the project, so then whatever I type in there, it will be erased...
And when I DID modify the idl file, after I compiled the project I got this message:
Is there a way to make the WAVEFORMATEX public to VB in the interface thing ?
This is the code I have now...
Put this code at the beginnin of my previous code (the interfce and the class has to see them)
Code:
[export, v1_enum]
enum eList {
e1 = 1,
e2 = 2
};
[export]
struct MYFLOT {
int i;
};
// to export an already defined struct you will have to rename it, like this (I put a "t" in front)
[export]
typedef struct tWAVEFORMATEX WAVEFORMATEX;
And you HAVE to use them in a method or property, otherwise they will not show up
When I do that (the code I pasted previously), I get this error "Variable uses an Automation type not supported in Visual Basic" when I try to use the type (struct)
The enum works fine... but can't figure out what's wrong with the struct thing...
So... ANYONE... please help me... i'm trying to figure this thing out for 2 days !!
OK... it seems that whenever I post a question here, shortly after that I find the anser on my own... I should do that more often
I was paying so much attention the the "export" thing, and what should I do with that to fix it, that I did not see that I was using WORD variable types (that are unsigned short) and of course, Visual Basic does not support unsigned....
So, I changed my variables to just short, and it works now... again...
Odd..... it really feels like there is no one else there on the net (this forum), I'm kinda like talking to myself...