lp:~klap-in/compiz-plugins-main/bug904205

Branch merges

Propose for merging

No branches dependent on this one.

Merged into lp:compiz-plugins-main at revision 34

Daniel van Vugt: Approve on 2012-07-03

Diff: 49 lines (+10/-10)

1 file modified

wall/src/wall.cpp (+10/-10)

api

Related source package recipes

No recipes using this branch. (?)

Create packaging recipe

Related snap packages

Related bugs

Bug #904205: Desktop wall: Bindings for next/previous don't wrap to the next row

Low

Fix Committed

Link a bug report

Related blueprints

34. By G. Uitslag <email address hidden> on 2012-06-30

Fix next/previous keybindings for Wall plugin

33. By Sam Spilsbury on 2012-05-15

Adapt for behavioural changes in lp:~smspillaz/compiz-core/compiz-core.work_923683

Merge lp:~smspillaz/compiz-snap-plugin/compiz-snap-plugin.work_923683 into lp:compiz-snap-plugin

32. By Sam Spilsbury on 2012-05-09

If a window spanned two monitors it would shift around on viewport changes.
Take all workareas into account when calculating window shift. (LP: #755842)

31. By Daniel van Vugt on 2012-04-27

Set VERSION to 0.9.7.3 until we have a candidate for 0.9.7.4

30. By Daniel van Vugt on 2012-04-24

Prepare to release compiz-plugins-main 0.9.7.2

29. By Daniel van Vugt on 2012-04-24

Change the mouse pointer while dragging windows in expo. Just like the
ubuntu branches do. (LP: #987647)

28. By micove on 2012-04-24

Fix exec_prefix in some of the pc files. (LP: #959260)
---
Add missing library links. (LP: #959260)
I checked the buildlogs and found:
dpkg-shlibdeps: warning: debian/compiz-fusion-plugins-main/usr/lib/x86_64-linux-gnu/compiz/libwall.so
contains an unresolvable reference to symbol dlopen: it's probably a plugin.

dpkg-shlibdeps assumes that the program that loads the plugins provides these
symbols therefore not giving an error.

[Miguel Colon <email address hidden>, 2012-03-14]

27. By Sam Spilsbury on 2012-04-10

Don't increment the destroy ref count of a window unless an animation is
active. (LP: #940603)

It doesn't make any sense to increase the destroy reference count of a window
on CompWindowNotifyBeforeDestroy based on whether or not an an animation for
that window "could" be allowed - CompWindowNotifyBeforeDestroyed is called
on CompWindow::destroy (which under sane circumstances, should only ever be
called when the window is either reparented away from its parent or the root
window or when the window is destroyed).

In this case, we deregister all events on the window so it isn't possible to
determine through any normal means that a close animation is going to activate
on the window. And in any event, the unmap which causes close animations
always comes before the DestroyNotify or ReparentNotify anyways.

Even if the CompWindowNotifyClose were to somehow come after the window
received a ReparentNotify or DestroyNotify, the tradeoff then comes between
not playing animations for those corner case windows or keeping ghost windows
on screen because we kept a destroy reference and never got rid of it. In this
case, it is more sane to do the former.

26. By Sam Spilsbury on 2012-04-10

Added a flag to specify whether an animation actually needs a transformed
window. (LP: #976469)

25. By Daniel van Vugt on 2012-03-21

Fix stuttering animations on large/fullscreen windows by using the higher
performance rendering method (full screen damage). (LP: #930192)