Limiting which desks are cycled through while 'alt+tab'-ing

Configuration General Questions
1

All:

I have mapped the ‘ALT+TAB’ functionality to F1 using the following code:

[code]Key F1 A A FuncFocusNextWindow

DestroyFunc FuncFocusNextWindow
AddToFunc FuncFocusNextWindow

  • I Next (!CurrentPage, AcceptsFocus) FlipFocus [/code]

Is there somthing that I can add to that code to be able to specify which desks will be visible while paging (say, desks 1-5) and disallow desks 6-7 from being visible when ‘alt_tab’-ing…

I want some apps to just run in the background, and not have to cycle through them every time…

I know, it’s a lame question, but I really would like that functionality.

Thanks in advance,
Jared

2

Not easily. I suppose you could do something like this:

Key F1 A A FuncFocusNextWindow

DestroyFunc FuncFocusNextWindow
AddToFunc FuncFocusNextWindow
+ I PipeRead '[ "$[desk.n]" == "6" -o "$[desk.n]" == "7" ] && echo Nop || echo "Next (!CurrentPage, AcceptsFocus) FlipFocus"'

Play about with it, and see what you get.

– Thomas Adam

3

You could use
Style <bg_appname> Layer

And use with WindowList:
Layer
Where m is the minimum layer, n maximum of displayed layers.

Other, more simple solution:
Style <bg_appname> WindowlistSkip
Or is it CirculateSkip?

4

You could, but this would affect the way applications are started, from the DefaultLayer, which may or may not be an issue. And even then, that still won’t address the issue of seeing the window, if it is on desk 6, for instance.

You were right the first time. WindowListSkip is what is used for various modules not to consider the window to be displayed. CirculateHit is similar to windowlistskip, but instead this affects whether the window is to be seen with conditional commands, such as: Next, etc.

– Thomas Adam