We think that people in the real world do not use the smoothing options at all and checking for their impact revealed that they seem to have no effect at all in most cases. We decided to remove the options from the preferences. In addition, there's a message in the terminal when no smoothed mesh could be created which is the case for some single-slice segmentations. It even suggests to try again without smoothing. However, this should probably be a more prominent feedback as message box for example.
- Queries
- All Stories
- Search
- Advanced Search
- Transactions
- Transaction Logs
Advanced Search
Oct 13 2022
We should double-check if there's really a bug as there's a good chance that it was just misunderstood how it works. Everything that's not covered by the level window is supposed to be transparent. We should probably improve the checklist to be more clear.
Oct 12 2022
In T29338#242672, @floca wrote:One question. The current implementation has always standard suggestions and the custom suggestions are added. I am wondering it wouldn't be better if in case of custom suggestions are given, only the custom suggestions appear.
E.g. with the current logic we would be able to allow people define a study that only contain special custom suggestions and not the standard ones, would we?
Pushed new branch to rMITK MITK: bugfix/T29338-RenameLabelWindowImprovements.
Oct 11 2022
Deleted branch from rMITK MITK: bugfix/T29332-QtWebEngineIssuesOnLinux.
Pushed new branch to rMITK MITK: bugfix/T29332-QtWebEngineIssuesOnLinux.
Oct 10 2022
The last part with the high physical memory however *is* an issue. I reopen and rename this task.
This is as expected, since we are not an officially proven developer by Apple.
We may even be able to do it in code, according to the Qt documentation: QTWEBENGINE_CHROMIUM_FLAGS can also be set using {qputenv} from within the application if called before QtWebEngineQuick::initialize().
QTWEBENGINE_DISABLE_SANDBOX=1 is equal to QTWEBENGINE_CHROMIUM_FLAGS="--no-sandbox". While trying to debug the issue, I noticed that the following workaround to have the WebEngine renderer and plugins in the same process as the browser works as well: QTWEBENGINE_CHROMIUM_FLAGS="--single-process". It is and sounds less scary compared to disabling the sandbox. As a fix, we could change our start shell scripts on Linux to set the environment variable for the call of the application.
Deleted branch from rMITK MITK: bugfix/T29339-F1ContextHelpViewNavigator.
Pushed new branch to rMITK MITK: bugfix/T29339-F1ContextHelpViewNavigator.
Oct 8 2022
Deleted branch from rMITK MITK: bugfix/T29334-ImproveSurfaceVtkWriterTest.
Pushed new branch to rMITK MITK: bugfix/T29334-ImproveSurfaceVtkWriterTest.
Oct 7 2022
Deleted branch from rMITK MITK: bugfix/T29334-MakeSceneSavingAndLoadingMoreRobust.
Pushed new branch to rMITK MITK: bugfix/T29334-MakeSceneSavingAndLoadingMoreRobust.
Oct 6 2022
Deleted branch from rMITK MITK: release/T29327-2022-Week-40.
Pushed new branch to rMITK MITK: release/T29327-2022-Week-40.
Oct 5 2022
Squashed into develop branch with co-authorship of @j762e, @kalali, and @floca: rMITK3dd8c7b5be73: Add GrowCut segmentation tool
Deleted branch from rMITK MITK: feature/T28851-AddITKGrowCutTool.
Oct 4 2022
Deleted branch from rMITK MITK: bugfix/T29318-DeleteObsoleteResources.
Pushed new branch to rMITK MITK: bugfix/T29318-DeleteObsoleteResources.
Deleted branch from rMITK MITK: bugfix/T29318-SegmentationToolIconsAndCursors.
Pushed new branch to rMITK MITK: bugfix/T29318-SegmentationToolIconsAndCursors.
Sep 28 2022
Here's the first batch of clean-up action. Needs to be continued!
In T24398#241998, @floca wrote:Our side or also the CTK part.
Hm, lets put it as known issue and discuss its priority when we plan the spring release.
Sep 27 2022
I looked into the dicombrowser plugin and found out that the directory on Windows is something like %APPDATA%/../Local/Temp/TmpDicomFolder.************. However I didn't see pop up any files after retrieve.
Sep 23 2022
I just tried to retrieve data from dicomserver.co.uk and I am able to query and kind of retrieve data. A repeated retrieve even tells me that existing files are overriden. At least that is what the console output tells me. But where are the retrieved images supposed to be stored? And shouldn't the retrieved images appear somewhere in the DICOM editor?