consume() in MouseEvent

[asit]

I recently came through the following code...

public void mouseReleased( MouseEvent e ) { // called after a button
is released
isButtonPressed = false;
setBackground( Color.black );
repaint();
e.consume();
}


Can anyone tell me what is the task of e.consume() ????

 

[Mark Space]

I recently came through the following code...

public void mouseReleased( MouseEvent e ) { // called after a button
is released
isButtonPressed = false;
setBackground( Color.black );
repaint();
e.consume();
}


Can anyone tell me what is the task of e.consume() ????

The docs say:

public void consume()

Consumes this event so that it will not be processed in the default
manner by the source which originated it.


So I assume there's some low-level behavior which was undesired, and the
consume() stops that behavior.

 

[John B. Matthews]

The docs say:

public void consume()

Consumes this event so that it will not be processed in the default
manner by the source which originated it.


So I assume there's some low-level behavior which was undesired, and the
consume() stops that behavior.

It looks like the OP is working through a tutorial similar to this,
which demonstrates the effect:

<http://www.dgp.toronto.edu/~mjmcguff/learn/java/04-mouseInput/>

 

[Albert]

Mark Space a écrit :

The docs say:

public void consume()

Consumes this event so that it will not be processed in the default
manner by the source which originated it.


So I assume there's some low-level behavior which was undesired, and the
consume() stops that behavior.

The good question is then, what is this low-level behavior ? Since
listener are called in "addition order", default behavior should have
processed already, don't you think ?

 

[asit]

The good question is then, what is this low-level behavior ? Since
listener are called in "addition order", default behavior should have
processed already, don't you think ?

I think I agree with u !!!!!

 

[John B. Matthews]

The good question is then, what is this low-level behavior ? Since
listener are called in "addition order", default behavior should
have processed already, don't you think ?

I think I agree with u !!!!!

Why not try the experiment: elide the call to e.consume() and see how
the program's behavior changes?