https://bugs.kde.org/show_bug.cgi?id=409723
Hannah von Reth changed:
What|Removed |Added
Resolution|WORKSFORME |FIXED
--- Comment #12 from Hannah von Reth
https://bugs.kde.org/show_bug.cgi?id=409723
Thomas changed:
What|Removed |Added
Resolution|--- |WORKSFORME
Status|REPORTED
https://bugs.kde.org/show_bug.cgi?id=409723
--- Comment #11 from Hannah von Reth ---
I think for nsis https://github.com/KDE/snoretoast/#shortcut-creation-with-nsis
is really the easiest way. A simple macro to create a shortcut, depending on
the Windows version. No need to extract the clsid etc.
https://bugs.kde.org/show_bug.cgi?id=409723
--- Comment #10 from Thomas ---
I added a NSIS headerfile that does exactly the same as my wix snippet, don't
think you will want to use that either:
https://github.com/safing/nsis-shortcut-properties
--
You are receiving this mail because:
You are
https://bugs.kde.org/show_bug.cgi?id=409723
--- Comment #9 from Hannah von Reth ---
Thx, yes sadly the clsid needs to be hard coded as it gets compiled into the
com interface...
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=409723
--- Comment #8 from Thomas ---
I really don't think that this is the way you want to do it since the
SnoreToast-CLSID is hardcoded into the installer at the moment. We will write
an entry in the Makefile that replaces the CLSID in the wixfile
https://bugs.kde.org/show_bug.cgi?id=409723
--- Comment #7 from Hannah von Reth ---
Yes that's the way it was solved with nsis, and you would need to add an if
clause to update the shortcut in a post install step too.
I think -v should probably report the CLSID for scripting purposes, could be
https://bugs.kde.org/show_bug.cgi?id=409723
--- Comment #6 from Thomas ---
But this requires to make the installer like this:
if(Windows-Version >= 8)
install shortcut using Snoretoast;
else
install shortcut yourself;
add own properties to already existing shortcut;
We are making the
https://bugs.kde.org/show_bug.cgi?id=409723
--- Comment #5 from Hannah von Reth ---
The recommended solution is to use snoretoast.exe in a post install step during
installation to create the shortcut.
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=409723
--- Comment #4 from Thomas ---
Yes, but not every installer can handle PKEY_AppUserModel_ToastActivatorCLSID.
I would have created the link first and if Windows-Version >= 8, I would have
let Snoretoast add the appID and the CLSID to the existing link.
https://bugs.kde.org/show_bug.cgi?id=409723
--- Comment #3 from Hannah von Reth ---
The only scenario where a link with an app id is create I could imagine is
during install.
Every installer should know about Icons and parameters?
--
You are receiving this mail because:
You are watching all
https://bugs.kde.org/show_bug.cgi?id=409723
--- Comment #2 from Thomas ---
Additional Link-Properties (Icon, Parameters, ...) would get lost.
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=409723
--- Comment #1 from Hannah von Reth ---
Hm any reason you can't remove and recreate the url?
--
You are receiving this mail because:
You are watching all bug changes.
13 matches
Mail list logo
