summaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorMichael Cardell Widerkrantz <mc@hack.org>2011-03-04 14:23:47 +0100
committerMichael Cardell Widerkrantz <mc@hack.org>2011-03-08 12:14:38 +0100
commit0c99c2a608283603238943147cff341ae7629514 (patch)
tree09e0f86dabf4f1ff3bffed404c1d3606edb9d2ae
parent976951dfeb0f36f5ba2c86ade574cff4b64ea8c7 (diff)
downloadmcwm-0c99c2a608283603238943147cff341ae7629514.zip
*** empty log message ***
-rw-r--r--TODO28
1 files changed, 19 insertions, 9 deletions
diff --git a/TODO b/TODO
index ca4264e..ddaaf1b 100644
--- a/TODO
+++ b/TODO
@@ -30,20 +30,26 @@
I would like it to work like this: modkey-Tab-Tab-Tab... Release
modkey to focus on a window *and* to remember the window where we
- started. The window we remember would be moved to the next position
- in the window list.
+ started.
This will also need to work if the change focus with the mouse.
- A single modkey-Tab would then get the focus to end up in the window where
- we started tabbing or where we last had our focus if changing with
- the mouse.
+ A single modkey-Tab would then get the focus to end up in the window
+ where we started tabbing or where we last had our focus if changing
+ with the mouse.
- This is done, but in a bit ugly way. I have bound Alt_L explicitly
- and looking for key release events.
+ This is now implemented like this:
- It is possible to ask for what keys give XCB_MOD_MASK_4 or whatever
- MODKEY is.
+ Always keep the current window as the first element in the current
+ workspace window list. Always keep the window we focused before it
+ as the second element.
+
+ When we focus on the next window from the current one, the first
+ Tab always goes to the window we had focus in before.
+
+ I have bound Alt_L explicitly and looking for key release events.
+ This is a bit ugly. It is possible to ask for what keys give
+ XCB_MOD_MASK_4 or whatever MODKEY is.
GetModifierMapping
@@ -73,6 +79,10 @@
How do we re-establish stack order after moving around windows to
focus on? Do we want to?
+ There is a bug when we change from one ws to another and focuswin
+ doesn't get reset. That is, focuswin isn't NULL but the
+ focuswin->wsitem[curws] is empty.
+
* Virtual screens/workspaces
Partially done. Still needed: