On Fri, Oct 23, 2015 at 12:30 PM, Eli Zaretskii <
address@hidden> wrote:
> Which shortcut? On the desktop or in the Start Menu?
Taskbar. Most of my tests are not using addpm, but running Emacs and pinning it to the taskbar.
> Anyway, you are in effect saying that when runemacs is run from a
> shortcut, its call to SetCurrentProcessExplicitAppUserModelID has no
> effect? Does that call succeed or fail?
> Also, if you invoke runemacs from the cmd prompt, does the problem go
> away?
Case 1)
- run runemacs.exe from the command line. An icon appears on the taskbar.
- Pin Emacs on the taskbar. Another icon appears (for emacs.exe, not runemacs.exe), so there are two.
- Exit Emacs. The first icon disappears.
- Cick on the remaining one (the one pinned): another icon appears (because the first one does not have the AppId, which I checked).
Case 2)
Like case 1, but after pinning Emacs, I modify it so it points to runemacs.exe, not emacs.exe
No difference with case 1
Case 3)
Like case 1, but running runemacs.exe from Win+R. No difference.
Case 4)
Like case 2, but running runemacs.exe from Win+R. No difference.
Cases 5 and 6)
Like 1 and 2, but creating a desktop shortcut to runemacs.exe and starting from there. No difference.
Case 7)
"Moving" the desktop shortcut (set to runemacs.exe) to the taskbar to pin it. No difference.
Case 8)
- Run addpm
- Run Emacs from the Start Menu icon.
- Pin Emacs to the taskbar
- Run Emacs from the taskbar icon: Two icons appear. etc etc
In all cases, if you run several instances of Emacs (i.e., if you run runemacs.exe several times from the command line), the icons are grouped in the taskbar. So the call to Set[...]ID does succeed *from the command line* (I debugged runemacs.exe and emacs.exe and checked that the call was succeeding and the AppId was being set. They were.)
I haven't debugged runemacs.exe starting it from a shortcut.
Is there anything specific that you want me to try?
J