Merge lp:~alexlauni/libunity/clear-models-on-vanish-859760 into lp:libunity
Proposed by
Alex Launi
Status: | Merged | ||||
---|---|---|---|---|---|
Approved by: | Neil J. Patel | ||||
Approved revision: | 82 | ||||
Merged at revision: | 83 | ||||
Proposed branch: | lp:~alexlauni/libunity/clear-models-on-vanish-859760 | ||||
Merge into: | lp:libunity | ||||
Diff against target: |
24 lines (+9/-0) 1 file modified
src/unity-scope-proxy-remote.vala (+9/-0) |
||||
To merge this branch: | bzr merge lp:~alexlauni/libunity/clear-models-on-vanish-859760 | ||||
Related bugs: |
|
Reviewer | Review Type | Date Requested | Status |
---|---|---|---|
Mikkel Kamstrup Erlandsen (community) | Approve | ||
Neil J. Patel (community) | Approve | ||
Review via email: mp+77019@code.launchpad.net |
Description of the change
Clears the models before making new ones so that old results don't get stuck
To post a comment you must log in.
Hmmmm... I am a bit split on this...
Keeping the model around is actually by design. It allows for a
lens/scope to exit, but keep useful state around - which it can pick
up automagically when it starts again. The idea being that it
shouldn't matter whether the lens/scope is running or not; it will be
transparently restarted by DBus activation when needed.
Those noble ideas aside I agree that it adds some unwelcome complexity
when not using this feature. So I agree somewhat on the intent of this
patch, but not so much in it's implementation.
Also at this point in the cycle I think we need to keep a consistent
behavior of the API. So I'd rather see a solution along the lines of:
* Add a new property "state-type" on lenses and scopes which has
values in a Unity.LensStateType enum
public enum Unity.LensStateType {
STATELESS,
RETAINED
}
(This opens the possibility for some nastiness in P where we can add a
PERSISTENT/CACHED statetype, that will transparently store and load
the model state on disk)