- User Since
- Aug 1 2016, 12:10 PM (269 w, 16 h)
Nov 4 2020
Dec 16 2019
FYI: VTK integrated this fix:
Nov 20 2019
Fix in https://github.com/MITK/MITK/pull/245, patches VTK
Nov 19 2019
Nov 13 2019
Nov 5 2019
Oct 16 2019
Ok, just created https://github.com/MITK/MITK/pull/240
Oct 15 2019
I tried the idea described above today and it fixes the behavior of my interactor that uses the mouse wheel in a 3D window. With this patch the MITK interactor gets to see the event first and can decide whether or not is is handled.
Oct 14 2019
Aug 28 2019
Jun 26 2019
Jun 6 2019
@kislinsk Thanks for your quick fix. I had a look into your changes, this looks very much like an overdue cleanup. Thanks again!
May 29 2019
May 28 2019
May 27 2019
I just looked into this again and provided a merge request (https://github.com/MITK/MITK/pull/233). This also merges into the current release/2018-xx branch
Apr 30 2019
(Didn't see latest comments from yesterday evening, was typing the following while only the initial comments of Stefan were visible in my browser)
Mar 29 2019
Mar 13 2019
Mar 12 2019
Jun 26 2018
I think your idea to add a short notice to Image Croppers UI would already help with the problem. An additional 'reinit' button could also help. However, I would argue against an 'enforced' reinit because this would come as a surprise to the user, potentially unnoticed (objects outside the image would just disappear making some users doubt their perception ;-)
Jun 25 2018
Thanks for looking into this. I just generated a non-axes-aligned image for testing:
Jun 12 2018
@thomass : thanks, that would be great! I just stumbled upon that but won't find the time to analyze the problem (plus the code was a bit lengthy and looked kind of redundant with the 3D mapper's code)
Jun 4 2018
May 16 2018
May 7 2018
Great news! Honestly I am surprised that everything just works fine (since nobody every tried this), but this is just very good news! Thank you!
Suggestion: use size_t instead which is used all over the standard library to denote memory sizes.
Plus: if you find the time, you could try to generate a random/fixed pattern image of 20GB and verify that MitkWorkbench is able to load _and_ display it. This might uncover a couple of related bugs - or just pass perfectly :-)
Apr 26 2018
Apr 24 2018
@goetzm: just out of curiosity: this looks like something where a bug + fix is available. Could you share why this is closed 'Wontfix'?
Apr 23 2018
Not sure if this was considered a feature (at least I am not aware of documentation): whitelisting modules changed, whitelisting plugins was added since 2016.11.
Mar 29 2018
@goch No, I did not test the script on other platforms than Windows yet. I am surprised to see differences here because I am not aware of modifications other than that caching mechanism that should be working independent of the operation system. If you go through the changes, you might look out to any regex expressions that might be Windows specific..
Mar 27 2018
Good to have your feedback and I am glad that this fix could be helpful for your build. However, I do not fully understand what kind of adaption you would need. Just in case that your problem is that fixup_bundle() clears its cache on each call: I think it should be safe to remove the call to get_prerequisites_clear_cache() in fixup_bundle(). In the latest version the cached result is stored under a name using all parameters passed to get_prerequisites. That should be stable even withour clearing the cache. If this is not sufficient, I am curious to see your use case
Mar 6 2018
Sep 18 2017
Sep 14 2017
Aug 30 2017
Aug 24 2017
Hey Daniel, no worries. It wasn't meant to be banned from MITK. I even had to remove my baby MITK Simulation to get things up and running
Code/Pull request available here: https://github.com/MITK/MITK/pull/209