<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2//EN">
<HTML>
<HEAD>
<META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=iso-8859-1">
<META NAME="Generator" CONTENT="MS Exchange Server version 6.5.7653.38">
<TITLE>RE: [Chimera-users] suggested feature/model panel</TITLE>
</HEAD>
<BODY>
<!-- Converted from text/plain format -->
<P><FONT SIZE=2>Hi Eric,<BR>
<BR>
You are correct about #2 & #3, there would be an ambiguity in the design & coding.<BR>
<BR>
what I would propose:<BR>
If a folder shuts off (hide), all multiple instantiations would be turned off.<BR>
If a folder turns on (show), it only turns the model on in that folder.<BR>
If a protein were in to two folders, it would require a third checkbox option of mixed, along with show & hide states.<BR>
definitely needs more analysis. Initially I would prefer #2 over #3<BR>
<BR>
<BR>
as for the motivation: each folder would represent a scenario, easy switching between scenes, improved convenience in working with dozens or hundreds of models.<BR>
<BR>
<BR>
<BR>
<BR>
> 1) ability to create folders in the model panel so models can be grouped<BR>
> 2) ability to have a model in multiple folders<BR>
> 3) ability to show/hide in a folder by a a single checkbox<BR>
> 4) ability to name the folder<BR>
<BR>
<BR>
I think #2 and #3 are in conflict though. Really, I don't think you <BR>
want #2 -- it's too confusing. Say a model is in two groups: you <BR>
close one group -- what happens? You hide one group -- what happens? <BR>
You deactivate one group and move the other -- what happens? Perhaps <BR>
if you elaborated on the motivation for putting a model in multiple <BR>
groups then some other alternative could be devised that provides what <BR>
you need.</FONT>
</P>
</BODY>
</HTML>