Qt5 build : a few hiccups


(SET) #21


In ‘Filtering/Threshold scalar volume’ module : If ‘Threshold Type’ is set to ‘Below’, Slicer crashes when the ‘Apply’ button is clicked.

(Davide Punzo) #22

ah ok, I thought you meant the threshold segmentation editor effect. At the moment I don’t have the filters in my build so I can’t check/fix.

asap I’ll try to fix the other one:

It will also be nice to report all these in an ordered manner in the mantis bug tracker

(Davide Punzo) #23

reported in:

and for reference:


(Andras Lasso) #24

I’ve noticed that with the new OpenGL2 backend/VTK9/Qt5, slice browsing speed can be much slower: it is always at least 20% slower than using OpenGL backend/VTK7.1/Qt4, but sometimes it is 5-10FPS instead of the normal 50FPS. It seems to be related to how many synchronous OpenGL calls are used and if NVidia threaded optimization is enabled. I’ve added a ticket to track this issue: https://issues.slicer.org/view.php?id=4496.

(SET) #26

I could not reproduce it in the 20180116 build where there are no errors.
A build from 20180107 gives the following errors with all default values :

Threshold Scalar Volume standard error:

PARSE ERROR: Argument: (–thresholdtype)
Value ‘&Below’ does not meet constraint: Below|Above|Outside

Brief USAGE:

For complete USAGE and HELP type:
/home/user/programs/Slicer-4.9.0-2018-01-07-linux-amd64/lib/Slicer-4.9/cli-modules/ThresholdScalarVolume --help

I probably noticed that in an older build and its has since been fixed by the many recent changes.

(Andras Lasso) #27

This seems to be the same bug as the extra & characters appearing in the GUI, which is most likely caused by this extremely ugly KDE bug (which is intended to be a feature and it seems it has not been removed yet). In the bug report there are many links to duplicate reports, with lots of additional information.

Probably the same bug causes the duplication of tools in the toolbar.

(Andras Lasso) #28

I’ve implemented a fix for Threshold volume and duplicated mouse mode icons issues. The fixes do not address the issue of KDE altering text in the application, just changes Slicer to not rely on exact GUI text match in these specific cases. The KDE bug may cause other issues, so we should keep in mind that it is always a possible root cause for errors.

(Jean Christophe Fillion Robin) #29

2 posts were split to a new topic: Support --designer launcher argument for Qt5 build