Yes, this is to be categorized as a bug. All ITK-based objects should call Modified() in their setter methods, if the values actually changed.
- Queries
- All Stories
- Search
- Advanced Search
- Transactions
- Transaction Logs
Advanced Search
Yesterday
Wed, Mar 20
Tue, Mar 19
Thu, Mar 14
Mon, Mar 11
I would change the checklist. With the multilabel support it makes sense to keep it open, if you have confirmed an interpolation, because you might directly go to the next label and confirm there as well...
Wed, Mar 6
More context:
- There's already MITK_CUSTOM_REVISION_DESC, which allows to change the tag/commit hash that is displayed in the Workbench as version like "v2023.12" and I think also in the package names generated by CPack.
- Exclusion/visibility of views, toolbars, and perspectives will be part of our customization efforts for the upcoming release and is scheduled to be implemented in March.
- Toolbar visibility is already implemented (just recently) as preferences.
Mon, Mar 4
Sun, Mar 3
Feb 28 2024
Feb 27 2024
@s434n What is your concrete proposal/idea here?
Feb 26 2024
Feb 23 2024
Feb 21 2024
I am also in favor of option 3.
Feb 9 2024
I also vote for 3.
Feb 8 2024
Feb 7 2024
Has been clarified
Feb 1 2024
Reason: see my comment above.
Jan 24 2024
Jan 23 2024
Jan 18 2024
Jan 10 2024
@fedorov I added you to "warn" 😉 you, that will join the effort. Great idea!
Jan 5 2024
Dec 5 2023
Hi there! 🙂
Hi there! 🙂
Hi there! 🙂
Hi there! 🙂
Hi there! 🙂
Dec 4 2023
@gaoh PLease feel free to reopen if there is still a problem.
Nov 29 2023
Nov 28 2023
Nov 22 2023
MITK Workbench XL
MITK Workbench - extra
Some more name ideas:
MITK Workbench Plus
MITK Workbench - Advanced Edition
MITK Workbench - Extended Edition
MITK Deluxe (ok, too far, I'll better stop now...)
Name suggestion: MITK Workbench - Science Edition
Nov 21 2023
Nov 20 2023
Thats because 3D Tools in total do not support undo redo currently.
Sofar we havent dared due to the memory footprint (as it would mean storing copies of the volume); but also never tested it.
May be we should ceck if it is OK in conjunction with compression (introduced by @kislinsk some time ago) and if needed limitations (a max step limit, or clearing the history if the segmentation is finished), to avoid extrem memory consumption due to long undo/redo history.
Nov 9 2023
New checkbox "Allow all models" added to Preferences. Changes included in D875
Nov 7 2023
I would lean to adding a preference "allow unsupported models" (default ==false). If people activate it, they can see all models (that are not blacklisted) and not just the white listed (verified) once.
If the risk is communicated and users are willing to take it, then I would not actively prevent people from using models (as long as they don't crash MITK or so).