I like Rolf's proposed solution very much, for the reasons he states. (Thanks, Rolf, for thinking creatively!)
Bob, what do you think about it? This came up because when one writes simplified user interfaces to Jmol (as Eran Hodis is doing in Proteopedia), one wants to give the best reasonable result to a command like "select 10-20" without complicated explanations and requiring users to look up which residues lack coordinates. Sure, we can write code in Proteopedia to change the command to ">=/<=", but it seemed to me that this issue deserves to be handled better in Jmol itself. Again, Rolf's idea seems to me to fill the bill. -Eric >What do you think about the following solution: > >Only if one of the border residues is not present, the ">=/<=" >selection mechanism is used instead. This would mean that nothing >would change with respect to numbering irregularities if one makes >sure that the border residues of a range are present. This is >currently already necessary in order to get a correct range selection. >If one of the border residues is not present, the selection is >currently not as desired in any case (nothing is selected). But by >using the other mechanism in these cases the selection would be >probably in >=95 percent as desired. So the overall failure rate would >be reduced. And the failure rate for cases with numbering >irregularities would not be increased. Only the type of the failure >would change. > >Regards, >Rolf ------------------------------------------------------------------------- This SF.net email is sponsored by the 2008 JavaOne(SM) Conference Don't miss this year's exciting event. There's still time to save $100. Use priority code J8TL2D2. http://ad.doubleclick.net/clk;198757673;13503038;p?http://java.sun.com/javaone _______________________________________________ Jmol-users mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/jmol-users
