Quote:
Originally Posted by kovidgoyal
This sounds very much like a timing related issue to me. Probably, there is a race condition between calling SetCurrentProcessExplicitAppUserModelID and the taskbar deciding icon grouping. If the call happens before the taskbar decides, it groups according to its internal heuristics, if not it groups by uid.
|
Can you suggest anyway to test that idea?
I used 3.4 for several hours yesterday, closed/started and restarted at least a dozen times with no problems. This morning when I started calibre, I got the extra icon, if I restarted it I got the extra icon, if I waited a while and started it again I got the extra icon. I did a Repair and all was well again - but I don't expect it to last.
My impression is that something causes Windows to lose whatever pinning a running instance does to the registry - but only for 64 bit calibre, not 32bit calibre or other programs (e.g. PDF XChange), that use the AppUserModelID 'facility'.
I say this because the misbehaviour is essentially the what one gets if you pin to the taskbar from the start menu (or anywhere else) rather than a from a running instance in the taskbar itself, and the fact it can only be fixed by a re-install or repair.
That pinning to the taskbar from within the taskbar does something different to pinning to the taskbar from elsewhere is bizarre - IMO.
BR