The idea of copy and paste here is: - The user specifies the content he wants to have in the selection buffer with a Eina_Content, these content pointer ownerships are passed to the called. Internally ecore_evas code will memorieze the pointer, and pass on function callbacks to the modules, which then do not have to deal with the ownership. - In case the module does not specify these APIs, the callback implementation will be called, which only works for cnp *not* dnd. - Action and mime types are handled as strings, which allows way better custom organisations. (The docs needs improvement) Reviewed-by: Mike Blumenkrantz <michael.blumenkrantz@gmail.com> Differential Revision: https://phab.enlightenment.org/D11192 |
||
---|---|---|
.. | ||
benchmarks | ||
bin | ||
bindings | ||
edje_external | ||
examples | ||
generic | ||
lib | ||
modules | ||
scripts | ||
static_libs | ||
tests | ||
wayland_protocol |