On Friday, 02 July 2010, at 01:31:13 (-0700),
Enlightenment SVN wrote:
> Log:
> Don't check alloca, it's like checking the stack exists.
It can't fail on *GNU* libc, but there's nothing in the standard that
stops it from returning NULL on stack overflow. In fact, the man page
implies that othe
On Fri, Jul 2, 2010 at 11:17 AM, Cedric BAIL wrote:
> On Fri, Jul 2, 2010 at 3:44 PM, Gustavo Sverzut Barbieri
> wrote:
>> On Fri, Jul 2, 2010 at 8:17 AM, Enlightenment SVN
>> wrote:
>>> Log:
>>> * ephoto: use ecore_long_run instead of idler to do async blocking
>>> IO.
>>>
>>> Author:
Do not kill me, my vim is stupid :(
2010/7/2 Enlightenment SVN
> Log:
> Fix research with Alias
>
>
> Author: watchwolf
> Date: 2010-07-02 11:17:37 -0700 (Fri, 02 Jul 2010)
> New Revision: 50003
>
> Modified:
> trunk/edje/src/lib/edje_util.c
>
> Modified: trunk/edje/src/lib/edje
On Fri, Jul 2, 2010 at 5:05 PM, Rafael Fonseca wrote:
> If you create an edc file with the two following styles:
>
> styles {
> style {
> base: "foo";
> }
> style {
> name: "bar";
> base: "foo2";
> }
> }
>
> edje_cc would SEGV when comparing whether the second styl
If you create an edc file with the two following styles:
styles {
style {
base: "foo";
}
style {
name: "bar";
base: "foo2";
}
}
edje_cc would SEGV when comparing whether the second style's name is
equal to the previous one.
The attached patch avoids tha
On Fri, Jul 2, 2010 at 3:34 PM, Gustavo Sverzut Barbieri
wrote:
> On Fri, Jul 2, 2010 at 8:15 AM, Enlightenment SVN
> wrote:
>> Log:
>> * ecore: fix long run thread, now that I have a nice user.
>
> Would you mind writing the docs with what each callback does, where
> each function runs (m
On Fri, Jul 2, 2010 at 3:44 PM, Gustavo Sverzut Barbieri
wrote:
> On Fri, Jul 2, 2010 at 8:17 AM, Enlightenment SVN
> wrote:
>> Log:
>> * ephoto: use ecore_long_run instead of idler to do async blocking IO.
>>
>> Author: cedric
>> Date: 2010-07-02 04:17:59 -0700 (Fri, 02 Jul
On Fri, Jul 2, 2010 at 8:15 AM, Enlightenment SVN
wrote:
> Log:
> * ecore: fix long run thread, now that I have a nice user.
Hi Cedric,
Would you mind writing the docs with what each callback does, where
each function runs (main/ecore thread, worker thread) and the
difference between ecor
On Thu, Jul 1, 2010 at 9:44 PM, Enlightenment SVN
wrote:
> Log:
> Not pure, don't need to care about results.
>
> Code with side effects is NOT pure. Cdoe where you can ignore the return
> value because you care about the side effects should not have WARN_UNUSED...
> Please only add such thin
On Fri, Jul 2, 2010 at 8:17 AM, Enlightenment SVN
wrote:
> Log:
> * ephoto: use ecore_long_run instead of idler to do async blocking IO.
>
> Author: cedric
> Date: 2010-07-02 04:17:59 -0700 (Fri, 02 Jul 2010)
> New Revision: 49995
>
> Modified:
> trunk/ephoto/src/bin/ephoto_t
On Fri, Jul 2, 2010 at 12:40 AM, Christopher Michael
wrote:
> On 07/01/2010 08:49 PM, Iván Briano (Sachiel) wrote:
>>
>> On Thu, Jul 1, 2010 at 9:35 PM, Christopher Michael
>> wrote:
>>>
>>> On 07/01/2010 10:32 AM, Iván Briano (Sachiel) wrote:
On Thu, Jul 1, 2010 at 6:46 AM, michael bo
Hey Andreas,
nice idea with the eooorg module. What you forgot: Once an openoffice window
has beend opened and closed, the prestarted instance will end too.
So next time you start openoffice you will get the splash screen again.
The module needs to check if the prestarted instance is still runnin
On Fri, Jul 2, 2010 at 08:41, Vincent Torri wrote:
>
>
> On Thu, 1 Jul 2010, Gustavo Sverzut Barbieri wrote:
>
>> On Thu, Jul 1, 2010 at 3:44 PM, Matthew Robbetts
>> wrote:
>>> I'm trying to rebuild E17 from the current Gentoo overlay and the build
>>> process fails during when building epdf. It
On Fri, 2 Jul 2010, Thomas Gstädtner wrote:
On Fri, Jul 2, 2010 at 08:41, Vincent Torri wrote:
On Thu, 1 Jul 2010, Gustavo Sverzut Barbieri wrote:
On Thu, Jul 1, 2010 at 3:44 PM, Matthew Robbetts wrote:
I'm trying to rebuild E17 from the current Gentoo overlay and the build
process fai
On Fri, Jul 2, 2010 at 10:46 AM, Atton Jonathan
wrote:
> Yes but I wish to find the part without using the complete name
> ("tools[plop]:object name"). This way the designer can add the part in a box
> or not.
All code refering to part in edje use the same recursive code and
should be able to cor
Yes but I wish to find the part without using the complete name
("tools[plop]:object name"). This way the designer can add the part in a box
or not.
2010/7/2 Boris 'billiob' Faure
> On Fri, Jul 2, 2010 at 10:35, Atton Jonathan
> wrote:
> > I plan to update edje_object_part_external_object_get()
On Fri, Jul 2, 2010 at 10:35, Atton Jonathan wrote:
> I plan to update edje_object_part_external_object_get() and add the research
> in boxs. Is it ok for you ?
It's already the case!
I've coded it then Cedric improved it.
Ps: it also works for tables
--
Boris 'billiob' Faure
-
I plan to update edje_object_part_external_object_get() and add the research
in boxs. Is it ok for you ?
2010/7/1 Atton Jonathan
> hello,
>
> How can I retrieve a external object which is in a edje box by using the
> name of the object ?
>
> A simple example :
>
>
> part {
> name: "tools";
On Thu, Jul 1, 2010 at 8:28 PM, Boris 'billiob' Faure wrote:
> On Thu, Jul 1, 2010 at 20:22, Atton Jonathan wrote:
>> hello,
>>
>> How can I retrieve a external object which is in a edje box by using the
>> name of the object ?
>>
>> A simple example :
>>
>>
>> part {
>> name: "tools";
>>
19 matches
Mail list logo
