to work well. grabs buttons. responds to input events and context. calls
appropriate action callbacks. you can add actions fairly easily. the cool bit
is that actions can be added on the fly... like ooh - lets say from...
MODULES :) ie module could load and enable then add lots of custom actions.
these could be custom in c code in the module.. OR... they could even be bits
of embryo loaded ... or perl... or python... or... anyway - you can figure it
out. it's justa bi-product of doing the action system this way. (btw - the
actions can be overridden too by modules so a module could change a default
action or even just augment it...)
SVN revision: 14495
support shading in other directions
support other transition types for shade animation (default is DECELERATE)
simplify some logic in _e_border_eval()
SVN revision: 12529