google-code-export / pushbuttonengine

Automatically exported from code.google.com/p/pushbuttonengine
0 stars 0 forks source link

InputMap does not remove mouse wheel handler when destroyed #158

Open GoogleCodeExporter opened 9 years ago

GoogleCodeExporter commented 9 years ago
InputMap adds a mouse wheel event handler but does not later remove it when
destroyed, causing it to continue to receive mouse wheel events when it
should not.

What steps will reproduce the problem?

1. Create an InputMap and map a handler to InputKey.MOUSE_WHEEL.
2. Destroy the input map.
3. Give your mouse wheel some love. The InputMap instance, even though it
has been destroyed, will still receive the event and call the mapped handler.

What is the expected output? What do you see instead?

I expect a destroyed InputMap to unhook all event handlers and under no
circumstances invoke any callbacks.

What version of the product are you using? On what operating system?

r958-1.0, Windows 7, Flash 9, Flex Builder 4

Please provide any additional information below.

While reading the code I noticed that the MOUSE_OVER and MOUSE_OUT events
are left wired up as well (though I did not test this).

PBE is sexy.

Original issue reported on code.google.com by doubles...@gmail.com on 14 Apr 2010 at 1:24

GoogleCodeExporter commented 9 years ago
Correction: I am using Flex Builder 3, not 4. Sorry for the typo.

Original comment by doubles...@gmail.com on 14 Apr 2010 at 4:45

GoogleCodeExporter commented 9 years ago

Original comment by florent....@gmail.com on 19 May 2010 at 2:17

Attachments: