Our current keymap doesn't give us enough room to make such changes in
the event system. To fix small issues caused by this, we would need to do
drastic changes in Blender's keymaps and internal handling. It was worth
a try, but it didn't work.
I can write down a more descriptive statement in a few days, but for now
I need a break of this stuff.
- Get rid of the obsolete operator
- Use select_or_deselect_all in 3ds keymap, which performs better
than separate deselect all and select binded to the select mouse.
This was already done for maya, and seems was accidentally reverted
by 5a91db3d.
In fact, armature layers operators (set layers, and show all) were kind of messy and broken
in Edit mode (Select layers had two different operators for Pose and Edit modes, both
using the same funcs that could only work in Pose mode, Show All was supposed to be
used in both modes but again, its exec code could only work in Pose one).
Fixed that by:
* Using only one op for each task, for both modes (with adapted poll func).
* Replacing 'object from context' access by an helper that returns the right Armature
object in both Edit and Pose modes.
Was missing keymap for REGION_TIMER, which ended up
in missing updates happening.
Added this kind of timer to RNA, so keymaps could
bind to it.
Also made 3ds max keymap working again. Too bad it
was broken in 2.67 and 2.67a :S
Quad View: ALT + W
Switch Wireframe / Solid: F3
Render: F10
Properties: F12
Ortho / perspective View: P
Zoom to selected center: Z
Select/ Deselect all: CTRL + A
in changing A hotkeys ctrl-a hotkeys are now ctrl-shift-a and GameEngine is now ctrl-alt-shift-p
Made keyap use the same select_or_deselect_all operator
as used for maya keymap instead of tricks with deselect_all.
Solves issue with selection in editor mode (reported as #3
in the original bug report).
