Hi,

> 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

I'm not completely sure this would work, but you could try
cmd.set_key('F1',None) before the second binding.  This should eliminate
the previously-bound function.


Good luck,

Pete


Pete Meyer
Fu Lab
BMCB grad student
Cornell University


Reply via email to