Bob, Clear documentation on this stuff is hard to find. This recent discovery on my part is worth mentioning in this chain because it opens more doors for this approach. The event object returns very useful info:
e.key – index key name e.newValue – value being added to key e.oldValue – value being replaced e.url – complete url path of event creator page e.storageArea – ??? The last one is supposed to return, localStorage or sessionStorage, but I’ve had some trouble with that one. The specs say that the event has to be sent to all active windows except the sender. The event is triggered by the setItem(), removeItem(), and clear() methods. With the event carrying the new message, "message eating” is not a factor. Also multiple window action is more easily controlled. My red atom color Jmol Script code in the previous note had a : rather than a ; Typo! Otis -- Otis Rothenberger o...@chemagic.com http://chemagic.com > On Sep 1, 2015, at 4:18 PM, Robert Hanson <hans...@stolaf.edu> wrote: > > That's very cool, Otis. Thanks for the intro to local storage. I especially > like the idea of the event notices. > > Bob > > ------------------------------------------------------------------------------ > _______________________________________________ > Jmol-users mailing list > Jmol-users@lists.sourceforge.net > https://lists.sourceforge.net/lists/listinfo/jmol-users ------------------------------------------------------------------------------ Monitor Your Dynamic Infrastructure at Any Scale With Datadog! Get real-time metrics from all of your servers, apps and tools in one place. SourceForge users - Click here to start your Free Trial of Datadog now! http://pubads.g.doubleclick.net/gampad/clk?id=241902991&iu=/4140 _______________________________________________ Jmol-users mailing list Jmol-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/jmol-users
