El 30 Jan 2006 a las 9:04, Bob Hanson escribió:
> It seems odd that
> wireframe DELETE
> undoes the effects of the "connect" command.
I agree with Bob.
Moreover, setting bond order could also make more sense in CONNECT
than in WIREFRAME:
select <sourceAtomSet>
connect <maxDistance> (<targetAtomSet>)
then
connect [bond-type]
then
select <sourceAtomSet> or <targetAtomSet>
connect delete
This way, wireframe deals with rendering, while connect deals with
establishing and removing bonds.
Finally, Miguel, will there be any interaction/interference between
setting multiple bonds and the value of "set bonds"? It may happen
that one defines a double bond which is shown and the double bonds
defined in the file are not shown because nobody sayed "set bonds
ON". I have no proposal, just think of it.
El 30 Jan 2006 a las 9:04, Bob Hanson escribió:
> It seems odd that
>
> wireframe DELETE
>
> undoes the effects of the "connect" command.
> No other wireframe command affects actual connectivity.
> To me it would seem more logical to have
>
> connect DELETE
>
> rather than
>
> wireframe DELETE
-------------------------------------------------------
This SF.net email is sponsored by: Splunk Inc. Do you grep through log files
for problems? Stop! Download the new AJAX search engine that makes
searching your log files as easy as surfing the web. DOWNLOAD SPLUNK!
http://sel.as-us.falkag.net/sel?cmd=lnk&kid3432&bid#0486&dat1642
_______________________________________________
Jmol-users mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/jmol-users
