The KML alpha value becomes the maximum alpha value not just the initial valu...

[GoogleCodeExporter]

Comments: 
The KML alpha value becomes the maximum alpha value not just the initial value

Make a Polygon with an alpha value equal to 100 say and then load it up into 
Google Earth. You'll see that alpha=100 is now the maximum alpha value for this 
polygon.This surely cannot be by design or to be consistent the <open> tag 
would mean that a folder was always open or forever closed.

Relevant Application(s): 
Google Earth 4.2.0198.2451 (beta) in Windows

Reported By: nix

Original issue reported on code.google.com by api.roman.public@gmail.com on 14 Aug 2008 at 10:51

[GoogleCodeExporter]

Noob here.  I was only a few minutes into my first foray of KML files when I
unwittingly stumbled upon this problem.  

I see this was reported over a year ago, but I think the description is vague.

So here's a description of what I did:

I too drew a polygon and used the slider in the Places pane to set opacity.  
Then I
right-click on the polygon and cut-paste it into a text editor where I see all 
alpha
values set to FF - the max - in the KML, rather than the correct alpha value. 

So this means GE can't save away opacity values for later use, right?  :(   
Ouch.

But once I hand edit the KML file to set the alpha value to less than FF, then 
open
it in GE, I see that GE leaves the alpha value alone.  So I think I'm left to
hand-edit my alpha values and sorta guess at what the hex value is of the 
opacity I'm
happy with when viewing/setting it in GE.

Using version 5.1.3533.1731 (Build Date Nov 12, 2009) in Windows XP.

Original comment by chantill...@gmail.com on 18 Dec 2009 at 6:59