Page MenuHomePhabricator

kalali (Amir Kalali)
Developer

Projects

User Details

User Since
Aug 1 2016, 12:10 PM (167 w, 6 d)

Recent Activity

Fri, Oct 18

kalali added a comment to T24757: Raw file downloads in CTest scripts don't work anymore with Phabricator URLs.

I just tried to use CTest with a branch. This is not working when I use set(GIT_BRANCH "Txxx"). I assume this is because this makes the script use the raw Phabricator file, which is not working, according to the task name.
However, since branches are not mirrored to GitHub, the proposed solution is not an option for me? Or is this not related?

Fri, Oct 18, 3:36 PM · Restricted Project, MITK
kalali triaged T26754: Review checklists as Low priority.
Fri, Oct 18, 3:21 PM · Restricted Project, MITK
kalali updated the task description for T26754: Review checklists.
Fri, Oct 18, 10:43 AM · Restricted Project, MITK

Tue, Oct 15

kalali committed rMITKd223e7267642: Merge branch 'T26727-Change-stdmultiwidget-dependent-files' into T24215-Remove… (authored by kalali).
Merge branch 'T26727-Change-stdmultiwidget-dependent-files' into T24215-Remove…
Tue, Oct 15, 4:50 PM
kalali committed rMITK2d8d2ca53254: Fix gcc errors (authored by kalali).
Fix gcc errors
Tue, Oct 15, 4:50 PM
kalali committed rMITK83fb64a3377d: Change custom viewer example plugin (authored by kalali).
Change custom viewer example plugin
Tue, Oct 15, 4:49 PM
kalali committed rMITK4db7d018bb9d: Change tutorial step8 (authored by kalali).
Change tutorial step8
Tue, Oct 15, 4:49 PM
kalali updated the task description for T26754: Review checklists.
Tue, Oct 15, 4:46 PM · Restricted Project, MITK
kalali updated subscribers of T26754: Review checklists.
Tue, Oct 15, 4:12 PM · Restricted Project, MITK
kalali created T26754: Review checklists.
Tue, Oct 15, 4:12 PM · Restricted Project, MITK
kalali added a comment to T26745: MITK's interaction not the first to handle events anymore -- QVTKOpenGLWidget::event() changed since VTK 7.0.0 (MITK 2016.11).

Actually, @hempe informed me that the render window menu is not flickering anymore in the latest stable release (if you mean with flickering: not being able to use the render window until you click inside the render window to set its focus).
I wanted to take a look into the diff this week.

Tue, Oct 15, 1:05 PM · MITK (2018-04-4), Pull Request

Mon, Oct 14

kalali updated the task description for T26741: Finishing new node selection concept.
Mon, Oct 14, 10:47 AM · Restricted Project
kalali added a parent task for T23751: Introduction of new selection concept: T26741: Finishing new node selection concept.
Mon, Oct 14, 10:43 AM · MITK
kalali added a subtask for T26741: Finishing new node selection concept: T23751: Introduction of new selection concept.
Mon, Oct 14, 10:43 AM · Restricted Project
kalali triaged T26741: Finishing new node selection concept as High priority.
Mon, Oct 14, 10:43 AM · Restricted Project

Tue, Oct 8

kalali added a comment to T26727: Change dependent files to work with the new concept.

Pushed new branch T26727-Change-stdmultiwidget-dependent-files.

Tue, Oct 8, 4:02 PM · Noteworthy, MITK

Mon, Oct 7

kalali triaged T26727: Change dependent files to work with the new concept as Normal priority.
Mon, Oct 7, 7:56 PM · Noteworthy, MITK

Fri, Oct 4

kalali added a project to T25930: [Segmentation] Fill/Erase crashes at non-zero timestep / Issue with ArbitraryTimeGeometry: Restricted Project.

Also if checking validity, consider T24766.

Fri, Oct 4, 11:07 AM · Restricted Project, MITK (2018-04-4)
kalali added a project to T25725: "Show in" action is currently not implemented: Restricted Project.
Fri, Oct 4, 10:22 AM · Restricted Project, MITK

Wed, Sep 25

kalali closed T26276: Segmentation created for multiple timepoints on 3D+t images as Resolved.
Wed, Sep 25, 3:46 PM · MITK (2018-04-4)
kalali closed T26276: Segmentation created for multiple timepoints on 3D+t images, a subtask of T24766: Last time step of 3D+t data with arbitrary time geometry not selectable by image navigator spinbox, as Resolved.
Wed, Sep 25, 3:46 PM · MITK
kalali closed T24766: Last time step of 3D+t data with arbitrary time geometry not selectable by image navigator spinbox as Resolved.
Wed, Sep 25, 3:42 PM · MITK

Mon, Sep 23

kalali added a project to T22838: Provide Jenkinsfile for CI: CI.
Mon, Sep 23, 3:16 PM · CI, Restricted Project, MITK
kalali added a project to T24536: Create "stupid" dart client: CI.
Mon, Sep 23, 3:15 PM · CI, MITK

Sep 13 2019

kalali committed rMITK1909c0b1d590: Fix for float / double level and window values (authored by kalali).
Fix for float / double level and window values
Sep 13 2019, 3:46 PM
kalali committed rMITKdcc1cbfeb418: Fix last time step access for data with arbitrary time geometry (authored by kalali).
Fix last time step access for data with arbitrary time geometry
Sep 13 2019, 1:13 PM

Sep 9 2019

kalali added a member for SIDT: j762e.
Sep 9 2019, 3:18 PM

Sep 3 2019

kalali added a comment to T19683: "Show only selected node" changes the visibility of crosshair.

I experienced a problem with that approach:
I have an image with many segmentation nodes as child nodes. If I want to hide all segmentation nodes except for one (using "show only selected node") it does not hide all other segmentation nodes because they are not on the first level.

Sep 3 2019, 6:48 PM · Bugzilla, Pull Request, MITK
kalali reopened T16153: Jump to center of mass of segmentation on click as "Open".

I'm currently using this inside the semantic relations plugin and I'm thinking about moving the functionality to the data manager context menu or similar.

Sep 3 2019, 12:36 PM · Request for Discussion, Bugzilla, MITK
kalali reopened T16153: Jump to center of mass of segmentation on click, a subtask of T15696: implement a multi-label segmentation functionality, as Open.
Sep 3 2019, 12:36 PM · Bugzilla, MITK

Sep 2 2019

kalali added a comment to T26496: [mxn multi widget] Re-initializations reset all render windows.
  • creating a new segmentation via the segmentation view

Has been disabled for the BlackSwan Demo. A "re-initialize selected nodes" button has been added, which will reinitialize the geometry of both selected nodes only inside the currently active render window.

Sep 2 2019, 5:17 PM · Restricted Project, MITK
kalali added a member for SIDT: graf.
Sep 2 2019, 3:57 PM

Aug 30 2019

kalali added a comment to T25583: Dynamically customize different context menus.

This is also necessary if a context menu action is defined within another plugin, which uses additional module-dependencies.

Aug 30 2019, 6:58 PM · MITK
kalali updated the task description for T26496: [mxn multi widget] Re-initializations reset all render windows.
Aug 30 2019, 4:42 PM · Restricted Project, MITK
kalali added a comment to T26276: Segmentation created for multiple timepoints on 3D+t images.

Will be solved if D214 is accepted and merged.

Aug 30 2019, 2:44 PM · MITK (2018-04-4)
kalali added a revision to T24766: Last time step of 3D+t data with arbitrary time geometry not selectable by image navigator spinbox: Unknown Object (Differential Revision).
Aug 30 2019, 2:39 PM · MITK
kalali added a comment to T24766: Last time step of 3D+t data with arbitrary time geometry not selectable by image navigator spinbox.

Pushed new branch T24766-Fix-last-time-step-access.

Aug 30 2019, 2:31 PM · MITK

Aug 27 2019

kalali added a comment to T25804: Set 'selected' property when using the new selection concept.

Another idea would be to use our QmitkSelectionServiceConnector to connect the service bus with a slot of the level window manager / level window widget, such that each selection is noticed by the level window slider and the context menu can access the currently selected data nodes.
I looked into the implementation and I think this is something we can do, given the code that we have.
However, I support the idea of rethinking and redesigning the level window manager (resp. level window widget). There are a lot of conditions and checks which make the class complex and error-prone.

Aug 27 2019, 6:40 PM · MITK
kalali added a comment to T25804: Set 'selected' property when using the new selection concept.

Pushed new branch T25804-Level-window-manager-as-selection-service-listener.

Aug 27 2019, 6:38 PM · MITK
kalali added a comment to T18403: Apply current shown level window setting to all selected images.

see T25483: different approach though: The idea is to change the level window slider while the "selected nodes" mode is enabled. This way, the level window will be applied to to all selected data nodes automatically and simultaneously.
The approach proposed here sounds more like using a node which has already a set LW and "propagating" this LW to different nodes (subsequently). I linked this task as we could discuss if this is something we want to have this feature additionally.

Aug 27 2019, 3:43 PM · Bugzilla, MITK

Aug 26 2019

kalali added a comment to T24356: Rework mouse mode switcher.

There are several things to point out here:

  • We could split the class into a real mouse mode switcher that only changes the mouse mode .xml-config file for a new mouse mode.

A new class has been introduced that handles all basic MITK- and PACS- interaction .xml-files in T24357.

Aug 26 2019, 3:41 PM · MITK
kalali added a comment to T24357: Rework mitkMouseModeSwitcher.

Has been solved on top of T26476.
This task will be closed if everything is merged to master and tested (wait for D212).

Aug 26 2019, 3:34 PM · MITK
kalali added a comment to T24357: Rework mitkMouseModeSwitcher.

Pushed new branch T24357-Remove-MouseModeSwitcher.

Aug 26 2019, 3:34 PM · MITK
kalali added a comment to T24357: Rework mitkMouseModeSwitcher.

A new class, the InteractionSchemeSwitcher has already been introduced in 9ab09bff137b. This class is used as a replacement for the MouseModeSwitcher. It it a simplified and cleaned version which reduces the responsibilities of the class: The service registration has been removed and is now done inside QmitkAbstractMultiWidget and DisplayActionEventBroadcast.
Additionally, the scheme switcher is adjusted to match the new scheme config files (see T24368): There is no difference anymore between a mouse mode and an interaction scheme (see T24368).
The new scheme switcher is used within the QmitkInteractionScheme and is currently tested with the QmitkAbstractMultiWidget.

Aug 26 2019, 1:53 PM · MITK
kalali added a comment to T24358: Rework QmitkMouseModeSwitcher.

Has been solved on top of T26476.
This task will be closed if everything is merged to master and tested (wait for D212).

Aug 26 2019, 12:45 PM · MITK
kalali added a comment to T24358: Rework QmitkMouseModeSwitcher.

Pushed new branch T24358-Remove-QmitkMouseModeSwitcher.

Aug 26 2019, 12:44 PM · MITK
kalali added a comment to T24358: Rework QmitkMouseModeSwitcher.

A new class, the QmitkInteractionSchemeToolBar has already been introduced in 9ab09bff137b. This class is used as a replacement for the QmitkMouseModeSwitcher. It it a simplified version which does not observe the mouse mode switcher / interaction scheme switcher. There is no observer tag and no block-functionality.
Additionally, the tool bar is adjusted to match the new InteractionSchemeSwitcher (see T24357): There is no difference anymore between a mouse mode and an interaction scheme (see T24368).
The new toolbar is used for the mxnmulwiwidgeteditor and is currently tested with the stdmultiwidgeteditor (see 732f754ad203).

Aug 26 2019, 12:39 PM · MITK
kalali closed T24368: Interaction scheme has different level of interaction, a subtask of T24356: Rework mouse mode switcher, as Resolved.
Aug 26 2019, 11:39 AM · MITK
kalali closed T24368: Interaction scheme has different level of interaction as Resolved.

Has been solved on top of T26476.

Aug 26 2019, 11:39 AM · MITK
kalali added a comment to T24368: Interaction scheme has different level of interaction.

Pushed new branch T24368-Adjust-display-config-files.

Aug 26 2019, 11:34 AM · MITK
kalali added a comment to T24368: Interaction scheme has different level of interaction.

I decided to go for having an own complete .xml-file for each mode, so I added the full definition for the different PACS modes.
The reason is that we want to have a consistent interaction scheme-handling which means either having full definition for both MITK and PACS modes or having base- and additional definition (like the original PACS modes). But changing the MITK configuration files to the base- and extra-mode variant requires event_variants to be empty in order to disable certain mouse events. Additionally any implementation needs to do two calls, one for setting the base-mode and one for adding the extra mode to make sure the correct base-mode is always set (e.g. switching from MITK to PACS). This was undesirable.

Aug 26 2019, 11:16 AM · MITK

Aug 23 2019

kalali closed T19643: Interaction problems occur between segmentation tools and renderwindow menu as Invalid.

I'm not sure if this is a valid issue.
I can reproduce the observable result if I don't disable the segmentation tool. I'm still in the drawing mode if the segmentation tool is enabled. If I change the display interaction mode now (by enabling Crosshair rotation (or any other mode - also No crosshair rotation), the MITK interaction scheme is enabled and both interactions happen at the same time (navigating and drawing).
Disabling and re-enabling the tool will again overwrite the navigation interaction and allow to draw the segmentation without any problems.

Aug 23 2019, 6:09 PM · MITK, Bugzilla
kalali closed T19118: Scroll mode in PACS like mouse interaction not re-enabled after using segmentation tool as Invalid.

I can not reproduce this.
After having deselected the Region Growing tool, I can use the left mouse button and move the mouse to scroll through the slices. "Normal" scrolling (does this mean scrolling using the mouse wheel?) does not work. Notice that you can always scroll by pressing the middle mouse and moving the mouse (regardless of the selected PACS mode).
However, in T26486 I changed the PACS mode such that you can always scroll through the slices using the mouse wheel (regardless of the selected PACS mode). The special PACS scroll mode still works for fast scrolling (left mouse button and mouse moving).

Aug 23 2019, 5:58 PM · Bugzilla, MITK
kalali closed T24635: PACS scroll leads to an infinite loop if no image is loaded as Resolved.

Has been solved on top of T26476.

Aug 23 2019, 5:39 PM · MITK
kalali added a comment to T24635: PACS scroll leads to an infinite loop if no image is loaded.

Pushed new branch T24635-Prevent-infinite-scroll-loop.

Aug 23 2019, 5:39 PM · MITK
kalali claimed T24635: PACS scroll leads to an infinite loop if no image is loaded.
Aug 23 2019, 5:16 PM · MITK
kalali closed T26486: PACS mouse mode does not allow scrolling with mouse wheel as Resolved.
Aug 23 2019, 5:10 PM · Restricted Project, MITK
kalali added a comment to T26486: PACS mouse mode does not allow scrolling with mouse wheel.

Pushed new branch T26486-PACS-mouse-mode-with-mouse-wheel-scrolling.

Aug 23 2019, 5:09 PM · Restricted Project, MITK
kalali closed T26642: [std / mxn multi widget] Restore original StdMultiWidget interactions as Resolved.
Aug 23 2019, 4:46 PM · Restricted Project, MITK
kalali added a comment to T26642: [std / mxn multi widget] Restore original StdMultiWidget interactions.

Pushed new branch T26642-Restore-original-interactions.

Aug 23 2019, 4:34 PM · Restricted Project, MITK
kalali added a parent task for T26642: [std / mxn multi widget] Restore original StdMultiWidget interactions: Unknown Object (Maniphest Task).
Aug 23 2019, 3:53 PM · Restricted Project, MITK
kalali triaged T26642: [std / mxn multi widget] Restore original StdMultiWidget interactions as Normal priority.
Aug 23 2019, 3:53 PM · Restricted Project, MITK

Aug 22 2019

kalali added a comment to T26486: PACS mouse mode does not allow scrolling with mouse wheel.

Combine with T24356 (esp. T24368).

Aug 22 2019, 5:50 PM · Restricted Project, MITK

Aug 16 2019

kalali added a comment to T24766: Last time step of 3D+t data with arbitrary time geometry not selectable by image navigator spinbox.

I think the problem is here: https://phabricator.mitk.org/source/mitk/browse/master/Modules/Core/src/DataManagement/mitkArbitraryTimeGeometry.cpp$124
The m_MaximumTimePoints for the 3D+t-Heart image is [103, 160, 160]. The last timePoint argument is 160. So in the first iteration if (timePoint < *pos) will be false. Next two iterations it will be false as well since 160 is not less than 160. This will lead to result being 0 at the end of the function.
Normally the m_MaximumTimePoints for another time-image is something like [41, 46, 51] and the timePoint argument will be 46 for the last timestep.
This could be solved by using something like this:

mitk::TimeStepType mitk::ArbitraryTimeGeometry::TimePointToTimeStep(TimePointType timePoint) const
{
  mitk::TimeStepType result = 0;
Aug 16 2019, 4:00 PM · MITK
kalali renamed T26633: [mxn multi widget] Show different time points of data from [mxn multi widget] Shof different time points of data to [mxn multi widget] Show different time points of data.
Aug 16 2019, 1:58 PM · Restricted Project, MITK
kalali added a project to T26633: [mxn multi widget] Show different time points of data: Restricted Project.
Aug 16 2019, 1:58 PM · Restricted Project, MITK
kalali triaged T26633: [mxn multi widget] Show different time points of data as Normal priority.
Aug 16 2019, 1:58 PM · Restricted Project, MITK
kalali added a comment to T25030: Image navigator time slider moves twice.

See T24766.
I also experienced the two-step when debugging but using only console-output this does not happen with other time-data than 3D+t-Heart.

Aug 16 2019, 1:41 PM · Restricted Project, MITK
kalali added a comment to T24766: Last time step of 3D+t data with arbitrary time geometry not selectable by image navigator spinbox.

This does not happen with the new mxn multi widget. Maybe connected to the render windows being synchronized / plane nodes when using the StdMultiWidget?

Aug 16 2019, 1:40 PM · MITK
kalali added a comment to T25930: [Segmentation] Fill/Erase crashes at non-zero timestep / Issue with ArbitraryTimeGeometry.

Is this still valid? I looked at it but couldn't reproduce the bug.
If you can reproduce it, could you try to reproduce it with Pic2DplusT and MITK-Data/3D+t-ITKIO-TestData as well?

Aug 16 2019, 12:36 PM · Restricted Project, MITK (2018-04-4)
kalali added a comment to T26276: Segmentation created for multiple timepoints on 3D+t images.

I created such a segmentation on the 3D+t-heart dataset and stored the segmentation as *.nrrd. The I loaded the *.nrrd-segmentation again and I now I can only see the segmentation on the first timestep.
Important: The timesteps of the *.nrrd-segmentation are now from 0 - 3 and with a duration of 1ms. The original 3D+t-Heart was [0,103] [103,160] [160, 160]. This was also true for the original segmentation. If I store the 3D+t-Heart image as *.nrrd and reopen it again the original timesteps are preserved.

Aug 16 2019, 12:19 PM · MITK (2018-04-4)
kalali updated subscribers of T18450: Inconsistent data selection between Measurement and Statistic.

Please talk to @kraeuter to as she is currently working on T26269

Aug 16 2019, 12:04 PM · Bugzilla, MITK
kalali added a comment to T26276: Segmentation created for multiple timepoints on 3D+t images.

I also tried it with MITK-Data/3D+t-ITKIO-TestData and everything works fine (segmentation and time-slider). However, a difference between all these time-images and the 3D+t-Heart// image is, that the Heart-image does not actually have a third timepoint, as the third timepoint is of length 0ms.
So maybe there is a problem with the matching of time points and the segmentation is displayed for the last time point, as the lats time point is actually non-existent and wraps around to the time point 0.

Aug 16 2019, 11:49 AM · MITK (2018-04-4)
kalali added a comment to T26276: Segmentation created for multiple timepoints on 3D+t images.

I just tried this and I can reproduce it with MITK-Data/3D+t-Heart. But when I used Pic2DplusT the segmentation was only created on a single timestep.
Additionally, when I clicked on the arrows of the time-slider of the image navigation plugin the time slider sometimes wraps around the last time step and returns to timestep 0. This was already mentioned here T25030. However, this does not happen If I use the Pic2DplusT image so maybe the 3D+t-Heart image is corrupt?

Aug 16 2019, 11:40 AM · MITK (2018-04-4)

Aug 13 2019

kalali added a revision to T24215: Refactor classes to use the QmitkAbstractMultiWidget(Editor): Unknown Object (Differential Revision).
Aug 13 2019, 3:06 PM · Noteworthy, MITK

Aug 12 2019

kalali closed T26495: [mxn multi widget] Not able to chose level-window presets as Resolved.
Aug 12 2019, 3:51 PM · Restricted Project, MITK
kalali added a comment to T26495: [mxn multi widget] Not able to chose level-window presets.

Level window widget has been added to both multi widget editors, presets work.
Using the context-menu of the level window slider the user can select the node he or she wants to modify. Using the multi-node selection approach from T25804 requires the selected-property to be set by the render window manager.
However, the multi-node-selection approach is included as the data manager is currently always available.

Aug 12 2019, 3:50 PM · Restricted Project, MITK
kalali added a comment to T26495: [mxn multi widget] Not able to chose level-window presets.

Pushed new branch T26495-Enable-level-window-slider-and-presets.

Aug 12 2019, 3:50 PM · Restricted Project, MITK
kalali added a comment to T25804: Set 'selected' property when using the new selection concept.

I came across this as I re-added the level window slider to the MxNMultiWidget (we didn't include this before as we used the PACS mode inside the MxNMultiWidget - which allows to change the level window via mouse moving). Now our user wants to use the level-window-presets available from the context menu of the level window slider.

Aug 12 2019, 3:25 PM · MITK
kalali added a comment to T25804: Set 'selected' property when using the new selection concept.

This would be necessary if we want to use the render window manager with the mxnmultiwidget and the mentioned task (T25483).

Aug 12 2019, 3:11 PM · MITK
kalali moved T26485: PACS mode is active while segmentation is drawn from Restricted Project Column to Restricted Project Column on the Restricted Project board.
Aug 12 2019, 1:52 PM · Restricted Project, MITK
kalali added a comment to T26485: PACS mode is active while segmentation is drawn.

For test purposes this has been solved for the segmentation module / plugin in 450d57dd of T24215.

Aug 12 2019, 1:51 PM · Restricted Project, MITK
kalali claimed T26485: PACS mode is active while segmentation is drawn.
Aug 12 2019, 1:15 PM · Restricted Project, MITK
kalali added a comment to T26485: PACS mode is active while segmentation is drawn.

Also when changing the interaction mode (PACS <-> MITK) while the segmentation tool (e.g. Add) is active, the changed interaction mode will overwrite the segmentation interaction and the render window changes again while drawing the segmentation.

Aug 12 2019, 1:14 PM · Restricted Project, MITK
kalali added a comment to T26485: PACS mode is active while segmentation is drawn.

There seems to be a problem with the mitkDisplayActionEventBroadcast-class in general. Some classes have legacy code that disables the default display interactor to load a scenario-specific state machine and config file (see e.g. https://phabricator.mitk.org/source/mitk/browse/master/Modules/Segmentation/Interactions/mitkTool.cpp$121).
This is done in other classes. The problem is that the function does not reset the display action event broadcast instance but only display interactor instances.

Aug 12 2019, 11:22 AM · Restricted Project, MITK

Aug 9 2019

kalali raised the priority of T24215: Refactor classes to use the QmitkAbstractMultiWidget(Editor) from Wishlist to Normal.
Aug 9 2019, 4:11 PM · Noteworthy, MITK
kalali closed T25605: New concept for changing the view direction of render windows, a subtask of T25603: Combine render window manager with custom multi widget, as Resolved.
Aug 9 2019, 4:00 PM · Restricted Project, MITK
kalali closed T25605: New concept for changing the view direction of render windows as Resolved.

The modified render window has been added and can be used by the StdMultiWidget and the MxNMulwiWidget (see T24215).
This is used here and a new entry for the render window menu has been added.

Aug 9 2019, 4:00 PM · Restricted Project, MITK
kalali added a comment to T25605: New concept for changing the view direction of render windows.

Pushed new branch T25605-View-direction-change-in-render-window-menu.

Aug 9 2019, 3:56 PM · Restricted Project, MITK

Aug 7 2019

kalali added a comment to T25595: Make classes work with the new render window access.

Pushed new branch T25595-New-render-window-access.

Aug 7 2019, 12:53 PM · Restricted Project, MITK
kalali updated the task description for T25595: Make classes work with the new render window access.
Aug 7 2019, 10:22 AM · Restricted Project, MITK
kalali renamed T25595: Make classes work with the new render window access from Make ImageNavigator work with the custom multi widget editor to Make classes work with the new render window access.
Aug 7 2019, 9:56 AM · Restricted Project, MITK
kalali updated the task description for T24211: Multi widget editor responsibilities.
Aug 7 2019, 9:46 AM · MITK
kalali added a comment to T24211: Multi widget editor responsibilities.

LayoutManager has been added in T24215.

Aug 7 2019, 9:45 AM · MITK

Aug 6 2019

kalali closed T26493: [mxn multi widget] Allow render window resizing as Resolved.

Render window menu is now available (T24215).
However, QSplitter were added to the MxNMultiWidget so that resizing via mouse-dragging is also possible.

Aug 6 2019, 7:00 PM · Restricted Project, MITK
kalali added a comment to T24215: Refactor classes to use the QmitkAbstractMultiWidget(Editor).

Pushed new branch T24215-Remove-stdmultiwidget-dependency.

Aug 6 2019, 6:59 PM · Noteworthy, MITK
kalali closed T24367: SetWidgetPlane-functions in QmitkStdMultiWidget not used, a subtask of T24356: Rework mouse mode switcher, as Resolved.
Aug 6 2019, 6:57 PM · MITK
kalali closed T24367: SetWidgetPlane-functions in QmitkStdMultiWidget not used as Resolved.

Functions have been removed in T24215.
Additional functions to be removed: see T26542

Aug 6 2019, 6:57 PM · Noteworthy, MITK
kalali updated the task description for T24215: Refactor classes to use the QmitkAbstractMultiWidget(Editor).
Aug 6 2019, 6:56 PM · Noteworthy, MITK
kalali claimed T24215: Refactor classes to use the QmitkAbstractMultiWidget(Editor).
Aug 6 2019, 6:53 PM · Noteworthy, MITK