On Tue, Oct 25, 2016 at 01:59:46AM +0100, Thomas Adam wrote: > On Tue, Oct 25, 2016 at 01:42:58AM +0100, Thomas Adam wrote: > > On Tue, Oct 25, 2016 at 01:34:57AM +0100, Dominik Vogt wrote: > > > I fear this commit is too disruptive. Aggregating Expose events > > > is very important to deal with race conditions cause by > > > applications doing crazy stuff. Is there some explanation of the > > > problem that was fixed with this commit? I'd like to revisit it > > > and see what needs to be done with the aggregation code to fix it > > > without completely removing it. Probably it just needs to stop > > > aggregating more often. > > > > It was to do with icons not being redrawn with moving one icon over another > > when using ParentRelative (transparent icons). The icons would leave > > artefacts and never refresh. > > > > I can't find the original thread in the archives but I know there is one. > > Because it was posted on GH. Here's the issue: > > https://github.com/fvwmorg/fvwm/issues/11 > > That's all the information you'll need.
Thanks. I'll take a look at the bug. Ciao Dominik ^_^ ^_^ -- Dominik Vogt
