I'm not sure if I should start a new thread (as that I do not mean to hijack this one). I found a route on Google Earth at this link; I'm specifically interested in the "Snow Lion" route on Mt. Jasper. https://www.google.com/maps/d/viewer?mid=znBCC7UUSsGY.k47cfyM2Dmy8 There are five icons in the top left of the page of Google Earth, such as tweeting, Facebook, with the last icon looking like a triangle with with three dots. I clicked-on that triangle and then chose to 'Download KML.' The file saved to my downloads folder (in Windows Explorer) as 'untitled.' I tried to add that KMZ file to Basecamp with no success. I then downloaded a software (GPSBabel) to convert it from KMZ to GPZ, and I got an error message. QUESTION: Is it possible to add the "Snow Lion" (or all the routes) at that link to Basecamp, and if so, how....what steps do I follow? Thank you!
Select a list in BaseCamp and then File->Import. The KML file will be imported directly by BC (no other software needed) and the data will be available in the list selected.
Yes, it is, but if the end user messes with a KML/KMZ file association that renders Google Earth inoperative that is the responsibility of the end user, not the developer. A properly installed Google Earth application, no matter what version, will run when launched by an external Windows application running the kml/kmz file; always, without error, without forcing the user to open GE before or any other intervention, from the user or the calling app.
But, if you call GE (the exe) by passing input parameters or some such, as I suspect is the case here, you are the mercy of Google; one change in the way they handle input parameters and the calling app bombs.
Yes, it is, but if the end user messes with a KML/KMZ file association that renders Google Earth inoperative that is the responsibility of the end user, not the developer.
Things other than the end user can mess with it.
(It's a fairly low probability than it would be changed.)
Calling Earth via the file association is reasonable to do.
But, if you call GE (the exe) by passing input parameters or some such, as I suspect is the case here, you are the mercy of Google; one change in the way they handle input parameters and the calling app bombs.
That doesn't appear to be the case here because there would be an error message from Google Earth (not from Basecamp). Since the Basecamp message says Earth isn't installed, it likely doesn't get to using parameters.
It's mostly moot anyway. As long as they get it to work.
That doesn't appear to be the case here because there would be an error message from Google Earth (not from Basecamp)....
Yes, but the error message does not go to the user, that is not how ShellExecuteEx works with robust apps. If BC is using the function Windows will first return a code to the calling app, not to the user. The calling app (BC in this case) will then interpret the code and, if there's an error, it (BC) will show its own error dialog ("not installed") to the user.
...It's mostly moot anyway. As long as they get it to work.
Couldn't agree more, but until they do it's fun to argue. :)
Yes, but the error message does not go to the user, that is not how ShellExecuteEx works with robust apps. If BC is using the function Windows will first return a code to the calling app, not to the user. The calling app (BC in this case) will then interpret the code and, if there's an error, it (BC) will show its own error dialog ("not installed") to the user.
A "robust app" would provide a better/more-accurate error message.
But if I open Google Earth manually (just to the globe centered over the USA) before starting Base Camp, the "Google Earth not installed" message does not appear, and it works fine.
