Re: Issue 4 in xmonad: Separate focus for tiled and floating layers

Comment #34 on issue 4 by vogt.adam: Separate focus for tiled and floating layers http://code.google.com/p/xmonad/issues/detail?id=4 I see how TrackFloating is still unsatisfactory. Perhaps xmonad (and the modified layout) focus should be modified only when focus goes to tiled due to a window disappearing, and for crossing events: (CrossingEvent {ev_window=w, ev_event_type=t, ev_mode=m}) | t == enterNotify, m == notifyNormal = Modifying xmonad focus from a layout is tricky, since it's difficult to know that infinite loops of refreshing can not occur. Splitting it up as layout and eventHook may be simpler.

Comment #35 on issue 4 by wirtwo...@gmail.com: Separate focus for tiled and floating layers http://code.google.com/p/xmonad/issues/detail?id=4 Issue 465 has been merged into this issue.

Comment #36 on issue 4 by eg1...@gmail.com: Separate focus for tiled and floating layers http://code.google.com/p/xmonad/issues/detail?id=4 Why don't we split what ever variable inside xmonad that tracks focus into two, a "trueFocus" and a "tiledFocus", for example? One for use in layouts like max and tabbed that use focus to determine layout, and one for use in determining within XMonad where text entry goes and where to draw the active border and such. Change "trueFocus" everywhere you used to change "focus" and if you're changing "trueFocus" to a tiled window change "tiledFocus" too. (Disclaimer: I know nothing about the Xmonad source, nor really much about haskell in general, so disregard my idea if I'm totally off base.)

Comment #37 on issue 4 by byor...@gmail.com: Separate focus for tiled and floating layers http://code.google.com/p/xmonad/issues/detail?id=4 It is not this simple. There is not a simple variable that tracks which window is focused. The focus is implicit in the way the StackSet data structure is organized. That's why this ticket has languished so long --- implementing it would really require a quite invasive restructuring of xmonad's core data structures.
participants (1)
-
codesite-noreply@google.com