[Bf-taskforce25] Event Handling Bug - WHEELDOWNMOUSE not invoking operators?

[Ton Roosendaal]

Hi Joshua,

The KM_PRESS event->val has to become KM_ANY for the 
WM_keymap_add_item().
Wheel values are plus or minus...

Tested it, and works fine. I'm still reviewing uiButtons code, cleaning 
some small things, and trying to grasp it fully. Als several bugfixes 
are coming later.
So I cannot commit a fix. :)

-Ton-

------------------------------------------------------------------------
Ton Roosendaal  Blender Foundation   ton at blender.org    www.blender.org
Blender Institute BV  Entrepotdok 57A  1018AD Amsterdam The Netherlands

On 1 Dec, 2008, at 12:44, Joshua Leung wrote:

> Hi Ton,
>
> While working on a few operators for View2D stuff, I noticed that 
> there seems to be a problem regarding operators which use 
> WHEELDOWNMOUSE as 'key' (in keymap) which triggers the operator. It 
> seems that the conversions from ghost to events goes ok (at least the 
> recognition of WHEELDOWNMOUSE works... I tested that with some debug 
> prints in the relevant place), however, the event doesn't seem to 
> reach the operators which use it.
>
> The WHEELUPMOUSE events seem to get handled normally/quite well 
> though. Also, it doesn't look like in error in the operator code I 
> wrote. It is also quite unlikely that the event is getting picked up 
> by UI-code, given that the mouse was nowhere near any buttons during 
> the tests.
>
> BTW, to test this, try some of the view manipulation methods in 
> Timeline.
>
> Regards,
> Joshua
> _______________________________________________
> Bf-taskforce25 mailing list
> Bf-taskforce25 at blender.org
> http://lists.blender.org/mailman/listinfo/bf-taskforce25