It also fixes the game Unity of Command II (same bug).

Wine-Bug: https://bugs.winehq.org/show_bug.cgi?id=46070

Signed-off-by: Eric Pouech <epouech@codeweavers.com>

(this fixes --command option when winedbg is relaunched in
wow64 case).
Signed-off-by: Eric Pouech <epouech@codeweavers.com>

Enumerate "shell" registry key entries instead of hardcoding a list.

Don't enumerate any entries unless all the files have the same type.

Pass the correct type to ShellExecuteEx().

This was added in f045c9df, with no explanation.

It does not affect any behaviour in Wine, since FWF_DESKTOP is never set.

It does not make sense, since "open" is already usually the default action on
Windows, and it's not obvious why FWF_DESKTOP would affect this.

It also leans on IContextMenu implementation details.

This reverts one of the changes included in d30dfd24.

Relying on FCIDM_SHVIEW_OPEN snoops into the internals of IContextMenu for no
good reason.

While I haven't tested whether ICommDlgBrowser::OnDefaultCommand() is triggered
in this case, the documentation states that it is "called when a user
double-clicks in the view or presses the ENTER key"; this is neither scenario.

Simply let the context menu call ShellExecuteEx().

These were never used. They were probably anticipating the context menu, but are
missing accelerators and otherwise redundant with the existing entries.

It would be nice to annotate it with __WINE_DEALLOC(NdrFreeBuffer) too,
but that causes a bunch of spurious -Wfree-nonheap-object warnings.

With headers from Zycore version 1.5.0.