> The problem: > > at this moment the Jmol Readers take a DisplayControl only, and no > reference to Jmol itself... it can thus not call a specific Jmol > method... But, it could use the approach used in the NewwinAction... > > However, problem 2: > > the Reader cannot open up a second window just like that... that would > break it for use in the applet... which cannot open up a second > window...
My quick thoughts. I think the way to do this is route it through the DisplayControl. The DisplayControl is already using an interface to deal with its two types of containers. (It is currently called JmolStatusListener ... but it is going to get a name change to JmolContainer). We can define a JmolContainer method to determine whether or not the container is multi-window capable. The IO code could route through the control to a) determine whether or not the container is capable of opening up multiple windows, b) request it to do so. I agree that this is not a short-term thing. Miguel ------------------------------------------------------- This SF.NET email is sponsored by: eBay Great deals on office technology -- on eBay now! Click here: http://adfarm.mediaplex.com/ad/ck/711-11697-6916-5 _______________________________________________ Jmol-developers mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jmol-developers
