Ron, > I'm not sure I fully understand your suggestion. It sounds to me > like what you're saying is that I should add code (e.g. a dictionary) > to the importing.py load() function which saves the file information > of objects as they're loaded. But then instead of just distributing > my plugin, I would have to get users to change their PyMOL source, as > well (which I'm not willing to do). Am I understanding correctly?
Well, I may have been misunderstanding you...I'd though you mentioned you were using a gui to load the pdb files, which would be the natural place to add additional code. I'd assumed the gui you were talking about was specific to your plugin (if this isn't the case, then my suggestion doesn't help that much). > Any other ways around this problem? You could try turning on logging, and scan through the logfile looking for load events (on my system, using the standard gui menus to open a pdb, this stores the full path to the input pdb file; although it does not associate it with the object name). Of course then you're stuck with the problem of getting the name/path of the logfile... Good luck, Pete Pete Meyer Fu Lab BMCB grad student Cornell University
