I think it must be a SWIG thing - using scheme, (active-atom-spec) returns a similar looking result (something to do with collectable-swig-pointer - coot won't let me copy/paste from the scheme scripting interface) while pushing the following error to the console:
** (coot-real:17331): WARNING **: scheme callback returning #<unspecified> where value expected: #<procedure #f (event)> Oliver. On Tue, 31 Dec 2013 16:45:31 +0000, Paul Emsley <pems...@mrc-lmb.cam.ac.uk> wrote: >On 31/12/13 16:31, Oliver Clarke wrote: > >> >> Another note - what is active_atom_spec() supposed to do? I guessed it was >> an equivalent of active_residue() but returning the specific atom rather >> than the CA, > >That's right. > >> but it returns this when called: >> >> _90ac6c78c97f0000_p_std__pairT_bool_std__pairT_int_coot__atom_spec_t_t_t >> >> While pushing the following to the console: >> BL INFO:: command input is: active_atom_spec() >> BL INFO:: result is <Swig Object of type 'std::pair< bool,std::pair< >> int,coot::atom_spec_t > > *' at 0x10c8cda50> >> swig/python detected a memory leak of type 'std::pair< bool,std::pair< >> int,coot::atom_spec_t > > *', no destructor found. >> > >You understand that Python is not my preferred language, so I don't use >it much. Now you are poking at the limits of my understanding. This >does look bad though. I'll take a look - it might be a SWIG (version) >problem. > >Paul.
