| Age | Commit message (Collapse) | Author |
|---|
|
This may be a bit more controversial...
But Evas_Coord really is just an int and all the internals
of EFL assume that the base coordinate type is a 32-bit int.
So this type is a bit redondant and can't easily be changed
to, say, a float or int64.
Ref T5312
|
|
We only need it in elm_config.
This removes the type Evas_Font_Hinting_Flags from EO,
as well as the functions font_hinting_set/get and
font_hinting_can_hint.
Ref T5312
|
|
Note: it seems the EAPI evas_touch_point_list_xy_get() was
lst at some point, as it doesn't appear in the headers anymore.
It looks like we fail to catch an ABI break! abi_checker didn't
catch this!?
Ref T5312
|
|
Ref T5312
|
|
Ref T5312
|
|
This makes photocam implement Efl.Flipable and Efl.Orientation
in order to use the proper API.
image_orient is now split into two function calls.
Ref T5312
|
|
Those are legacy only.
Ref T5312
|
|
This moves the enum to legacy only, but in Evas_Common.h and not
Evas_Legacy.h because some other legacy things are in Evas_Common.h
Ref T5312
|
|
It is an internal only API.
Ref T5312 (one less use of a legacy type)
|
|
It belongs to legacy only... Evas.Text is not part of EO.
Ref T5312
|
|
Ref T5312
|
|
In trying to clean up some code and fix a hypothetical buffer leak, I added
a use after free error that can break rendering on the drm and gl_drm
evas engines.
Coverity did the heavy lifting for me on this one.
Fix Coverity CID 1375047
Fix T5484
|
|
I think this was intended as a reminder to do something that's already
been done. Or something.
|
|
Accessing an fb after discarding it is bad karma, so we should log something
if it ever happens.
|
|
Removes the previous "busy" flag, as now we might have an fb attached to
multiple outputs at once, and need to be careful to destroy them only
after they've been removed from all outputs.
Removed the old "busy_set" API which nothing used, and renames fb_destroy
to fb_discard to make it more clear that it's not immediately destroyed.
It's all beta api, so I can do this.
|
|
|
|
|
|
|
|
future theme developers.
|
|
in some cases (e.g,, x11 bridged selections) it is necessary to use
alternate means when transferring a selection, and so performing the
entire piped receive is not necessary. instead, extend the lifetime
of the data offer until the proxied receive has completed
@feature
|
|
in some cases it may be desired to have a drag data source without ever
initiating a drag, so ensure that it's possible to set the actions of the
source which will be passed for drag operations in this case
@feature
|
|
@feature
|
|
this seems to have been done to account for the case where no mimes were
passed, but sending null in this way is bad behavior for a client. the
spec indicates that null should be sent only when no mimes are accepted
@fix
|
|
@feature
|
|
it's impossible to know the result of a drag operation without this
member
|
|
this is required in order to determine which connection an event originated
from
|
|
|
|
seat id is required in order to handle multiseat environments
|
|
use serials of the selections and events to avoid mangling external selections
|
|
these allow apps to match the serial of their selection to the related
event in order to avoid mangling selections from other components
|
|
in the case where multiple places in an app may be handling selections, this
is necessary in order to manage the selections accurately
@feature
|
|
this can trigger in the case where a selection transfer occurs and
no input resource has received an enter (e.g., the window is not focused)
@fix
|
|
ensure lifetime of display object is longer than events in which
the object is passed
@fix
|
|
ensure this is not called on server displays
|
|
@fix
|
|
@feature
|
|
@feature
|
|
these are distinct objects and can coexist simultaneously; a drag
source should not overwrite an existing selection source
@fix
|
|
@feature
|
|
no display = invalid object, so this needs checking
|
|
in some cases (e.g., the mouse-out emission from the ee wl engine),
this was calculating wrong coordinates, which would lead to a broken
chain of events like:
object mouse out -> object mouse in -> object mouse out
which would severely break some apps
@fix
|
|
@feature
|
|
it's possible to set flags to 0 with another function, so allowing
creation with 0 makes the api more consistent without breaking the
documented behavior
|
|
setting this to only markup means that it's impossible to paste into
an elm_entry from a plaintext app under wayland
@fix
|
|
this is no longer necessary
|
|
ref 67fae7aa0fdc9d778e8db88fc49bc149576994d2
|
|
|
|
we haven't gotten replies yet on what our position or size should be,
so we should store them so centering works before show but after
resizing is evaluated (that also fixed by forcing an eval).
@fix
|
|
Summary:
This fixes a typo in the fix 55676b33, which introduced an invalid early
return from the save_list function, preventing it from outputing the
list data to the file.
@fix CID1375005, CID1375004
Reviewers: jpeg
Reviewed By: jpeg
Subscribers: stefan_schmidt, cedric, jpeg
Differential Revision: https://phab.enlightenment.org/D4873
|
|
Omg... Thanks Daekwang Ryu for pointing me to my error. I remember
struggling a lot with this OpenGL API and libGLdispatch (glvnd) when
in fact this was all just a typo in the code.
GLES 3.1 and the upcoming 3.2 support need a proper test case...
See c68a40987404375b36460b6a7f5ccceb45444b57
@fix
|
