COM API is deprecated (2)

[GoogleCodeExporter]

You seemed to close this issue pretty quickly as a no-fix. On the project 
description you write "The library uses a late binding model to the COM Google 
Earth Plugin Type Library (plugin_ax.dll)." But in your response you say the 
project doesn't use the COM API (issue 35). Your response was "this project 
doesn't use the COM API and never has done..."

As an uncredited contributor to this project (including various patches and 
adding support for NetworkLinks) I am fairly certain the project has at least 
in the past used COM API to access various KML types etc.

Now, I am not sure what Google means when they say they are removing COM 
support but I suspect it will have a direct impact on "late binding model(s) to 
COM Google Earth Plugin Type Library". 

Isn't this worth at least discussing?

Original issue reported on code.google.com by blai...@gmail.com on 7 Sep 2010 at 12:55

• Merged into: #35

[GoogleCodeExporter]

[deleted comment]

[GoogleCodeExporter]

No, sorry, the project has never used the COM API at all. It seems you are 
confusing two entirely unrelated concepts here. 

The COM Api is an application programming interface that allows you to use 
native COM calls on the full Google Earth Application not the plugin. It is 
true that this control library did use an early binding model to the "Google 
Earth Plugin Type Librbary", however this has nothing at all to do with the 
Google Earth COM API.

The now used late binding model simply allows dynamic runtime calls to be made 
on the "Google Earth Plugin Type Library" without referencing a particular 
version of it in development. 
Again this has nothing at all to do with the COM Api.

Hope that clears it up.

F.

Original comment by fraser.c...@gmail.com on 7 Sep 2010 at 1:57