On 11/2/07, Szabolcs Nagy <[EMAIL PROTECTED]> wrote: > > On 11/2/07, Ritesh Kumar <[EMAIL PROTECTED]> wrote: > > The monocle layout implementation would have been simpler if focus(NULL) > was > > called in arrange() *before* layout[].arrange(). That would have ensured > > > that sel was correctly updated before the layout routine did its task. I > > would have been able to assume that sel == NULL => no windows to show in > > this view. > > > > What do you say Arg? Can you reorder the operations in focus() so that > > pancake and I don't have to replicate the "next selected window finding > > algorithm" in the layout routine? > > note that focus changes client order so > > focus(NULL); > layout->arrange(); > > is slighly different from > > layout->arrange(); > focus(NULL); > > > otherwise i agree, it's reasonable for arrange to know the focused window > > This is something that has been troubling me for some time... focus changes only the order of windows in the stack (the variable in dwm.c which keeps focus history) right? However, layout[].arrange() only use clients or nextclient(). How does using focus change the client order in the layout?
_r
