Merge lp:~donadigo/granite/saved-state-in-appclass into lp:~elementary-pantheon/granite/granite
Status: | Rejected |
---|---|
Rejected by: | Danielle Foré |
Proposed branch: | lp:~donadigo/granite/saved-state-in-appclass |
Merge into: | lp:~elementary-pantheon/granite/granite |
Diff against target: |
175 lines (+128/-2) 1 file modified
lib/Application.vala (+128/-2) |
To merge this branch: | bzr merge lp:~donadigo/granite/saved-state-in-appclass |
Related bugs: |
Reviewer | Review Type | Date Requested | Status |
---|---|---|---|
elementary Pantheon team | Pending | ||
Review via email: mp+290085@code.launchpad.net |
Commit message
Fixes bug #1475825: Window states are saved inconsistently.
Description of the change
Fixes bug #1475825: Window states are saved inconsistently.
Saving state is implemented directly in Application class. To make window saving it's state simply set the GSettings schema path "settings_
Much of the code was taken from the saved-state branch:
https:/
Process of porting apps:
* Remove old, separate saved-state code from the application.
* Add "saved-state" key to schema .xml file.
* Set settings_schema_id to where are the app settings stored.
* Call add_window () in the activate () method.
Example:
public class App : Granite.Application {
...
public App () {
...
...
}
public override void activate () {
...
var window = new Gtk.Window ();
add_window (window);
...
}
}
Unmerged revisions
- 934. By Adam Bieńkowski
-
Implement saved state in Application class
Breaks ABI