Hello !
I finally found out what my problem was. Thanks to Warren DeLano I tried to
overwrite a cmd.set_key with another one in a very simple setting, and it
worked. That made me realize that what I wanted to do was to override a
cmd.set_key()' with a scene selection rather than with another cmd.set_key()
like I initially thought:
(...)
cmd.set_key('F1',showonlyone,['-1-100'])
(...) some script (...)
cmd.scene('F1','store','HPC-4 Fab structure: overview')
Conclusion: a set_key binding takes precedence over a scene storage. Thank you
for your suggestions; I have now added Peter's cmd.set_key('F1',None) at some
point to release the keys for scene storage, my presentation is finally
smoothed !
Garteiser Philippe
OMRF, Cardiovascular Biology dpt.
Doctoral candidate, OU Bioengineering
Advisors: Dr. Tim Mather, Dr M. Uli Nollert
12600 N Macarthur
Crown Pointe apt. #1423
Oklahoma City, OK 73142
home: (405) 603 7091
work: (405) 271 4924
"It does not pay to leave a live
dragon out of your calculations"
- Tolkien
----- Original Message -----
From: Warren DeLano <war...@delsci.com>
Date: Monday, February 12, 2007 9:17 pm
Subject: RE: [PyMOL] how do i unset a cmd.set_key() binding ?
To: philippe.garteise...@ou.edu
> > I have a problem with set_key() that appeared when I executed two
> scripts
> > sequentially. In both scripts I set the F1 key to do something
> different
> > (ok, not a very smart move...). I thought that the newest set_key()
> would
> > take precedence over the latest and overtake its adressing, but
> > unfortunately it does not.
>
> Strange -- it does for me... how are you using it exactly? Is it in a
> module you import?
>
> Cheers,
> Warren
>
> > -----Original Message-----
> > From: pymol-users-boun...@lists.sourceforge.net [
> > boun...@lists.sourceforge.net] On Behalf Of
> philippe.garteise...@ou.edu
> > Sent: Friday, February 09, 2007 5:31 PM
> > To: pymol-users@lists.sourceforge.net
> > Subject: [PyMOL] how do i unset a cmd.set_key() binding ?
> >
> > Hi list !
> >
> > I have a problem with set_key() that appeared when I executed two
> scripts
> > sequentially. In both scripts I set the F1 key to do something
> different
> > (ok, not a very smart move...). I thought that the newest set_key()
> would
> > take precedence over the latest and overtake its adressing, but
> > unfortunately it does not. The binding is very persistent, because I
> need
> > to close pymol and reopen it altogether between the two scripts so
> that
> > the new binding can take place. The current workaround for me is to
> have 2
> > pymol instances opened (btw wow on pymol's performance even on slow
> > machines ! 30 proteins in one window and a density map in the other
> on
> > just 512M at 1.8GHz !), but I would still prefer to know how to do
> that.
> >
> > Thanks in advance !
> >
> > Garteiser Philippe
> > OMRF, Cardiovascular Biology dpt.
> > Doctoral candidate, OU Bioengineering
> > Advisors: Dr. Tim Mather, Dr M. Uli Nollert
> > 12600 N Macarthur
> > Crown Pointe apt. #1423
> > Oklahoma City, OK 73142
> > home: (405) 603 7091
> > work: (405) 271 4924
> >
> > "It does not pay to leave a live
> > dragon out of your calculations"
> > - Tolkien
> >
> >
> ------------------------------------------------------------------------
> -
> > 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
> >
>
> > _______________________________________________
> > PyMOL-users mailing list
> > PyMOL-users@lists.sourceforge.net
> >
> >
>
