Hi Oliver,

Yep, that is odd, and I think I know this bug. It is because status messages in ChimeraX cause extra events to be processed. As you adjust the contour level with the mouse, some status messages appear about recontouring the map, and during those status messages, new mouse motions are detected that cause new adjustments, and eventually when you release some old queued mouse event gets processed and causes it to jump to a different contour level. It may seem baffling that this does not happen at step 2 — that is because when contouring smaller regions it emits no status messages.

Unfortunately this is a problem with the Qt window toolkit we use — there seems to be no easy way to provide a status message without having inadvertent event processing. We have some extremely difficult solutions for this (e.g. making an OpenGL status line) that we have not had time to implement. It may be many months before this is fixed.

If you can’t find a way to change your mouse drag (pause before release?) to get around this, you could edit the “min_status_message_voxels” value in the Python code (chimera/libs/python3.6/site-packages/chimerax/core/map/volume.py) to use a very large value so contouring status messages are not shown — the current limit is 16 million voxels.

Tom

On Jun 2, 2017, at 12:27 AM, Oliver Clarke olibclarke@gmail.com wrote:

Hi,

Using the right mouse button to adjust map contour works very well at volume step 2, but displays odd behavior at step 1.

This may of course be a slow computer issue (MacBook pro 2015 13”, integrated graphics), but figured I’d report it in any case.

Specifically what happens, is as I right click drag, the map contour appears to adjust correctly, but then when I release the mouse button, the map jerks back to a very low contour.

Cheers Oli _______________________________________________ ChimeraX-users mailing list ChimeraX-users@cgl.ucsf.edu Manage subscription: http://www.rbvi.ucsf.edu/mailman/listinfo/chimerax-users