![[ChimeraX Issue Tracking System]](/trac/ChimeraX/chrome/site/ChimeraX-icon.svg){kind=icon}
Opened 8 years ago
Closed 7 years ago
#775 closed defect (fixed)
add matrix/place attr to C++ Structure
| Reported by: | pett | Owned by: | pett |
|---|---|---|---|
| Priority: | major | Milestone: | |
| Component: | Core | Version: | |
| Keywords: | Cc: | Tom Goddard | |
| Blocked By: | Blocking: | ||
| Notify when closed: | Platform: | all | |
| Project: | ChimeraX |
Description
...to make it easy to get the transformed coordinates, and to get a 'transformation changed' trigger/reason into the atomic changes trigger.
Change History (3)
comment:1 by , 8 years ago
comment:2 by , 7 years ago
| Cc: | added |
|---|---|
| Owner: | changed from to |
Eric added a C++ Structure scene position matrix.
comment:3 by , 7 years ago
| Resolution: | → fixed |
|---|---|
| Status: | assigned → closed |
Note:
See TracTickets
for help on using tickets.
Think this should be done after alpha2 release.
Need to think about how we intend "graphical copies" (ie instances) to be used for structures. Right now the sym command makes graphical copies of a structure. If I make trimer from a monomer using 3 graphical copies what does the transform of the Structure mean? I guess it would be the first copy. But if we go this route it probably rules out doing any computation using the atom coordinates of the other two copies (e.g. clashes). Probably that is ok, and we should limit "graphical copies" to viewing and not measuring operations.