From: Pawel Kedzierski (kedziers_at_ccmsi.us)
Date: Sat Aug 17 2002 - 11:36:24 CDT

On Thu, Aug 15, 2002 at 04:05:55PM -0500, Justin Gullingsrud wrote:
> Sounds like a cool app! Unfortunately, it looks like the only workaround
> I have at the moment for adding graphics data is to load a real molecule
> instead of a 'graphics' molecule. You could create a pdb file containing

  This does not work. The graphics.xxx() functions refuse to accept an id
  which is not of a 'graphics' type object. It looks like a dead-end
  -- it is no longer possible to create 'graphics' objects, but the
  Python interface refuses to work on anything else... Do You have
  another idea, what could I try?

  There is a molecule.import_graphics() function but the user guide
  suggests that it also do not create 'graphics' objects. The
  info, how to use it, is missing anyway -- what file types does it
  accept?

  What was really the reason behind disabling the old functionality
  of molecule.load('graphics', name)? Apart from it should not complain
  about nonexistant file, I was rather useful, as was the concept
  of 'graphics'-only objects. Oh well, maybe it would be more consistent
  to have graphics.create().

Greetings,

     Pawel Kedzierski

-- 
Pawel Kedzierski, kedziers_at_ccmsi.us
Chemistry/CREST, Jacson State University