I have added (in CVS) the possibilty to do actions on window events (at least enter/leave). This makes it possible to do the auto shade/unshade thing without having to modify all border parts and still not having it work properly.
Example based on winter/borders/PAGER/border.cfg:
__ACLASS __BGN __NAME ACTION_AUTOSHADE __TYPE __TYPE_NORMAL __EVENT __MOUSE_ENTER __ACTION __A_SHADE off __NEXT_ACTION __EVENT __MOUSE_LEAVE __ACTION __A_SHADE on __END
__BORDER __BGN __NAME PAGER __BORDER_GROUP_NAME PAGER_GROUP __BORDER_SIZE_LEFT 5 __BORDER_SIZE_RIGHT 19 __BORDER_SIZE_TOP 5 __BORDER_SIZE_BOTTOM 5 __SHADE_DIRECTION __LEFT __CHANGES_SHAPE __OFF __ACLASS ACTION_AUTOSHADE
/* 0 */
__BORDER_PART __BGN
__ICLASS PB1
...There can still be some glitches but it's quite useable.
/Kim
PLASSON Raphael wrote:
Hello,
This quite looks like what I had once tried (and didn't really succed) to do. What would be interesting, is to have a window that can be either in an unshaded state (i.e. behave like a common window) or a "semi-shaded" state, that is: - It is shaded if it doesn't have the focus - It is automatically unshaded when it get the focus (e.g. when the mouse is on it) - It is automatically shaded when it loses the focus (e.g. when the mouse leave it)
It should be very useful for windows that are often used, but for a short length each time. Typically: the pager, configuration "sub-windows" (for software like Gimp, Grace, etc.), launchers... Actually, this is just the ability to apply an "auto-hide"-like behavior, like gnome or KDE taskbar, to any window.
What I had tried to do was to modify the theme border of a window, so that each time the mouse enter on one of the border of the considered window (__EVENT __MOUSE_ENTER for every border element), the shade state is toggled (__ACTION __A_SHADE). It may have worked quite well, as each time the mouse goes into the window, it has to enter one border (then unshade), and when it leave the window, it has to enter again in one border (then shade). However, there was many drawbacks I couldn't manage to avoid: If the mouse moves to quickly, the toggle state may not be taken into account, if the mouse just touch the border but not enter the window, the shade behavior was reversed, if the window is partly hidden by another one, the mouse can leave the window without entering any border, etc...
Would there be any elegant solution to solve this problem ? Is there a "__GET/LOSE__FOCUS" event available for window configuration in E (I think I didn't manage to find it the last time I conigured my own theme, but things seems to evolve fast since the E16.7.x series) ?
-------------------------------------------------------
SF email is sponsored by - The IT Product Guide
Read honest & candid reviews on hundreds of IT Products from real users.
Discover which products truly live up to the hype. Start reading now. http://productguide.itmanagersjournal.com/
_______________________________________________
enlightenment-users mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/enlightenment-users
