Page MenuHomePhabricator
Create Task
Maniphest T13098

Measurement Tools produces 2 points on mouseclick
Closed, WontfixPublic
Actions

Description

Use "Line Path" or "Polgyon".

click and hold mouse button, move mouse, release mouse button.
This produces two points.

Especially annyoing when you draw a contour "quickly".

Event Timeline

graser added projects: MITK, Bugzilla.Sep 12 2012, 5:41 PM
• fetzer added a subscriber: • fetzer.Dec 18 2012, 3:58 PM

Updating target milestone to upcoming release

neher added a subscriber: neher.Apr 3 2013, 3:17 PM

To me this sounds like an awesome feature :)

graser added a subscriber: graser.Apr 24 2013, 2:16 PM

it's annoying, it's a bug.

• mersmann added a subscriber: • mersmann.Jun 5 2013, 3:56 PM

I'll take care of this. My guess is that the mouse click event listens to both the OnPush- and OnReleaseEvent.

• mersmann added a comment.Jun 5 2013, 4:15 PM

I'll take care of this. My guess is that the mouse click event listens to both the OnPush- and OnReleaseEvent.

• mersmann added a comment.Jun 19 2013, 2:06 PM

Adding Markus in CC.
Is this a special mint feature that a control point is set on mouseReleaseEvent? Do you need this behavior?

engelm added a subscriber: engelm.Jun 19 2013, 2:35 PM

As a matter of fact, this is a feature! It has been implemented to be able to draw a line with only one click.

It would be possible to 'disable' the creation of the control-point on the release for 'closed figures' by adapting the state "FigurePlacedByDrag". The second transition that leads to state '58' must only be available if the figure is closed.

Do you really want this 'fixed' in the upcoming release?

• mersmann added a comment.Jun 19 2013, 3:21 PM

Ok, nice feature ;-)
We need to disable it on both open and closed figures (line path and polygons). Is this an important feature, than we leave it as it is, otherwise I would just prohibit the event handling in the interactor.

engelm added a comment.Jun 19 2013, 3:25 PM

As we implemented this on purpose, I don't think that completely removing the interaction is an option.

It would also be possible to disable the feature for PlanarFigures that have a certain property defined. Thus, the developer can decide how he wants to interact with the PlanarFigure.

• mersmann added a comment.Jun 19 2013, 4:17 PM

Hm, in this context I think this bug needs to be discussed in detail. I set the RFD flag and change the target milestone to "AfterNextRelease".

• fetzer added a comment.Jun 27 2013, 1:35 PM

This bug could not be fixed within the 2013-06 release and has medium severity. Setting target milestone to unspecified.

• mersmann added a comment.Aug 21 2013, 1:46 PM

This bug was discussed in the MITK meeting yesterday. Since the currently implemented behavior is a MINT feature, we won't remove it. However, there seem to be two interaction modes already implemented, but how is it possible to switch between them?

Adding Daniel Maleike in CC.

• mersmann added a comment.Nov 25 2013, 3:34 PM

Removing RFD tag. Changing asignee, Markus cares about the interaction at MINT.
@Markus: Is there a solution for this issue? (Some switch to define the interaction pattern).

• fetzer added a comment.Dec 9 2013, 3:50 PM

Current release is finished. Reseting target milestone...

kislinsk closed this task as Wontfix.Jun 20 2018, 6:26 AM
kislinsk claimed this task.
kislinsk added a subscriber: kislinsk.
This task was automatically closed because it wasn't updated at least since July 2016 (over 2 years). Please re-open this task if you think that it is still relevant. This most probably means that you will resolve it.
MITK · MIC · IMSY · DKFZ