Rolf Huehne wrote:

>      Hi Bob,
>
>I tried the new 'hide' and 'display' commands and like the new
>possibilities very much.
>
>What I still don't like is that 'hide' also displays things and
>'display' also hides things. 
>
comments appreciated -- it might take a little user use to sort this out.

>It is not what you would expect from these
>commands and it will make scripting more complicated in many cases. On
>the other hand it would make scripting easier in some cases.
>Therefore I would propose a configuration switch that sets the behaviour
>of these commands. The question is what the default behaviour should be.
>I would prefer "hide only hides" and "display only displays" because it
>would be more intuitive. 
>
I'm not following what these would mean. Can you be specific? I think 
what you are after is simply understanding how to do it:

display displayed or....
hide hidden or....

This is exactly like

select selected or....

In other words, "display" and "hide" always describe precisely what to 
display or hide. Just like select.

My argument is that it is far simpler to go with what logic we already 
have. Your "switch", I think, is just to be sure you yourself add  
"displayed or" .... "hidden or" .... in cases where that is what you 
want to do.

This is the way select works, and it's precisely the same for "display" 
and "hide"


>But we should discuss this on the user-list.
>
>  
>
the discussion is open.

>While testing 10.9.75 I noted the following:
>
>1) The 'hide' command doesn't hide everything. Meshribbon and trace are
>not hidden.
>
>  
>
I'm sure I checked that -- I thought I had checked it, but maybe not.

>2) The 'dots' command doesn't work any more after 'frame all':
>  error message:
>    script ERROR: ScriptException:surfaces require that only one model
>be displayed
>        Script line:Dots on; color Dots opaque;
>
>  Q: Is this restriction really necessary?
>(This would mean that we couldn't any longer integrate 'dots' rendering
>and also couldn't integrate (fast) surface rendering into our Jmol
>interface.)
>  
>
Well, I didn't intend to break anything for you. The reason is that if 
you have surfaces, those surfaces must be described for individual 
molecules and generated independently. Are these dots you are using 
surfaces, or just spherical elaborations of halos? If the latter, I 
could set it to do exactly that explicitly or implicitly when dots are on.

I'll take that message out in the next edition, and you can see if 
there's any reason for it yourself. I might have just done that because 
it's definitely true for isosurfaces.


Bob


>Regards,
>Rolf
>
>
>-------------------------------------------------------------------------
>Using Tomcat but need to do more? Need to support web services, security?
>Get stuff done quickly with pre-integrated technology to make your job easier
>Download IBM WebSphere Application Server v.1.0.1 based on Apache Geronimo
>http://sel.as-us.falkag.net/sel?cmd=lnk&kid=120709&bid=263057&dat=121642
>_______________________________________________
>Jmol-developers mailing list
>[email protected]
>https://lists.sourceforge.net/lists/listinfo/jmol-developers
>  
>

-------------------------------------------------------------------------
Using Tomcat but need to do more? Need to support web services, security?
Get stuff done quickly with pre-integrated technology to make your job easier
Download IBM WebSphere Application Server v.1.0.1 based on Apache Geronimo
http://sel.as-us.falkag.net/sel?cmd=lnk&kid=120709&bid=263057&dat=121642
_______________________________________________
Jmol-users mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/jmol-users

Reply via email to