Pushed new branch to rMITK MITK: bugfix/T30213-PocoOpenSSL.
- Queries
- All Stories
- Search
- Advanced Search
- Transactions
- Transaction Logs
All Stories
Today
Yesterday
I think in doubt I would just move but not merge it for now. If we see that it is needed or wanted we can make the effort and merge it. It would be better than not offering this feature at all.
The dicom inspector has one additional dependency to module MITKDICOM. Therefore if we merge the inspector plugins also our normal inspector could only be build if DICOM module is activated. (Which it currently is per default).
Tue, Sep 26
In fact, this problem occurs not just for the progress bar, but the progress itself, e.g. also in the info box 1 is currently never reached even if the descriptive parameter calculation process is finished. The reason for this bug is that the progress is stored in a member variable which is updated after the progress event is invoked. Therefore, the progress variable is always lagging one update behind. This is fixed by changing the order of the called functions.
The fix is done for the descriptive parameter calculation, but also for the pixel and ROI-wise fitting.
Wed, Sep 20
Discussion result: Use permissive mode always switched on. No preferences needed.
Discussion result: Feature is useful but not as plugin on its own but instead as part of the statistics plugin (as an additional button like copy to clipboard).
Integrate into F1 help. Make MITK ModelFit Webpage deprecated for manual section with link to doxygen documentation.
It is a useful feature and should be part of the next release.
Tue, Sep 19
In T30186#253599, @kislinsk wrote:Is there some additional functionality involved or could we just add it as another MIME type for images instead of a dedicated plugin?
Yes there is. As only (potentially) the pixel values of image parts with an mask should be exported. And you can select multiple image (as long as they have the same geometry), there pixel values will be exported into the same table.
Fri, Sep 15
Mon, Sep 11
Fri, Sep 8
@full Is this still an issue (with the current release)?