From: Philipp H. <ph...@ph...> - 2013-01-03 13:04:17
|
Hi, > I keep seeing incorrect behaviors in the focusing behavior of notion, and it > finally bothered me enough to look into it. I have > > warp = false > mousefocus = sloppy > > I used (not)ion for years with warp = true, and the focusing was much more > correct with that setting, for what it's worth. In the rest of this message I'm > assuming that the right focusing behavior with those settings is > > The window beneath the mouse pointer should have focus, unless the pointer is > currently grabbed by a different window. > > If this underlying premise isn't right, maybe the following doesn't apply. it's not correct I'm afraid: You can always switch the focus away from the pointer using the keyboard. The pointer only influences the focus when it is moved. In particular I consider the two "failure modes" that you describe to be essential features. Especially the second one: when I switch my browser into fullscreen mode, maybe do something with the mouse and then switch back, I absolutely want the focus to remain on my browser, no matter where I've moved the pointer. Anything else would drive me insane within seconds. > Questions: > > Why kpress_wait() in the sample config file? Would kpress() suffice? Why > kpress_wait() for anything? I couldn't find any description anywhere about what > kpress_wait() does and why one may want to use it. The role of kpress_wait is explained in http://notion.sourceforge.net/notionconf/node4.html#SECTION00433000000000000000 Whether one wants to use it for toggling fullscreen may be debatable, but it's at least not completely unreasonable. Cheers, Philipp |