Def. cmmd setup:Excuse me if I mention the obvious, but at least it’ll get that out of the way?
Def cmmd pref needs to be enabled via advanced prefs page (I assume this has been done, 'cos of Q about pwr user stuff)
L/M refer to mouse buttons, not keys - again I doubt this is the problem …
I use Mirai mode and it all works fine (/32b) - with certain camera modes, user can only set one def.cmmd, because of key use for navigation etc. … combine this possibility with using a mac (i use PC) and there’s all manner of scope for trouble?
Maybe there’s something in your (wings) prefs that’s causing a problem - it might be worth considering moving (not dumping) your prefs folder to somewhere safe, re-starting wgs so it’s using default prefs?
(If not the answer, just move your old prefs back)
Sorry can’t be more helpful …
<< some great info there! thanks for the resource >>
np - you’d have found it somehow or other, anyway.
<< nice to see … >>
well, you won’t see much, as I don’t do much (atm) and rarely post what I do make 
I have no aspirations whatsoever to work in the industry, for various reasons (two being I wouldn’tbe good enough or quick enough…) … so there’s no real need for self promotion 
Am happier with non-organic stuff, again, for various reasons.
Current project involves objects with less than 30 faces. These objects will exist in real-life … therefore the simpler they are, the easier they are to make - these certainly wouldn’t win any prizes for artistic merit - but they (about 5-6 RL prototypes made to date) - or rather the function they provide - work, and provide extended functionality for something else.
pwr user prefs:
A personal taste item … luv’em or hate 'em … enabled in my case.
When enabled, they offer the option of including the last element selected (as part of a vector definition procedure) as well as executing (that part of) the procedure.
Eg
Say you’re doing a vector move and the vector needs to be specified by selecting 3 verts (want normal to that plane).
So you’d (with pwr u prefs enabled)
Select geom
rmb move
lmb first vert
lmb second vert
RMB third (and last) vert
This last rmb action executes the op AND includes the 3rd vert in the sequence - thus defining the required plane normal.
With these prefs disabled, you’d have to:
Select geom
rmb move
lmb 1st
lmb 2nd
lmb 3rd
rmb execute.
With longer vector def procedures, the saving, percentage wise, lessens - but if you do a lot of stuff where you are using 2 elements to define a vectore, then it’s useful - imo 
There’s pros and cons to both - a couple of the main objections to ‘the enabled option’ - by those that prefer the disabled approach - were:
Lack of continuity with other commands
Fact that user has to click on an element that’s already selected, during exit / excute - otherwise it’ll get added.
Try both (well, you’ve already been using one of 'em - by definition - but was it ‘normal’
) - and make up your own mind.
Strong opinions were present at the time - for both approaches - hence the pref …
hth
pp