One more chance for giving the correct answer

[Thomas]

Current behavior of the program (using MouseDown event):
When you click on a multiple-choice button with the left mouse button and holding down the mouse button while moving the cursor out of the button, the answer of the button is evaluated because the MouseDown event is triggered. You can also describe this like a drag and drop action. You drag the multiple-choice button and drop him away from his place.

Program behavior using MouseUp event:
When you do the same, nothing is evaluated because there is no more an MouseDown event procedure and the MouseUp event cannot fire. This is the last chance to give the correct answer instead of giving the false answer when you realize this on clicking the button. So I can check if I have pressed the correct button while holding down the mouse button for a second. Sometimes I know the correct answer but I click the false button because there are many buttons on the screen and some buttons have similiar captions (verm Quint (5th) and reine Quint (dim. 5th)).

[Quentin]

Hi,

I'm not sure I fully understand you demand, but if you right-click on the multiple choice buttons, the interval/chord they represent is played.
I think that is what you talked about with the drag-and-drop actions on the buttons.

Otherwise, please try to specify your demand

Cheers

[Thomas]

I don't mean the right click. I'm speaking of the normal left click. There a 3 phases of the click of the button:

- (1) Moving down,
- (2) still holding it down for an undefinite time and
- (3) moving up.

I don't really want a drag and drop function on a multiple-choice button. It's just another way to describe what is going on.


Scenario: 8-|

I click (phase 1) in lesson 22 of the interval recognition exercise the button verm Quint (dim. 5th). While I'm clicking (phase 2) I realize that this is the false answer. I wanted to click to reine Quint (5th). Because of the many buttons (13) and the two buttons with similar captions (verm Quint and reine Quint) I clicked the wrong answer. But I won't give this answer, so I move the cursor out of the button and then release (phase 3) the left mouse button. The only reason to move the cursor away from the button is not to trigger the MouseUp event. When you use the MouseUp event instead of the MouseDown event, this could be true.

[Quentin]

Ok, sorry, I read your first message too fast. It perfectly made sense from the start :--D
The developper of EarMaster chose after reflection the Mouse Down event instead of Mouse Up at the time of the writitng of the program.
I have forwarded your message and he'll take a look again and ponder wether we should return to the classic Windows Mouse up configuration.