Tus comentarios
There is a separate module for red stars that was part of the zipped package that includes the Denver stars. You can therefore have separate controls over the slum and polysize for just the reddish stars in Uniview.
I do remember Betelgeuse looking a little too red. The original module was based on the Charity colors (http://www.vendian.org/mncharity/dir3/starcolor/), and the way I extracted just the red stars when I originally created the module was to search for certain RGB values associated with spectral classes from the HIPPARCOS-based Denver stars, e.g.,
"255 187 123" M6 (V)
"255 190 127" M4 (V)
"255 198 144" M2 (V)
"255 215 174" K7 (V)
"255 235 209" K4 (V)
"255 210 161" K stars
"255 204 111" M stars
"255 198 118" Scheat
"255 193 104" Betelgeuse
"255 221 175" Arcturus
"255 204 138" Aldebaran
"255 204 111" Proxima Centauri
"255 206 127" Gacrux
Even the reddest of these is just a deep orange, so I'm not sure how they got so red in the final module. I won't have any time for awhile to really debug this, but for anyone who is interested, you play around with the colorbv.cmap file in the module denver_redStars/.
Thanks, Daniel! That's exactly what I needed.
I've confirmed that the uniview.js script is running and sending back "200 OK"s from the sendEvent function. The resume, pause, stop, stepforward, and stepbackward functions in uvCycler.js:range_cycler() all seem to work at least based on the status messages that show up.
For an example of this code to test, check out the profile files referenced in my other support forum thread at https://copy.com/j4oganWtqYDLv3hJ. They contain an example of the range_cycler() code in the first tab of the Custom browser control, with the stepbackward/play/pause/stop/stepforward buttons under "Continuous Cycle":
uvCycler.js
However it would still be useful to be able to edit layers when we are not loading animated time series. Or we have time series that do not have large frame counts, so it doesn't make sense to go to the trouble of making a video (e.g., 12 frames for each month of the year). Often we have multiple sets of short time series.
But what often kills us is needing to keep on deck many different KML files and individual WMS base layers (e.g., Landsat, NAIP, Bing, Black Marble, NLCD). These can add up quickly, especially since we want to have them handy in case the presentation or conversation turns to one direction or another.
With the way things are, I usually have to rebuild layersets from scratch since the layer numbering is opaque, unless you open it up gui.statemanager, and even then that only tells you what layer you need to edit. Editing in the Geoscope window is also not very efficient. Since many of our layersets run into dozens of datasets, this is a real pain.
Let me see if your files can help with our toggling needs. I thought I had a generic function written that would work for any Geoscope layer, but that has recently stopped working in 2.0 as well. I'll report back later today (Monday May 18) ...
Servicio de atención al cliente por UserEcho
Dan: I think you've tracked down the problem!
I dimly recall running into an issue with some of the B-V's. I meant to fix them, but somehow got distracted and left them in the denver_stars modules. I'll see if I can make some time in the next couple weeks or so to correct these values.