After an evaluation, GNOME has moved from Bugzilla to GitLab. Learn more about GitLab.
No new issues can be reported in GNOME Bugzilla anymore.
To report an issue in a GNOME project, go to GNOME GitLab.
Do not go to GNOME Gitlab for: Bluefish, Doxygen, GnuCash, GStreamer, java-gnome, LDTP, NetworkManager, Tomboy.
Bug 645031 - Warnings when removing workspaces
Warnings when removing workspaces
Status: RESOLVED FIXED
Product: gnome-shell
Classification: Core
Component: general
unspecified
Other Linux
: Normal normal
: ---
Assigned To: gnome-shell-maint
gnome-shell-maint
Depends on:
Blocks:
 
 
Reported: 2011-03-17 15:12 UTC by Alexander Larsson
Modified: 2011-06-03 17:58 UTC
See Also:
GNOME target: ---
GNOME version: ---


Attachments
workspaces-view: Simplify handling of removed workspaces (4.97 KB, patch)
2011-06-01 11:17 UTC, Florian Müllner
committed Details | Review

Description Alexander Larsson 2011-03-17 15:12:18 UTC
When workspaces are removed i get warnings like:

Window manager warning: Log level 16: value "-nan" of type `gfloat' is invalid or out of range for property `y' of type `gfloat'

This is due to this code in workspacesView.js:_updateWorkspaceActors()

                Tweener.addTween(workspace.actor,
                                 { y: workspace.x,

Its obviously wrong to tween y to x, but neither workspace.x or workspace.y is set. I don't know what the initial code was supposed to do here. Where do we want to animate lost workspaces to?
Comment 1 Dan Winship 2011-04-11 19:45:20 UTC
Well, they already do animate, out off the right side, the opposite of the animating-in effect. Maybe this part is just dead code?
Comment 2 Florian Müllner 2011-06-01 11:17:36 UTC
Created attachment 188985 [details] [review]
workspaces-view: Simplify handling of removed workspaces

(In reply to comment #0)
> This is due to this code in workspacesView.js:_updateWorkspaceActors()
> 
>                 Tweener.addTween(workspace.actor,
>                                  { y: workspace.x,
> 
> Its obviously wrong to tween y to x, but neither workspace.x or workspace.y is
> set.

Woops, looks like it should now be workspace._y, but ...


> I don't know what the initial code was supposed to do here. Where do we
> want to animate lost workspaces to?

... the animation is completely unnecessary now - Dan is right, it's pretty much dead code (e.g. animating an empty container).


Workspaces used to contain the desktop background, so when a
workspace was removed, we animated its actor to an off-screen
position before destroying it. As the background has been
removed a while ago, we can destroy the actor directly.
Comment 3 Dan Winship 2011-06-02 13:39:53 UTC
Comment on attachment 188985 [details] [review]
workspaces-view: Simplify handling of removed workspaces

This all looks reasonable, but if I repeatedly do the "drag last window from existing workspace to a new workspace" thing, I still get

    Window manager warning: Log level 16: value "-84.957748" of type `gfloat' is invalid or out of range for property `width' of type `gfloat'

etc
Comment 4 Florian Müllner 2011-06-02 13:59:33 UTC
(In reply to comment #3)
> (From update of attachment 188985 [details] [review])
> This all looks reasonable, but if I repeatedly do the "drag last window from
> existing workspace to a new workspace" thing, I still get
> 
>     Window manager warning: Log level 16: value "-84.957748" of type `gfloat'
> is invalid or out of range for property `width' of type `gfloat'
> 
> etc

Looks like bug 649001?
Comment 5 Dan Winship 2011-06-03 17:36:39 UTC
Comment on attachment 188985 [details] [review]
workspaces-view: Simplify handling of removed workspaces

ok, 649001 fixes the warnings, and this patch doesn't seem to change any behavior, so I guess it's correct.
Comment 6 Florian Müllner 2011-06-03 17:58:28 UTC
Attachment 188985 [details] pushed as 45c1a9e - workspaces-view: Simplify handling of removed workspaces