Page MenuHomePhabricator
Create Task
Maniphest T17784

About the maus Event for Ashvins 3D and the example QtFreeRender
Closed, WontfixPublic
Actions

Description

Hello All,

The mause Event for our product Ashvins 3D does not work any more after using the MITK Version (2013.09). We used the Version 2012 before.

I have also tested the No-Qt-example demo "QtFreeRender". It does not work either for the versio n2013.09 and the new Version 2014.03.

After searching a solution in Internet, I found an old discuss(from 2012) about this issue. The following is my try:

There are two Problems,
-->The 2D Viewer behaviors like a 3D Viewer, so is the maus event.

  1. I try to use ForeceImmediateUpdateAll() to reset the camera. The Problem of the 2D Viewer behaviour is solved. It is now like 2D Viewer. But the whole mouse Events do not work any more.
  1. I also use the ReinitEventProvider() after ForceImmediateUpdateAll() to reactivate the mouse Event. But it still does not work.

Maybe this is not a right try. Is there any solution for this issue so that we can solve our Problem of the 3D mouse Event.

Thanks a lot in advance for your help.

Best Regards,

Mei-Chuan Chen (From Medical communications GmbH)

ps. 1) For reply, please mail to MChen@medicalcommunications.com

  1. About this problem, my kolleague(Mr.Christian Schwarz) has already asked and got an answer from Mr.Markus Engel. But all related mails got lost after the PC crashed. Therefore I Need to reopen this issue. Sorry for that and thanks a lot for your patience

Related Objects

Event Timeline

bartels added projects: MITK, Bugzilla.May 9 2014, 5:40 PM
• webechr added a subscriber: • webechr.May 21 2014, 5:27 PM

Hi,

i looked into this today, and there several issues:

  1. call of PrepareRender() on the render windows was missing, this caused them to remain in 3D mode even though 2D has been set
  2. within mapping of mouse move events there was a bug, caused falsely set up mouse move events
  3. the request update had to be changed to a fore immediate update,

this is now all fixed in the branch that will be pushed, and will be integrated shortly.

• git-user added a subscriber: • git-user.May 21 2014, 5:34 PM

User webechr has pushed new remote branch:

bug-17784-FixQtFreeInteraction
bartels added a subscriber: bartels.May 22 2014, 12:14 PM

(In reply to Christian Weber from comment #1)

Hi,

i looked into this today, and there several issues:

  1. call of PrepareRender() on the render windows was missing, this caused

them to remain in 3D mode even though 2D has been set

  1. within mapping of mouse move events there was a bug, caused falsely set

up mouse move events

  1. the request update had to be changed to a fore immediate update,

this is now all fixed in the branch that will be pushed, and will be
integrated shortly.

Hi Christian,

thanks a lot for the answer.
I tested it. But the action of the crosshair line is deactivated. It is shown only with the white Color and it will not interact with the 3D view and other 2D views. That means, I can not move the crosshair with left-mouse button.

Best Regards,

Mei

bartels added a comment.May 22 2014, 12:34 PM

Hi Christian,

actually only zooming with the right mouse and Scrolling through the slices work.

Thanks a lot

Mei

zelzer added a subscriber: zelzer.May 23 2014, 11:17 AM

@Christian Can we use the new interaction test framework for creating unit tests of the interactions in the 2D/3D windows to reproduce the issues in the QtFreeRender example?

• git-user added a comment.Jul 9 2014, 4:34 PM

User webechr has pushed new remote branch:

bug-17784-FixQtFreeInteraction-Int
• webechr added a comment.Jul 9 2014, 5:20 PM

Crosshair Problems seems to be related to work on this T16681 ,
I'll look into this more .

bartels added a comment.Jul 14 2014, 5:59 PM

Hi Christian,

Thanks a lot for having a look at this issue.
I have already solved this Problem by myself. The example QtFreeRender works again including crosshair positioning and moving. I can use the mouse Event for no-Qt UI.

Best Regards,

Mei

zelzer added a comment.Jul 28 2014, 1:58 PM

@Christian is this still relevant? Do you have an idea why forcing the update is not necessary in the Qt case?

• fetzer added a subscriber: • fetzer.Oct 6 2014, 2:29 PM

Updating target milestone to upcoming release

• git-user added a comment.Oct 15 2014, 5:03 PM

User webechr has pushed new remote branch:

bug-17784-FixQtFreeInteraction-Int-Oct-2014
• webechr added a comment.Oct 22 2014, 4:17 PM

Involves forcing some Rendering-Updates in Core classes,
needs a more thourough adressing. pushing this back after the release.

• git-user added a comment.Jan 28 2015, 2:24 PM

User webechr has pushed new remote branch:

bug-17784-FixQtFreeInteraction-Int-Jan-2015-28
kislinsk edited projects, added MITK (2016-11); removed MITK.Aug 1 2016, 10:48 PM
kislinsk closed this task as Wontfix.Oct 28 2016, 10:01 AM
kislinsk claimed this task.
kislinsk added a subscriber: kislinsk.

As nothing happened the last 1,5 years here and Christian left the department, I'll close this one for now.

kislinsk reopened this task as Open.Jun 27 2018, 1:04 PM
kislinsk removed kislinsk as the assignee of this task.
kislinsk added a project: Bulk Edit.
kislinsk closed this task as Wontfix.Jun 27 2018, 1:09 PM
kislinsk removed a project: Bulk Edit.
kislinsk mentioned this in T27033: Clean up stale remote branches.Jan 25 2020, 9:01 PM
MITK · MIC · IMSY · DKFZ