Opened 2 years ago
Last modified 2 years ago
#9904 closed defect
Starting a segmentation in 3d then switching to orthoplanes causes transient rendering errors — at Version 1
| Reported by: | Zach Pearson | Owned by: | Zach Pearson |
|---|---|---|---|
| Priority: | high | Milestone: | 1.8 |
| Component: | DICOM | Version: | |
| Keywords: | Cc: | ||
| Blocked By: | Blocking: | ||
| Notify when closed: | Platform: | all | |
| Project: | ChimeraX |
Description (last modified by )
It used to give a traceback, but now when we switch from 3d back to orthoplanes the coronal plane will inevitably not be drawn, the axial plane will be too bright, and they will only go back to normal when the user mouses over them and forces a redraw from that interaction. Just finding the object representing the viewport in the shell and calling its redraw method for some reason doesn't work!
Change History (1)
comment:1 by , 2 years ago
| Description: | modified (diff) |
|---|---|
| Milestone: | → 1.8 |
| Summary: | Starting a segmentation in 3d then switching to orthoplanes gives traceback → Starting a segmentation in 3d then switching to orthoplanes causes transient rendering errors |
Note:
See TracTickets
for help on using tickets.