On 24 Jun 2018 20:56:24 GMT, Stefan Ram wrote:

I don't know. That's why I was asking.

I think you bring up a good question, which is, apparently, that you
navigate (and modify) the WinXP Cascade Menu using keyboard clicks, whereas
I navigate (and modify) it using mouse clicks.

You probably also use the *default* "Programs" menu on WinXP, where I never
do (for reasons that you don't want to hear because I will talk your ear
off if you ask.

So our use model on WinXP isn't the same even when we're on XP:
a. You use "Programs" (most likely); I use "menu" (next to "Programs")
b. You use keyboard shortcuts; I use mouse clicks.

On Win10, I use the *same* strategy for the Win10 Cascade Menu as on XP:
a. I use "menu" (next to "Programs")
b. I use mouse clicks.

I can't answer your question on the keyboard shortcuts though.
Maybe someone who knows keyboard shortcuts better than we do, can help.

The amazing thing about traditional menus is that they
support both a mouse-oriented and a keyboard-oriented
user style.

Until you mentioned the keyboard-oriented user style, I wasn't considering
it (I think, oh, many many many years ago I tried it, and didn't like it),
but it's a perfectly valid style.

I'm on record for saying two things about your suggested style:
1. It's perfectly valid - so I hope someone answers the question, and,
2. I don't see why it wouldn't work on Win10 just like WinXP since the
menus are exactly the same and both the WinXP and Win10 "menu" is right
next to the WinXP & Win10 "Programs" menu.

I don't see any difference whatsoever - but I still can't answer your
keyboard question because I don't have experience with the keyboard
shortcuts.

It's a good question though.
I hope someone has the answer for you.

But I already got my personal solution: Autohotkey.
It allows one to build menus that can be opened with hotkeys
and be operated using the keyboard (or the mouse). One could
use it to create something like the classical start menu.
But the definition of keys and menus with Authotkey is more
accessible to "advanced" users, because one configures it by
writing a kind of a script (a program).

Good for you to find a 3rd party solution that works well for you.

I used to use the Classic Shell but I've had so many problems with
Microsoft breaking things that I recently decided (back in February) to try
to just wrestle Microsoft native software into doing what I want it to do.

That idea of microsoft to copy a touch interface for their
desktop OS because touch devices are very successful today
seems to be a kind of cargo-cult management.

I agree with your sentiment, especially as I don't have touch screens.

I recently started wrestling the orthodox Start Menu and the heterodox
Start Menu, and the Cascade Menu into consistent groups where here are my
current works in progress...

1. Win10 Cascade Menu
http://img4.imagetitan.com/img.php?image=18_menu1.png
2. Win10 Orthodox Start Menu:
http://img4.imagetitan.com/img.php?image=18_menu2.png
3. Win10 Heterodox Start Menu:
http://img4.imagetitan.com/img.php?image=18_menu3.png

Tutorial:
https://groups.google.com/forum/#!topic/microsoft.public.windowsxp.general/eWU-jOkFRtU