Opened 11 years ago
Closed 10 years ago
#36 closed defect (wontfix)
Table Viewer Master Ticket
Reported by: | Scooter Morris | Owned by: | Conrad Huang |
---|---|---|---|
Priority: | blocker | Milestone: | Initial Tools |
Component: | Core | Version: | |
Keywords: | Cc: | chimera-programmers | |
Blocked By: | Blocking: | ||
Notify when closed: | Platform: | all | |
Project: | chimera |
Description
Change History (7)
comment:1 by , 11 years ago
comment:2 by , 11 years ago
…and I think that when setting a per-coordset attribute there has to be some means of setting it in all coord sets at once or in some arbitrary coord set -- so that you don't have to make each coord set current in order to set an attribute in it.
comment:3 by , 11 years ago
The last ugly detail is that some attributes are per-altoc (bfactor, occupancy). I got nothing.
comment:4 by , 11 years ago
Urg, all these comments should have gone into the Table Data ticket (#28). Sigh.
comment:6 by , 11 years ago
Hmm, the row-index-includes-altloc idea is problematic because all attrs then become per-altloc attrs, so for instance setting the charge for an atom that has altlocs will only set it for one of the altlocs.
comment:7 by , 10 years ago
Component: | Table Viewer → Core |
---|---|
Resolution: | → wontfix |
Status: | new → closed |
The other wrinkle here is that some attributes are per-coordset, and therefore those attributes have to have an additional dimension and be indexed not only by row but by current coordinate set. There also has to be a mechanism for ordaining some attributes as per-coordset, presumably during attribute registration.