in defining the text string view_name, spaces are disallowed, eg "rotate 30". Although the position will be created, the reset command will not properly access the position key. What are the allowable characters? Matthew Dougherty National Center for Macromolecular Imaging Baylor College of Medicine ===========================================================================
This is a bug. The reset command should allow quotes such as reset “rotate 30” 50 I’ve fixed the code so the name can be quoted in the reset command. In tonight’s daily build. Any character other than quotes should be ok in the position name. Tom
On Jun 23, 2015, at 1:53 PM, Dougherty, Matthew T wrote:
in defining the text string view_name, spaces are disallowed, eg "rotate 30". Although the position will be created, the reset command will not properly access the position key.
What are the allowable characters?
Matthew Dougherty National Center for Macromolecular Imaging Baylor College of Medicine =========================================================================== _______________________________________________ Chimera-users mailing list Chimera-users@cgl.ucsf.edu <mailto:Chimera-users@cgl.ucsf.edu> http://plato.cgl.ucsf.edu/mailman/listinfo/chimera-users <http://plato.cgl.ucsf.edu/mailman/listinfo/chimera-users>
I think you need to avoid whitespace and semi-colon, which will screw up the parser. Anything else should be okay I think. --Eric Eric Pettersen UCSF Computer Graphics Lab http://www.cgl.ucsf.edu On Jun 23, 2015, at 1:53 PM, "Dougherty, Matthew T" <matthewd@bcm.edu> wrote:
in defining the text string view_name, spaces are disallowed, eg "rotate 30". Although the position will be created, the reset command will not properly access the position key.
What are the allowable characters?
Matthew Dougherty National Center for Macromolecular Imaging Baylor College of Medicine =========================================================================== _______________________________________________ Chimera-users mailing list Chimera-users@cgl.ucsf.edu http://plato.cgl.ucsf.edu/mailman/listinfo/chimera-users
I would think other symbols should be avoided like commas, single/double quotes, and apostrophe come to mind; plus non-viewable characters like tabs & device codes. Then there is the question of unicode characters, which ones in, which ones out. Ligatures could be messy Filesystems, domain servers and HDF have similar restrictions & condundrums. In terms of a generic sw development project, probably best to have an api that tests or corrects for acceptable text strings within the program. Matthew Dougherty National Center for Macromolecular Imaging Baylor College of Medicine =========================================================================== ________________________________ From: Eric Pettersen <pett@cgl.ucsf.edu> Sent: Wednesday, June 24, 2015 2:46 PM To: Dougherty, Matthew T Cc: chimera-users@cgl.ucsf.edu Subject: Re: [Chimera-users] savepos I think you need to avoid whitespace and semi-colon, which will screw up the parser. Anything else should be okay I think. --Eric Eric Pettersen UCSF Computer Graphics Lab http://www.cgl.ucsf.edu On Jun 23, 2015, at 1:53 PM, "Dougherty, Matthew T" <matthewd@bcm.edu<mailto:matthewd@bcm.edu>> wrote: in defining the text string view_name, spaces are disallowed, eg "rotate 30". Although the position will be created, the reset command will not properly access the position key. What are the allowable characters? Matthew Dougherty National Center for Macromolecular Imaging Baylor College of Medicine =========================================================================== _______________________________________________ Chimera-users mailing list Chimera-users@cgl.ucsf.edu<mailto:Chimera-users@cgl.ucsf.edu> http://plato.cgl.ucsf.edu/mailman/listinfo/chimera-users
participants (3)
-
Dougherty, Matthew T -
Eric Pettersen -
Tom Goddard