Menu

#1095 fluxbox 1.3.5 opaqueMove glitch

future release
open
nobody
None
5
2016-09-22
2013-10-07
Alzheimer
No

When I move windows in fluxbox they leave a trail of window borders...

This only happens when opaqueMove is set to false in .fluxbox/init - which is not the case for new profiles. I'm not sure why it's set like that for me. Maybe I set it sometime because without it, moving windows is slightly sluggish for me..

1 Attachments

Discussion

  • edman007

    edman007 - 2013-10-12

    This bug happens on my system with 1.3.5, was not there with earlier versions (1.3.2 is what I had before).

    Thanks for the workaround though.

     
  • Mathias Gumz

    Mathias Gumz - 2015-01-21
    • Group: v1.3.5 --> future release
     
  • Mathias Gumz

    Mathias Gumz - 2015-01-21

    i can not reproduce it. which video-driver for xorg do you use?

     
  • Thomas Luebking

    Thomas Luebking - 2016-09-22
     
  • Thomas Luebking

    Thomas Luebking - 2016-09-22

    This happens because the server isn't grabbed and depends on how the area/window behind the rubberband refreshes. This here looks a bit like the particular window anticipates an exposure event where there is none, but the XOR problem is systematic.
    Unfortunately refreshing the screen by enforcing an exposure event (on stopping moveresize) may (and will for most gtk+ clients) cause a visible flicker (unless composited)

     

Log in to post a comment.