You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Right now when adding the application actions from a plugin's
QSRegistry dictionary QS simply calls addEntriesFromDictionary. What
this means is that for a given application with a given bundle identifier
only one plugin can add application actions. And if two different
plugins attempt to add application actions for a given app, which ever
plugin is loaded/registered last "wins".
I discovered this because I tried to write a little QSPlugin to add an
update podcast application action for iTunes to sit along side the
Previous/Next Track actions.
The text was updated successfully, but these errors were encountered:
…oading plugins
Previously, the last plugin to create QSApplicationActions for a certain app's action would overwrite any existing actions.
This change adds the any new actions to the existing ones, instead of blindly over-writing
Fixes#460
…oading plugins (#2605)
Previously, the last plugin to create QSApplicationActions for a certain app's action would overwrite any existing actions.
This change adds the any new actions to the existing ones, instead of blindly over-writing
Fixes#460
Right now when adding the application actions from a plugin's
QSRegistry dictionary QS simply calls addEntriesFromDictionary. What
this means is that for a given application with a given bundle identifier
only one plugin can add application actions. And if two different
plugins attempt to add application actions for a given app, which ever
plugin is loaded/registered last "wins".
I discovered this because I tried to write a little QSPlugin to add an
update podcast application action for iTunes to sit along side the
Previous/Next Track actions.
The text was updated successfully, but these errors were encountered: