spacemap 0.1.15 → 0.1.17

package/README.md

@@ -47,7 +47,7 @@ your page:
 ```html
 <div id="map" style="height: 500px"></div>
 <script type="module">
-	import { createMap } from 'https://cdn.jsdelivr.net/npm/spacemap@0.1.15/dist/spacemap.js';
+	import { createMap } from 'https://cdn.jsdelivr.net/npm/spacemap@0.1.17/dist/spacemap.js';
 	const map = await createMap({ container: '#map' });
 </script>
 ```
@@ -123,6 +123,7 @@ hold.release();
 | `featureselect`                   | a nomenclature label was clicked                   |
 | `clock`                           | the date, play state, rate or direction changed    |
 | `loading` / `progress`            | data is coming in                                  |
+| `idle`                            | the camera is at rest and the view is fully loaded |
 | `error`                           | the data could not be loaded                       |
 | `notice` / `noticedismiss`        | a condition worth telling the reader about         |
 | `layerschange`                    | a layer was switched                               |
@@ -662,6 +663,22 @@ A `system` is named by its primary and measured in the primary's radii. A body
 with no moons has no system map, and asking for one rejects, leaving the map as
 it was.
 
+A ringed primary's rings are a band across every ring there is, out to the
+faintest dust: Saturn's runs past Mimas, Enceladus, Tethys and Dione to the
+E ring. `rings: 'visible'` spans only the rings `createMap` shows, at the cost
+of the primary's bundle and its ring profiles:
+
+```js
+createSystemMap({
+	container: '#picker',
+	view: { kind: 'system', id: 'naif-699' },
+	rings: 'visible'
+});
+```
+
+Jupiter's and Neptune's rings are too faint to see, so their systems then have
+no band.
+
 **A click reports what was picked and goes nowhere.** Walking down into a
 system and back up is the page's own doing, which is what lets it keep a back
 button, a breadcrumb or a URL of its own: