Ability to control time slider handles from KML or plugin API

[GoogleCodeExporter]

What should this feature enhancement do?
The time slider currently loads up with the begin/end handles closed, so that 
no placemarks show up on the globe.  This can be very confusing to a user when 
they don't see anything on the globe.  Please provide a way to set the begin 
and end handle position for the initial load from within the KML or the plugin 
API.  I'd like to at least be able to start with them expanded all the way and 
let the user narrow it down from there.

Are there any known workarounds that produce the similar results?
In the Google Earth standalone you can add a LookAt with a TimeSpan that spans 
from the earliest to the latest placemark and it loads up with them expanded 
all the way.  But I can't get this to work in the plugin.

Original issue reported on code.google.com by stephani...@gmail.com on 28 Sep 2010 at 2:41

[GoogleCodeExporter]

It would be nice to have setExtents() too

Original comment by theb...@emanueleziglioli.it on 6 Jul 2011 at 4:40

[GoogleCodeExporter]

Even better, being able to hook into events when the slider reaches some limits 
so that we can load more data.

Original comment by theb...@emanueleziglioli.it on 6 Jul 2011 at 4:41

[GoogleCodeExporter]

I would strongly support setExtents()

Original comment by Tobias.W...@googlemail.com on 30 Jul 2011 at 1:42

[GoogleCodeExporter]

I would like to be able to set the current time being displayed, i.e. where the 
handle is located. Also restrict users from being able to separate the two 
handles so that there is no way they can view two separate dates at the same 
time.

Original comment by garethma...@hotmail.com on 2 Aug 2011 at 8:53

[GoogleCodeExporter]

I would also like to an options to have them expanded all the way for the 
plugin, then the user can change the range if required, it is of little use 
when its the other way, showing almost nothing until you move the slider right 
all the way then the left one...

any update on this?  seems to be an old thread

thanks

Original comment by leefromc...@gmail.com on 10 Nov 2011 at 11:28

[GoogleCodeExporter]

I would also like that option. There are too many reports from people telling 
me marks aren't there, when all they have to do is widen the time slider span. 
Having the ability to have it open completely, or open over a certain range 
rather than trust that the user will remember would be great!

Thanks,

Paul

Original comment by P...@realphotopros.com on 15 Jun 2012 at 6:18

[GoogleCodeExporter]

http://moonstartravels.com/googlee74cc797749d1150.html

Original comment by qaiserqurryshi12353@gmail.com on 17 Jun 2012 at 5:29

[GoogleCodeExporter]

The ability to lock the "right side" of this slider (or at least move it) would 
be great, this would allow the use of gx:track for realtime data. My use case: 
I'm using a networklink to fetch KML data in real time from a sensor, but I 
can't automatically see the latest data; I have to constantly manually move the 
time slider. Using <flyToView> on the networklink does not work, it causes the 
camera to move even if I only specify a timespan in the <LookAt> element in the 
networklink control. This is very frustrating it basically makes the gx:track 
feature useless for realtime data

Original comment by davetheu...@gmail.com on 26 Sep 2013 at 2:55

[GoogleCodeExporter]

To set the time slider to the full range of the data use:

    ge.getTime().setTimePrimitive(ge.getTime().getControl().getExtents());

Only problem I had was when I tried to call this snippet immediately after 
loading a KML file using fetchKML it didn't seem to do anything. If put into a 
button click callback it worked fine. So, I wrapped it in a setTimeout call and 
all is good.

setTimeout(function() {
    ge.getTime().setTimePrimitive(ge.getTime().getControl().getExtents());
}, 0);

Original comment by ja...@newmoyergeospatial.com on 25 Jul 2014 at 6:53