kml has visibility off for every point about bbl2kml HOT 4 CLOSED

So, there is a difference in behaviour in the way desktop GE works v. the web version. I'm sure there is a "lost in time" reason why it's the way it is; I'll have look at it.

from bbl2kml.

What a mess; the OGC KML standard mandates the behaviour requested; however Google declines to implement in the desktop application as "changing this would break existing code" . As most the users use the desktop (vice the web) application; the web app being somewhat unusable on my rural broadband), I'm going to follow Google's lead on this. However, the next release (tomorrow I hope) will (a) offer an option to override this and (b) have a configuration file if you want to make a different behaviour your personal default).

$ flightlog2kml -help
Usage of flightlog2kml [options] file...
 ...
  -visibility int
    	0=folder value,-1=don't set,1=all on

Anything other than the default of 0 causes the desktop client to misbehave, and the web client to behave rationally.

I'll push the changes to development later today, prior to the later master merge and release.

from bbl2kml.

Test binaries
fl2x-0.9.7rc2.tar.gz

from bbl2kml.

Aha I figured there had to be a reason like the way it is supposed to be vs what works in various Google platforms. Nice that it behaves differently across the clients. I had been using the desktop Google Earth, but this machine didn't have it installed so I used the web platform for the first time.

The test binaries work, I tried all three options. -visibility 0 gives me the regular behavior and both -visibility 1 and -visibility -1 allow me to toggle the entire track from the top level folder item in Google Earth web. Perfect! Also love the inclusion of the squares for RTH markers, that's a nice feature.

from bbl2kml.