>I wonder why, for instance, menus disappear once a selesction is made? Couldn't it stick around in case you want to make another chioce from the same menu?

A good interface does not impose one specific command vector on its users. Cooper considers menus to be primarily for the benefit of beginners--they're a good way to see what the app offers. But experienced uses will use hotkeys and toolbar buttons (which he designates as "buttcons":).

>Same goes for rt-click menus, even especially more so there, where often they list properties to be turned on/off, and usually one wants more than one. Having to move the mouse again to the 'object', rt-click again, then move it down the list again is just plain wasteful and frustrating.

Absolutely. This is just bad UI, even without Cooper chiming in. :) That's why good apps use property pages with Apply buttons.

Some people like mice, others don't. It's not Windows fault that you have to use it, but the UI designers'.