Hello,
static void
_ecore_coroutine_setjmp(Ecore_Coroutine *coro)
{
setjmp(coro->context);
/* The idea of this trick come from libcoroutine */
/* __jmpbuf[6] == stack pointer */
/* __jmpbuf[7] == program counter */
self->env[0].__jmpbuf[6] = ((uintptr_t)(&coro->stack));
self->en
Hello,
I traced my module loader and I get in eina_module_new in line
at DBG("m=%p, file=%s", m, file);
this output:
m=0x5115eb20, file=eina_module_new
and in eina_module_load(Eina_Module *m)
at DBG("m=%p, handle=%p, file=%s, refs=%d", m, m->handle, m->file,
m->ref);
m=0x5115eb10, handle=0x5
Another thing that can be done is a dumb repository using git submodule
:
$ git init /var/tmp/e-core
$ cd /var/tmp/e-core
$ git submodule add http://git.enlightenment.org/core/efl.git/ efl
$ git submodule add http://git.enlightenment.org/core/elementary.git/
elementary
$ git submodule add ht
tl;dr:
To have a sub-ecore_evas inside the wayland ecore_evas. The
sub-ecore_evas would handle the client area content, while the
ecore_evas (external one) would handle the rendering of the window
decorations.
How it should work:
==
Once one asks for a wayland ecore evas (ecore_
On Wed, Feb 27, 2013 at 11:44 AM, Tom Hacohen wrote:
> On 27/02/13 14:38, Rafael Antognolli wrote:
>> What about requiring push -f?
>
> Do you know how to do that? I'd love having that.
If git >= 1.6 is running on the server, all you need to do is set the
configuration:
receive.denyNonFastForwar
Hi Cedric,
Cedric BAIL writes:
> I now understand your problem. I still have a few question. What
> happen if you rotate an edje object with a GROUP part that has an
> animated text in that group. My guess looking at the code is that it
> wont work also.
>
> I also think that if you change the f
On 27/02/13 22:41, Cedric BAIL wrote:
> On Wed, Feb 27, 2013 at 3:04 PM, Tom Hacohen wrote:
>> $ elementary_test "File Selector"
>> Segmentation fault (core dumped)
>
> Shouldn't you add a task to phab for that ?
>
Don't know, as it's not a bug, it's a daily thing. Master breaks a few
times a da
Hi,
Gustavo Sverzut Barbieri writes:
> That may be another bug, we did not test but the current patch indeed
> fixes the problem, discarding the previous surface sooner than later.
>
> If you want another function, there is no need to mark it as
> dirty/changed, just isolate the mapped surface c
Hi Cedric,
That may be another bug, we did not test but the current patch indeed
fixes the problem, discarding the previous surface sooner than later.
If you want another function, there is no need to mark it as
dirty/changed, just isolate the mapped surface cleanup code into a
function, call it
