Hi Burr, I'm not sure what's up with oleview not working anymore for you - maybe you're ending up using a 64-bit oleview and you would need to use a 32-bit oleview instead since moi_lib.dll is a 32-bit DLL ?

But at any rate, there's also a link to the moi.idl file here:
http://moi3d.com/wiki/Scripting

So you can just download that instead of using oleview.

- Michael

I wonder if it has anything to do with when I made the transfer of OS's I didnt do a MoI installation on the new OS, just a folder move???

Hi Burr - moving the folder over should not make any difference for this. MoI's installer basically just copies files into the folder, the only thing that I can really think of that the installer does in addition to just copying files is to set up an uninstall entry in the control panel and also setting up a file association for .3DM files if not already set, so you can open MoI by double-clicking a file in the windows explorer.

My only guess is that maybe you're running a 64-bit oleview which may not want to load 32-bit files. You could try installing this older version of oleview and see if it will work:
http://www.microsoft.com/downloads/en/details.aspx?FamilyID=5233b70d-d9b2-4cb5-aeb6-45664be858b6&displaylang=en

But you can also just download the moi.idl file from the link on that scripting page in the wiki instead of using oleview at all.

- Michael

""""""""""""But you can also just download the moi.idl file from the link on that scripting page in the wiki instead of using oleview at all.""""""""

I dont understand this part.. I have the moi.idl file already. Do you mean to just use Daves interface to read all the info?

Hi Burr, well the only thing that oleview does for you is to give you a way to extract the moi.idl file that is embedded inside of moi_lib.dll .

If you already have moi.idl , then there is no need to use oleview for anything at all, you would just be getting at the same file that you already have.

As far as reading moi.idl itself - it's just a text file so you can look at it with any text editor program, you don't need any special viewer program just to look at the .idl file.

You'll see various interfaces defined within the moi.idl file, and different properties and methods will be listed within each interface.

But Dave's web pages have this same information presented in a nicer way so you probably just want to look over there instead anyway.

- Michael

> But Dave's web pages have this same information presented in a nicer way so you probably just want to look over there instead anyway.

I might mention that the information on my web page is, in some ways, a superset of the information in the moi.idl file. I wrote a script that extracts all of the API information from the .idl file and then, by hand, annotated many of the properties, methods and arguments with as much detailed information about the interface as I could muster by eyeballing the API and, in some cases, experimenting with more obscure interfaces via test scripts.

The extraction script also performs "deltas" between successive versions of the moi.idl file, so new API elements will appear in the web page automatically (although any descriptive information will need to be added by hand).

If anyone wants to contribute additional API descriptions for inclusion in the web page, be sure to let me know :-)