On 13-05-2013, at 7:36 AM, "David T. Lewis" <lewis at mail.msen.com> wrote:

> On Mon, May 13, 2013 at 12:42:19PM +0200, Bert Freudenberg wrote:
>> 
>> I use it: shift-click followed by CMD-E is the quickest way to look at the implementation behind a menu item. OTOH, a morphic halo menu entry might be more appropriate for that function.
>> 
> 
> I see no straightforward way to eliminate the conflict between conflict
> between usage of shift state for Morphic, versus usage of shift state to
> control case sensitive search.


We could change the modifier key used for direct-to-morphic selections and leave the shift to pass on to deeper code.

And I see Bob has already pointed out making proper usage of hierarchical menus as an option; yet again a place where the RISC OS way has been doing it better for decades. Why on earth do we still have places where secondary menus have to be triggered by clicking on a menu option 'foobly…' ?

We could also consider menu items that are shift-sensitive and update to suit. Apple managed to get that one reasonably correct for the quit/force quit menu item for example. Just as long as it doesn't result in yet another slowdown of everything in the system.

A really basic point underlying all this is that the UI level should handle all the UI stuff and pass suitable parameters down to the tools that said UI triggers. There is no way that the method to search all the sources should get a morphic event passed to it, for example. Pass it a boolean for shift, a number for 'time held down', a point for where clicked, but never, never a morphic event.

tim
--
tim Rowledge; tim at rowledge.org; http://www.rowledge.org/tim
Useful random insult:- Always responds to "Make Money Fast" postings on the Net.