On Mon, 10 Oct 2005 17:49:39 -0400 Alex Viskovatoff <[EMAIL PROTECTED]> babbled:
> Hi all, > > I updated e from CVS yesterday, and am very pleased indeed. But I have > run into one annoyance. Previously, clicking the middle mouse button on > a window's titlebar would send the window to a lower layer (as described > at http://get-e.org/User_Guide). But now this action shades the window, > something which double clicking with the first mouse button also does. people kept asking for it - so the default bindings were changed. these bindings are configurable with the new signal bindings (see enlightenment_remote). so you can define the actions for all the border elements, instead of the theme hard-coding them. > (I know that control-alt-down_arrow is supposed to send a window to the > bottom, but that doesn't always work, since often an application will > grab the relevant keyboard events from e.) no - that does always work - e grabs the key long before the app does - the problem is some weird focus thing where e actually gets thet keygrab, but gets a focus out event when u press it thus removing the focus from the window, BUT now since it doesnt know what window is focused, it cannto lower the window (it doesnt know what to lower). i've listed this in the bug list. it's kind of bizarre as to why it SOMETIMES happens (move mouse out and in - re-focusing the window and it will work properly). > The documentation at http://get-e.org/User_Guide indicates that > "enlightenment_remote -binding-mouse-add" should be able to restore the > earlier behavior, but I have been unable to get this to work. incorrect. mouse bindings cover the entire border and client - and bypass any widgets/gadgets there. their contexts is the entire object they are bound to (in this case u are thinking borders). > Specifically, enlightenment_remote states that opt1 (context) must be > one of "NONE UNKNOWN BORDER ZONE CONTAINER MANAGER MENU WINLIST POPUP > ANY". Thus, a window titlebar does not seem to be a valid context for > enlightenment_remote, which would mean, I think, that behavior when the > pointer is in the titlebar is not configurable (other than by modifying > the source code), something which would go against the documentation. (I > tried the options listed that seemed like they might possibly refer to a > window title bar, but none of that experimentation produced the desired > effect.) singal bindings :) > Thanks in advance for any help, > > Alex > > > ------------------------------------------------------- > This SF.Net email is sponsored by: > Power Architecture Resource Center: Free content, downloads, discussions, > and more. http://solutions.newsforge.com/ibmarch.tmpl > _______________________________________________ > enlightenment-users mailing list > [email protected] > https://lists.sourceforge.net/lists/listinfo/enlightenment-users > -- ------------- Codito, ergo sum - "I code, therefore I am" -------------- The Rasterman (Carsten Haitzler) [EMAIL PROTECTED] 裸好多 [EMAIL PROTECTED] Tokyo, Japan (東京 日本) ------------------------------------------------------- This SF.Net email is sponsored by: Power Architecture Resource Center: Free content, downloads, discussions, and more. http://solutions.newsforge.com/ibmarch.tmpl _______________________________________________ enlightenment-users mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/enlightenment-users
