id	summary	reporter	owner	description	type	status	priority	milestone	component	version	resolution	keywords	cc	blockedby	blocking	notify_on_close	platform	project
680	Make deleting Model or Drawing notify parent.	tic20@…	Tom Goddard	"Want to be able to use

  m.delete()

instead of

  session.models.remove([m])

and for Drawing

  d.delete()

instead of

  parent.remove_drawings([d])


Begin forwarded message:

From: Tristan Croll 
Subject: Re: Pseudobonds question (and crash)
Date: May 18, 2017 at 11:23:18 AM PDT
To: Tom Goddard 

...

Another issue I ran into today: if I've created a Drawing (call it d) and added it to a Model, then running:

d.delete()

does Very Bad Things(TM) (the drawing loop crashes). The immediate cause is fairly straightforward (the Drawing object tries to measure the length of a variable that's been set to None). If I run delete() on a Model object, the entry remains in the Model panel.

I'm not sure if delete() was meant to be used this way, but it's what seemed the intuitive thing to me. Perhaps it would be better if delete() was a a synonym for chimerax.core.commands.close(session, self) and the current delete() turned into a hidden method?



Tristan Croll
Research Fellow
Cambridge Institute for Medical Research
University of Cambridge CB2 0XY
"	enhancement	assigned	major		Core								all	ChimeraX