[Bf-committers] [Bf-blender-cvs] SVN commit: /data/svn/bf-blender [29660] trunk/blender/source/blender: Fix #22553: dragging number buttons would run update functions more often than

Brecht Van Lommel brecht at blender.org
Fri Jul 2 12:09:48 CEST 2010


I made this an opt-in rather than opt-out thing because there's about
10x more places that don't need it than places that do. Mouse trails
would be opt-in too by the way.

My reasoning was that this is like a mouse trail but simpler
implementation, just add an extra case INBETWEEN_MOUSEMOVE: line and
you're done. Now that I think of it, mouse trail does not need to be
too complicated, using a ListBase of wmEvent's, just a bit more code.
I prefer the current method, but if you think doing it the other way
is better design, I can change it.


On Fri, Jul 2, 2010 at 11:23 AM, Ton Roosendaal <ton at blender.org> wrote:
> Hi,
> I forgot: original idea was to configure Blender WM or Ghost to add
> mouse-trail custom data to mousemove events. That would balance the
> the queues nice too.
> -Ton-
> ------------------------------------------------------------------------
> Ton Roosendaal  Blender Foundation   ton at blender.org    www.blender.org
> Blender Institute   Entrepotdok 57A  1018AD Amsterdam   The Netherlands
> On 2 Jul, 2010, at 10:34, Ton Roosendaal wrote:
>> Hi,
>> It might be more clearly solved by keeping a general mousemove event,
>> and give it a value type (event->val) when it's an 'inbetween event'.
>> A lot of event code depends on detecting mousemoves, and needing to
>> adapt all code with this case is not very nice. It's not really clear
>> either, platform depending, etc.
>> -Ton-

More information about the Bf-committers mailing list