Merge lp:~elementary-apps/granite/about-dialog-commandline into lp:~elementary-pantheon/granite/granite
Status: | Merged |
---|---|
Approved by: | David Gomes |
Approved revision: | 643 |
Merged at revision: | 651 |
Proposed branch: | lp:~elementary-apps/granite/about-dialog-commandline |
Merge into: | lp:~elementary-pantheon/granite/granite |
Diff against target: |
121 lines (+71/-2) 2 files modified
lib/Application.vala (+70/-1) lib/Widgets/AboutDialog.vala (+1/-1) |
To merge this branch: | bzr merge lp:~elementary-apps/granite/about-dialog-commandline |
Related bugs: |
Reviewer | Review Type | Date Requested | Status |
---|---|---|---|
David Gomes (community) | Approve | ||
Review via email: mp+185597@code.launchpad.net |
Commit message
[Granite.
Description of the change
[Granite.
This capacity will be needed to trigger showing the About dialog from the launcher menu of an application (see https:/
That menu entry would be added in the .desktop file of each application that wants to have this feature. This would be the only app-specific change.
This works when the app isn't running, and only spawns the About dialog.
Showing the About dialog with this method happens early in the startup stage of the application, so Gtk needs to be explicitly initialized.
Here is an example .desktop file for Scratch: http://
I noticed that using this creates another instance of the application (instead of using a running one if it exists) using around 10 MB just for the about window.
It would be nice to avoid this if there is a running instance.