Closed GoogleCodeExporter closed 8 years ago
To achieve the old behavior, you can remove TimeSpan and TimeStamp information
from
the file.
This looks like a feature request to control the time range in the time slider.
Original comment by api.roman.public@gmail.com
on 6 Apr 2009 at 5:30
Original comment by api.roman.public@gmail.com
on 6 Apr 2009 at 5:31
Original comment by api.roman.public@gmail.com
on 9 Aug 2009 at 12:55
I'm interested in this feature request, as I've just voted. I was looking at
Camera gx:timeStamp and wondering if
I loaded a KML using the KML plugin API and used a time range specification in
a Camera element if that would
set the time slider to a range, rather than a point.
Original comment by mbu...@gmail.com
on 5 Oct 2009 at 8:04
I am wondering if you can programmatically control what is originally set in
the
time slider control. Whenever a kml or kmz file is loaded, it always shows the
first event, then you have to manually slide the control to find the other
events.
I am also interested in programmatically setting the control settings. (ie.
The
timescale play speed)
Other things that might be useful are:
- When the kml element is selected or visible that you can set the time slider
to
include that element to be seen.
Original comment by jonetta.ng@gmail.com
on 5 Jan 2010 at 9:54
Original comment by jli...@google.com
on 11 Jun 2010 at 5:02
Fixed in 5.2.1.1329
Original comment by jli...@google.com
on 16 Jun 2010 at 3:31
Could anyone tell me where the api instructions are for this fix?
Original comment by P...@realphotopros.com
on 15 Jun 2012 at 6:10
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:55
Original issue reported on code.google.com by
gpsanima...@gmail.com
on 4 Apr 2009 at 3:59