| Commit message (Collapse) | Author | Age | Files | Lines |
|---|
| | |
|
| | |
|
| | |
|
| | |
|
| |
|
|
| |
parameter
|
| |
|
|
|
|
| |
- add page size option (fill)
- add default behavior without transition
- change page geometry's base from pager itself to a part of the layout
|
| |
|
|
|
|
| |
- destructor -> invalidate
- animator-> event_callback
- extract common codes into functions
|
| | |
|
| | |
|
| | |
|
| | |
|
| |
|
|
|
|
| |
- remove redundant loops
- remove unnecessary lines
- use struct rectangle instead of pointer
|
| | |
|
| | |
|
| | |
|
| |
|
|
| |
add more test case
|
| |
|
|
|
|
|
|
| |
- can move more than one pages at a time
- accept mouse down while animating
- event propagate
- implement efl_pack_linear functions
- many bug fixes... (...and still buggy)
|
| |
|
|
| |
applied feedback in https://phab.enlightenment.org/D5430
|
| | |
|
| |
|
|
| |
applied feedback in https://phab.enlightenment.org/D5430
|
| | |
|
| | |
|
| |
|
|
|
|
|
| |
The value must be given to eina_value_set and not a pointer to a
Eina_Value.
This bug results in always getting wrong exit code when the application
terminates.
|
| |
|
|
|
|
|
|
|
|
|
|
| |
Added 4 buttons to the "genlist group tree" to perform
item next/prev/first/last.
This test works correctly by reverting fd82c2521ebb but it
still in contrast with the item_next() docs, that say item_next
should not descend in item childs.
I think that the docs is also wrong, as I never saw the behaviour
that is explained there.
|
| |
|
|
|
|
| |
Clean up various places where we do flushes that we don't need to
because some immediately following action is going to cause a flush.
Also fix places where we flush without actually doing anything.
|
| |
|
|
|
| |
If input and opaque region are the same (they usually are) we can use
the same region for both.
|
| |
|
|
| |
Trivial refactor
|
| |
|
|
|
|
|
|
| |
False commit when a commit is already pending is an error, but for safety
it should be a nop.
Currently it would overwrite the existing frame callback which could
cause problems on window destruction.
|
| |
|
|
|
| |
These just protect against caller stupidity. Double register or double
unregister shouldn't happen anyway.
|
| |
|
|
|
|
| |
We should be using dmabuf sync ioctls instead of mmap/munmap every draw,
this makes that happen. The surface code continues to do what its always
done, and map/unlock.
|
| |
|
|
|
| |
Should never double lock or double unlock, this isn't refcounted, and
probably doesn't need to be.
|
| |
|
|
|
| |
These should help with coherency later when we don't unmap for every
surface post.
|
| |
|
|
| |
For backend specific lock/unlock behaviour
|
| |
|
|
| |
Currently we're making mapping implicitly take a lock.
|
| |
|
|
|
| |
This stuff is all in the wayland ecore_evas now, so elm no longer needs
to handle it.
|
| |
|
|
| |
This isn't necessary anymore as ecore_evas handles it internally now.
|
| |
|
|
|
|
| |
This is now done in ecore_evas where it should be. alpha_set now does
only what its name claims it does - sets whether a surface has an alpha
channel or not.
|
| |
|
|
|
|
| |
Instead of having elm handle all this stuff, handle it in ee. This fixes
a loooong standing bug where we would always use an alpha enabled surface
because CSD needs shadows - even if we aren't drawing CSD.
|
| |
|
|
| |
Instead of depending on the backend figuring it out.
|
| |
|
|
|
| |
This allows software renderers to reconfigure their buffers to actually
change whether alpha is present.
|
| |
|
|
|
| |
This is exactly the same as alpha_set, so it really doesn't have much
reason to exist.
|
| |
|
|
|
| |
transparent_set is a legacy path that should do exactly what alpha_set
does these days, so squash them into the same function.
|
| |
|
|
| |
It's no longer used.
|
| |
|
|
|
| |
We don't need this because we calculate it in ecore_evas from the shadow
value and framespace.
|
| |
|
|
| |
Instead of using wdata->content, calculate these values.
|
| |
|
|
|
|
|
| |
When alpha changes we need to blow away all our buffers in reconfigure,
even if they're still the right dimensions. Otherwise we can end up
rendering to an XRGB buffer when we wanted to use ARGB and we won't have
proper transparency.
|
| |
|
|
| |
We'll need this for some surface modules to properly handle alpha changes
|
| |
|
|
|
| |
Currently we only ever make wayland windows with alpha, this is a step
towards changing that.
|
| |
|
|
|
|
|
|
|
| |
Since we don't actually set the color depth at all we can end up with
an RGB565 buffer. We don't ask for depths because apparently the N900
had a problem with this under X.
I'm not aware of any efforts to bring wayland to the N900, so let's do
this normally.
|
| |
|
|
|
| |
This will be used from validation to properly count actual
dependencies of a unit.
|
