[Bf-taskforce25] Feedback needed: mapping tablet, mouse, devices

[Ton Roosendaal]

Hi,

>>  KM_ACTION_MOUSE
>>  KM_SELECT_MOUSE
>>
>>  And have those translated to left/right mouse based on the user  
>> preset.
> I really don't agree with this much. The current method of just  
> 'swapping' mouse buttons is really not the best way of doing things  
> and makes many things awkward- it was just implemented for simplicity  
> at the time, since there was no proper way to customise. Especially in  
> the painting modes, things get murky. Ideally it would be great to  
> have full customisation over mouse buttons, being able to assign  
> different commands to left / right / middle mouse buttons (with or  
> without modifiers), and even extra side buttons that are on some mice  
> too.

I think you misunderstood; those two event defines are only hints, so  
Blender can remap all appropriate handlers with 1 command. You will  
still define left/right mouse handlers of course, like for painting.  
This way remapping is much simpler, and can become configured  
internally, so we can deliver Blender with a single keymap default for  
both cases.

-Ton-

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

On 23 Nov, 2008, at 23:28, Matt Ebb wrote:

> Hiya
>
> On Sun, Nov 23, 2008 at 11:13 PM, Ton Roosendaal <ton at blender.org>  
> wrote:
>>
>>
>>  1) Tablet mapping
>>
>>  I'm not a tablet user... not sure how many options you have for a pen
>>  click. Currently the tablet event is registered as-such, but I can
>>  imagine you want tablet events to map to mouse clicks. Or do we leave
>>  this to the tablet drivers to handle?
> There really isn't anything much to worry about for tablets in terms  
> of mouse events. The drivers already map tablet buttons to mouse  
> clicks, which is how they are interpreted in Blender. Any additional  
> side buttons on the tablet too are generally handled by the driver,  
> mapping them to mouse buttons, key commands, etc.
>
> The only thing different about tablets is that there's extra  
> information such as the 'active tool' (eraser or pen for example), or  
> pressure (float value from 0.0 - 1.0) or tilt (a vector). From memory  
> these don't really work as 'events' per se, they don't trigger  
> anything in a queue, they're just additional information that you  
> should be able to get at any time. For example right now there's a  
> float get_pressure() function that you can use within a painting loop,  
> to get the current tablet pressure at that time.
>   2) Mouse mapping
>>
>>  To efficiently make use of user configs for left/right mouse
>>  especially, we should prevent this to happen in all cases. A
>>  keymap/handler definition therefore should use these defines if you
>>  intend this to be user-defined:
>>
>>  KM_ACTION_MOUSE
>>  KM_SELECT_MOUSE
>>
>>  And have those translated to left/right mouse based on the user  
>> preset.
> I really don't agree with this much. The current method of just  
> 'swapping' mouse buttons is really not the best way of doing things  
> and makes many things awkward- it was just implemented for simplicity  
> at the time, since there was no proper way to customise. Especially in  
> the painting modes, things get murky. Ideally it would be great to  
> have full customisation over mouse buttons, being able to assign  
> different commands to left / right / middle mouse buttons (with or  
> without modifiers), and even extra side buttons that are on some mice  
> too.
>
> For example, look what you can do with Silo:
> http://www.silo3d.com/Tutorials/Mouse_Customization/ 
> Mouse_Customization.html
>
> i.e. not only should it be possible to set up customisable tools/menus  
> on mouse buttons (i.e. left click select, right click radial menu) but  
> it should also make it possible to make setups that mimic the 3D  
> navigation configs in other apps (eg. Maya: Alt LMB rotate, Alt MMB  
> pan, Alt RMB, zoom). Having just two options doesn't give nearly the  
> amount of flexibility required.
>   4) Simpler mouse support
>>
>>  How will we support one- or two-button mice (laptops)? The current
>>  mapping gives conflicts with hotkeys in cases, will need some
>>  experimenting.
> With the above customisation, this could just be a matter of shipping  
> with a preset '2 button mouse config' that just remaps things in a  
> more convenient way for those devices.
>   
> cheers
>
> Matt
>
> _______________________________________________
> Bf-taskforce25 mailing list
> Bf-taskforce25 at blender.org
> http://lists.blender.org/mailman/listinfo/bf-taskforce25