try and highlight focus better with a window wobble to make it easier
to know what is focused. it's fairly small and unobtrusive but a hint
as to what just got focused when alt-tabbing around etc.
if efreet updates its in memory db of themes/icons etc. the ptrs you
get from it will be invalid. always dup them out if you keep them
around after going back to main loop control. in this case a tiny
possible leak in stringshare won't ever matter... sot his fixes it
@fix
we don't get synthetic configurenotifies for positiomn which we SHOULD
get from a wm when a wm places us on screen... this broke efl
rendering as it would block rendering until we were told by the wm
"you have been placed here" which should always happen.
this works around this b0rkage in xwayland land.
@fix
we don't get synthetic configurenotifies for positiomn which we SHOULD
get from a wm when a wm places us on screen... this broke efl
rendering as it would block rendering until we were told by the wm
"you have been placed here" which should always happen.
this works around this b0rkage in xwayland land.
@fix
These are typically not required for an end-user unless they are
coding something, in which case if they want the examples they can
pass a build option for that
openssl3 should now solve licensing issues with openssl. there is no
good reason to keep gnutls support anymore especially since there just
isn't anyoen who wants to maintain that extra ifdef'd code (and that
code has some gotchas that don't match the full features of openssl
too). so this removed "code cruft" to maintain, complexity and
maintenance work as well as build complexity.
this is bad but it's necessary. need to make the htextblock accept
events so links can be put in it. this then also requires it become
editable to support anchors and items which are needed for
notification links and inline images.
since this has to break nayway, embrace the break and add action box
swallow - and action buttons. the action buttons will probably need a
swallow added for icons still - but debating that still.
@fix / break / feat
sometimes on some systems and drviers time here is not what we
want/expect. it can be in the future. there are reasons so, work
around this and use the timestamp of "now" when we get the event as
opposed to the timestamp given to work around odd weirdnesses and
complaints time went backwards.
@fix