View Issue Details

IDProjectCategoryView StatusLast Update
0003346Slicer4Core: GUIpublic2018-03-16 09:27
ReportermillerjvAssigned Tojcfr 
PrioritynormalSeverityminorReproducibilityalways
Status assignedResolutionopen 
Product VersionSlicer 4.2.2-1 
Target VersionbacklogFixed in Version 
Summary0003346: Slice offset slider widget offset (ctkSliderWidget)
Description

Volume with origin (0, 0, 0) and spacing (1, 1, 66.7) with 20 slices.

Slider on the axial viewer is wider than can be reached by using the arrow keys or the mouse wheel, i.e. the slider shows that it covers more slices than span of the data.

If you use the mouse to move the slider, you can reach this area of the slider that is not accessible by the arrow keys or mouse wheel. But when you do this, the range of the slider changes such that the slide not longer shows real slice locations but instead shows interpolated images.

Additional Information

This can be reproduced (somewhat) by creating a ctkSliderWidget and setting maximum to 1267.3. If you then move the slider, the maximum shown is 1267. If you hit the up button, it will go to 1267.3.

TagsNo tags attached.

Activities

millerjv

millerjv

2013-08-29 11:29

developer   ~0009704

Last edited: 2013-08-29 11:29

We should consider giving the user an indication that they are viewing interpolated slices instead of real slices. Steve recommended changing the shape of the slider control knob (to a diamond) when interpolated slices are being displayed. Also, we could change the color of the slider control knob.

millerjv

millerjv

2013-08-29 11:35

developer   ~0009705

Steve and I think it is caused by line 260 in ctkSliderWidget.cxx

// SpinBox can truncate the range (depending on decimals).
// use Spinbox's range to set Slider's range
d->Slider->setRange(d->SpinBox->minimum(), d->SpinBox->maximum());

The SpinBox is being set with the correct maximum value but it truncates/rounds the value and then uses this truncated/rounded value in the slider.

The MoveSlice()/IncrementSlice()/DecrementSlice() methods from the interactor clamp to the true range of the data, not to the range of the spinbox.

millerjv

millerjv

2013-08-29 11:40

developer   ~0009706

Reminder sent to: pieper

Bug writeup of what we discussed with the slice offset slider.

Add to it anything I left off.

Jim

jcfr

jcfr

2014-03-07 11:55

administrator   ~0011389

Proposed solution: Snap the slider value back to the closet integer range.

jcfr

jcfr

2015-11-02 09:30

administrator   ~0013489

See https://github.com/commontk/CTK/issues/570

lassoan

lassoan

2018-03-16 09:27

developer   ~0015572

This causes unexpected behavior in Segment Editor: when at slice boundary, drawing tools may appear not to work - https://discourse.slicer.org/t/sometimes-freehand-drawing-does-not-work-in-segment-editor/2271/9

Issue History

Date Modified Username Field Change
2013-08-29 11:27 millerjv New Issue
2013-08-29 11:27 millerjv Status new => assigned
2013-08-29 11:27 millerjv Assigned To => kikinis
2013-08-29 11:29 millerjv Note Added: 0009704
2013-08-29 11:29 millerjv Note Edited: 0009704
2013-08-29 11:30 millerjv Assigned To kikinis => finetjul
2013-08-29 11:35 millerjv Note Added: 0009705
2013-08-29 11:40 millerjv Note Added: 0009706
2013-08-29 11:50 finetjul Assigned To finetjul => jcfr
2013-09-03 06:14 jcfr Target Version => Slicer 4.3.1
2013-10-01 12:08 jcfr Target Version Slicer 4.3.1 => Slicer 4.3.2
2014-03-06 10:15 nicole Target Version Slicer 4.3.2 => Slicer 4.4.0
2014-03-07 11:55 jcfr Note Added: 0011389
2014-07-29 10:09 jcfr Target Version Slicer 4.4.0 => Slicer 4.5.0-1
2015-11-02 09:29 jcfr Target Version Slicer 4.5.0-1 => Slicer 4.5.1
2015-11-02 09:30 jcfr Note Added: 0013489
2016-10-12 02:30 jcfr Target Version Slicer 4.5.1 => Slicer 4.7.0
2017-09-27 15:07 lassoan Target Version Slicer 4.7.0 => backlog
2018-03-16 09:27 lassoan Note Added: 0015572