summaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorMichael Cardell Widerkrantz <mc@hack.org>2011-02-07 22:36:18 +0100
committerMichael Cardell Widerkrantz <mc@hack.org>2011-02-07 22:36:18 +0100
commit48e53c7b77ed55003ab5ef15da254da5e4c30fcb (patch)
tree7b1d22aeb5ba0cc92cf35ef75ffa3eb5ee2d3094
parent01799f4774e678135d7f86ba5ac461b66302a79e (diff)
downloadmcwm-48e53c7b77ed55003ab5ef15da254da5e4c30fcb.zip
Added a few ideas.
-rw-r--r--TODO24
1 files changed, 17 insertions, 7 deletions
diff --git a/TODO b/TODO
index bb3a766..33e53a7 100644
--- a/TODO
+++ b/TODO
@@ -5,10 +5,11 @@
When physical screens change, reset sense of maximum, virtmax et
cetera.
-* Grab keys specifically
+* Grab specific keys
- Current code grabs modifier keys and any other keypress. Need to
- specifically grab keys we need to work OK with xbindkeys.
+ Current code grabs modifier keys and any other keypress. We need to
+ specifically grab the keycodes we need. xbindkeys and possibly other
+ programs don't work.
* MappingNotify
@@ -33,8 +34,9 @@
around them in a simple window ring.
We need to re-arrange the list so the last focused window gets to be
- the next in ring. Perhaps simply move the focused window to head of
- list after finishing focusing? How do we know when we're finished
+ the next in ring. Perhaps just change direction in the list? Needs
+ double linked list... Perhaps simply move the focused window to head
+ of list after finishing focusing? How do we know when we're finished
and have the focus we want? Both Tab and Mod2 are released. Use a
mode?
@@ -79,9 +81,9 @@
* Gaps on borders for docks, status windows et cetera.
- Keep space reserverd for Conky, dzen2 et cetera.
+ Keep space reserved for Conky, dzen2 et cetera.
- Also handle EWMH hints _NET_WM_TYPE_DOCK and _NET_WM_TYPE_DESKTOP.
+ Also respect EWMH hints _NET_WM_TYPE_DOCK and _NET_WM_TYPE_DESKTOP.
* Flag to disable dontmoveoff?
@@ -102,6 +104,10 @@
How do we handle window moves from one screen to another. Should we
snap to the physical screen's edge and then allow move to continue?
+ An idea from Christian: Use a huge virtual screen and make physical
+ screens map to it. Perhaps we can actually manage to have a window
+ on two physical screens at once?
+
* Key to move pointer to another physical screen.
* Use xcb-event's event handlers?
@@ -127,3 +133,7 @@
focused window...
And a few others.
+
+* Use bitfields instead of extra lists for virtual screens?
+
+* Dispatch table for key bindings instead of keysym->enum->case?