On 10 July 2011 03:39, Peter Hartlich wrote:
>> To prevent the first restack, maybe something like the attached patch?
>
> ... which causes the title bar to flicker, as restack calls drawbar
> before bailing out. Not sure why that's needed.
I reverted your map modifications in the 5.9 release. I
> To prevent the first restack, maybe something like the attached patch?
... which causes the title bar to flicker, as restack calls drawbar
before bailing out. Not sure why that's needed.
Peter
> just one annoying issue with floating apps. eg. running save as in gimp,
> will open a window in the background.
Oh man, sorry. I should've tested it more with floating windows.
So arrange calls arrangemon, which calls restack, but the new floating
window hasn't become selmon->sel yet.
Restack
On Sat, Jul 9, 2011 at 10:01, garbeam wrote:
> Hi Peter,
>
> On 9 July 2011 00:40, Peter Hartlich wrote:
> >> I reviewed your patch and concluded I can't apply it as is, because
> >> focus() would be called twice, once on the unmapped window, and then
> >> on again.
> >
> > It seems to me that f
Hi Peter,
On 9 July 2011 00:40, Peter Hartlich wrote:
>> I reviewed your patch and concluded I can't apply it as is, because
>> focus() would be called twice, once on the unmapped window, and then
>> on again.
>
> It seems to me that focusing and arranging should be independent
> operations. So h
Hi Anselm,
> I reviewed your patch and concluded I can't apply it as is, because
> focus() would be called twice, once on the unmapped window, and then
> on again.
It seems to me that focusing and arranging should be independent
operations. So here comes another patch to remove focus(NULL) from
a
Hi Peter,
I reviewed your patch and concluded I can't apply it as is, because
focus() would be called twice, once on the unmapped window, and then
on again.
I'm thinking about modifying your patch to avoid this.
Cheers,
garbeam
PS: On Sunday there is dwm's official 5th birthday and I consider
d
Hi Peter,
On 6 July 2011 23:15, Peter Hartlich wrote:
> Couldn't dwm map newly created windows *after* they have been moved
> to their proper position? Less flickering (especially noticeable with
> the attachabove/attachaside patches), and it feels snappier on a slow
> computer.
>
> I haven't exp
Couldn't dwm map newly created windows *after* they have been moved
to their proper position? Less flickering (especially noticeable with
the attachabove/attachaside patches), and it feels snappier on a slow
computer.
I haven't experienced any problems with the attached patch so far.
Peter
diff -
