Overview: don't use the overlay_group

It's a deprecated concept, and we want to have our own actor
that we can add to the chrome to handle the input region.

https://bugzilla.gnome.org/show_bug.cgi?id=700735
This commit is contained in:
Giovanni Campagna
2013-05-21 22:15:01 +02:00
parent 35c665156b
commit d0310bd745
4 changed files with 11 additions and 9 deletions

View File

@ -137,7 +137,7 @@ const WorkspacesView = new Lang.Class({
let ws = new Workspace.Workspace(null, i);
ws.setFullGeometry(monitors[i]);
ws.setActualGeometry(monitors[i]);
global.overlay_group.add_actor(ws.actor);
Main.layoutManager.overviewGroup.add_actor(ws.actor);
this._extraWorkspaces.push(ws);
}
},
@ -594,7 +594,7 @@ const WorkspacesDisplay = new Lang.Class({
this._updateWorkspacesActualGeometry();
for (let i = 0; i < this._workspacesViews.length; i++)
global.overlay_group.add_actor(this._workspacesViews[i].actor);
Main.layoutManager.overviewGroup.add_actor(this._workspacesViews[i].actor);
},
_scrollValueChanged: function() {
@ -638,7 +638,7 @@ const WorkspacesDisplay = new Lang.Class({
// This is kinda hackish - we want the primary view to
// appear as parent of this.actor, though in reality it
// is added directly to overlay_group
// is added directly to Main.layoutManager.overviewGroup
this._notifyOpacityId = newParent.connect('notify::opacity',
Lang.bind(this, function() {
let opacity = this.actor.get_parent().opacity;