Opened 6 years ago

Closed 6 years ago

#2213 closed defect (fixed)

Can't add volume threshold with context menu

Reported by: goddard@… Owned by: Tom Goddard
Priority: normal Milestone:
Component: Volume Data Version:
Keywords: Cc:
Blocked By: Blocking:
Notify when closed: Platform: all
Project: ChimeraX

Description 

The following bug report has been submitted:
Platform:        Darwin-18.6.0-x86_64-i386-64bit
ChimeraX Version: 0.91 (2019-07-11)
Description
Adding a new threshold using the context menu on multichannel volume data does not show the new vertical bar on the histogram, although the surface appears in the graphics.  Reported originally by Graham Johnson.

Log:
UCSF ChimeraX version: 0.91 (2019-07-11)  
© 2016-2019 Regents of the University of California. All rights reserved.  
How to cite UCSF ChimeraX  

> open /Users/goddard/ucsf/presentations/optical-
mar2019/data/AICS-10_136.ome.tiff

Summary of feedback from opening /Users/goddard/ucsf/presentations/optical-
mar2019/data/AICS-10_136.ome.tiff  
---  
notes | image name 3500000510_100X_20170131_E05_P03.czi #1, dimension order
XYCZT, grid spacing 0.1083, 0.1083, 0.29, grid size 512, 512, 42, times 1,
channels 9, value type uint16  
  
Opened multi-channel map AICS-10_136.ome.tiff, 9 channels, grid size
512,512,42, pixel 0.108,0.108,0.29, shown at step 1, values uint16  




OpenGL version: 4.1 ATI-2.9.26
OpenGL renderer: AMD Radeon Pro 580 OpenGL Engine
OpenGL vendor: ATI Technologies Inc.

Change History (2)

comment:1 by Tom Goddard, 6 years ago

Component: Unassigned → Volume Data
Owner: set to Tom Goddard
Platform: → all
Project: → ChimeraX
Status: new → assigned
Summary: ChimeraX bug report submission → Can't add volume threshold with context menu

comment:2 by Tom Goddard, 6 years ago

Resolution: → fixed
Status: assigned → closed

Fixed.

Problem was that creating volume surface for new threshold invoked a volume "color changed" trigger before the surface creation completed, and that reset the histogram markers to not include this surface.

This bug was introduced when changing the color handling of VolumeSurface.

Note: See TracTickets for help on using tickets.