[clfswm-devel] Stuck in window swap mode

[Philippe Brochard]

Duncan McGreggor writes:

> On Tue, Nov 27, 2012 at 9:31 PM, Ales Guzik <ales.guzik at gmail.com> wrote:
>
>     Hi Duncan.
>
>     Welcome to the list!
>
Hi Duncan, welcome too.

>
> Thanks, Ales!
>  
>
>     If I correctly understood what happens, than it might be expected
>     behaviour. If you set change layout and answer "No" to "Keep frame children
>     position?", than clicking child frame rearranges frames in such a way that
>     clicked frame becomes the first. Clicks inside first (usually top left)
>     frame should work as expected (be processed by target application). Just
>     answer "yes" when setting layout to avoid this behaviour.
>
>
> Bingo. You nailed it -- that was exactly what happened (just tried it out).
>
> It seems that the only "fix" is to go back to the layout menu, ask to tile, and
> then say "yes" to keeping the child positions. Is that the case? Or am I
> missing a short-cut somewhere?
>
No, you missed nothing. This is the default behaviour but I think it's
not appropriate. We'll revert to a more conventional child in fixed positions.

> Thanks again! I'm *really* enjoying clfswm ... looking forward to creating some
> blog posts and (hopefully) some buzz around it ;-)
>
Good to hear this! And thanks for the buzz :-)

Philippe

> d
>  
>
>
>     With best wishes,
>     Ales
>
>
>     On Wed, Nov 28, 2012 at 5:28 AM, Duncan McGreggor <duncan at cogitat.io>
>     wrote:
>
>         Hey folks,
>
>         I'm trying out clfswm for the first time today, and I've been loving
>         it. Quite impressive stuff. Thanks!
>
>         However, I have run into the same problem twice now... I must have
>         clicked some key-combination by accident. Right now, whenever I click
>         (right or left) with the mouse on the primary window in a frame, it
>         swaps out with another window (rotates through the windows of that
>         frame).
>
>         The first time I did this, I ended up killing X and starting over. Now
>         that it's happened again, I really need to figure out how to get out of
>         this state (and perhaps avoid getting into it by accident!).
>
>         As you might imagine, this has made using clfswm rather awkward ;-) 
>
>         Thanks for your help,
>
>         d
>
>
>         _______________________________________________
>         clfswm-devel mailing list
>         clfswm-devel at common-lisp.net
>         http://lists.common-lisp.net/cgi-bin/mailman/listinfo/clfswm-devel
>
>
>    
>
>
>     --
>      Ales Guzik <me at aguzik.net>
>      skype: ales-guzik
>      tel: +375 29 5751103
>    
>     _______________________________________________
>     clfswm-devel mailing list
>     clfswm-devel at common-lisp.net
>     http://lists.common-lisp.net/cgi-bin/mailman/listinfo/clfswm-devel
>
>
>
> _______________________________________________
> clfswm-devel mailing list
> clfswm-devel at common-lisp.net
> http://lists.common-lisp.net/cgi-bin/mailman/listinfo/clfswm-devel