On Tue, 4 Sep 2007 13:23:51 +0200 Simon TRENY <[EMAIL PROTECTED]> babbled:
> On Sat, 25 Aug 2007 12:41:02 +0900,
> Carsten Haitzler (The Rasterman) <[EMAIL PROTECTED]> wrote :
>
> > On Tue, 21 Aug 2007 00:58:58 +0200 Simon TRENY <[EMAIL PROTECTED]>
> > babbled:
> >
> > > Hi,
> > >
> > > I've se
On Sat, 25 Aug 2007 12:41:02 +0900,
Carsten Haitzler (The Rasterman) <[EMAIL PROTECTED]> wrote :
> On Tue, 21 Aug 2007 00:58:58 +0200 Simon TRENY <[EMAIL PROTECTED]>
> babbled:
>
> > Hi,
> >
> > I've seen in Evas.h that most of the methods of Evas_Smart_Class are
> > marked as to-be-deleted in t
On Tue, 21 Aug 2007 00:58:58 +0200 Simon TRENY <[EMAIL PROTECTED]> babbled:
> Hi,
>
> I've seen in Evas.h that most of the methods of Evas_Smart_Class are
> marked as to-be-deleted in the future ("FIXME: DELETE ME"). This
> concerns show(), hide(), color_set(), clip_set() and clip_unset().
mmm -
On Tue, 21 Aug 2007 00:58:58 +0200 Simon TRENY <[EMAIL PROTECTED]> babbled:
i'll get to this on the weekend - so don't think i'm ignoring it - it just
needs a longer reply than i have time for right now :)
> Hi,
>
> I've seen in Evas.h that most of the methods of Evas_Smart_Class are
> marked as
Am Wed, 22 Aug 2007 09:03:07 +1000 schrieb Brett Nash:
> > > I disagree here. You are correct in that 95+% of cases are just
> > > hide/show the clip and the like. However we have a number of
> > > widgets that do things like stop animations, release resources or
> > > similar actions on hide ca
> > I disagree here. You are correct in that 95+% of cases are just
> > hide/show the clip and the like. However we have a number of widgets
> > that do things like stop animations, release resources or similar
> > actions on hide calls, also more complex widgets delay layout
> > recalculations u
On 8/20/07, Brett Nash <[EMAIL PROTECTED]> wrote:
> On Tue, 2007-08-21 at 00:58 +0200, Simon TRENY wrote:
> > Hi,
> >
> > I've seen in Evas.h that most of the methods of Evas_Smart_Class are
> > marked as to-be-deleted in the future ("FIXME: DELETE ME"). This
> > concerns show(), hide(), color_set(
On Tue, 2007-08-21 at 00:58 +0200, Simon TRENY wrote:
> Hi,
>
> I've seen in Evas.h that most of the methods of Evas_Smart_Class are
> marked as to-be-deleted in the future ("FIXME: DELETE ME"). This
> concerns show(), hide(), color_set(), clip_set() and clip_unset().
>
> I think it will be indee
On 8/20/07, Simon TRENY <[EMAIL PROTECTED]> wrote:
> Hi,
>
> I've seen in Evas.h that most of the methods of Evas_Smart_Class are
> marked as to-be-deleted in the future ("FIXME: DELETE ME"). This
> concerns show(), hide(), color_set(), clip_set() and clip_unset().
>
> I think it will be indeed a r
Simon TRENY schrieb:
> On Tue, 21 Aug 2007 10:26:16 +0200,
> Peter Wehrfritz <[EMAIL PROTECTED]> wrote :
>
>
>> Chady Kassouf schrieb:
>>
>>> On 8/21/07, Peter Wehrfritz <[EMAIL PROTECTED]> wrote:
>>>
>>>
Simon TRENY schrieb:
> Hi,
>
> I've
On Tue, 21 Aug 2007 10:02:03 +1000,
Brett Nash <[EMAIL PROTECTED]> wrote :
> On Tue, 2007-08-21 at 00:58 +0200, Simon TRENY wrote:
> > Hi,
> >
> > I've seen in Evas.h that most of the methods of Evas_Smart_Class are
> > marked as to-be-deleted in the future ("FIXME: DELETE ME"). This
> > concerns
On Tue, 21 Aug 2007 10:26:16 +0200,
Peter Wehrfritz <[EMAIL PROTECTED]> wrote :
> Chady Kassouf schrieb:
> > On 8/21/07, Peter Wehrfritz <[EMAIL PROTECTED]> wrote:
> >
> >> Simon TRENY schrieb:
> >>
> >>> Hi,
> >>>
> >>> I've seen in Evas.h that most of the methods of Evas_Smart_Class
> >>
On Tue, 21 Aug 2007 08:50:46 +0200,
Peter Wehrfritz <[EMAIL PROTECTED]> wrote :
> Simon TRENY schrieb:
> > Hi,
> >
> > I've seen in Evas.h that most of the methods of Evas_Smart_Class are
> > marked as to-be-deleted in the future ("FIXME: DELETE ME"). This
> > concerns show(), hide(), color_set(),
Chady Kassouf schrieb:
> On 8/21/07, Peter Wehrfritz <[EMAIL PROTECTED]> wrote:
>
>> Simon TRENY schrieb:
>>
>>> Hi,
>>>
>>> I've seen in Evas.h that most of the methods of Evas_Smart_Class are
>>> marked as to-be-deleted in the future ("FIXME: DELETE ME"). This
>>> concerns show(), hide(),
On 8/21/07, Peter Wehrfritz <[EMAIL PROTECTED]> wrote:
>
> Simon TRENY schrieb:
> > Hi,
> >
> > I've seen in Evas.h that most of the methods of Evas_Smart_Class are
> > marked as to-be-deleted in the future ("FIXME: DELETE ME"). This
> > concerns show(), hide(), color_set(), clip_set() and clip_uns
Simon TRENY schrieb:
> Hi,
>
> I've seen in Evas.h that most of the methods of Evas_Smart_Class are
> marked as to-be-deleted in the future ("FIXME: DELETE ME"). This
> concerns show(), hide(), color_set(), clip_set() and clip_unset().
>
> I think it will be indeed a really great thing to do since
Am Tue, 21 Aug 2007 00:58:58 +0200 schrieb Simon TRENY:
> Hi,
>
> I've seen in Evas.h that most of the methods of Evas_Smart_Class are
> marked as to-be-deleted in the future ("FIXME: DELETE ME"). This
> concerns show(), hide(), color_set(), clip_set() and clip_unset().
>
> I think it will be in
Hi,
I've seen in Evas.h that most of the methods of Evas_Smart_Class are
marked as to-be-deleted in the future ("FIXME: DELETE ME"). This
concerns show(), hide(), color_set(), clip_set() and clip_unset().
I think it will be indeed a really great thing to do since when we
implement these methods f
On Mon, 1 Jan 2007 15:43:42 +0100 "Jorge Luis Zapata Muga"
<[EMAIL PROTECTED]> babbled:
> On 7/2/06, The Rasterman Carsten Haitzler <[EMAIL PROTECTED]> wrote:
> > On Mon, 19 Jun 2006 01:17:03 +0200 "Jorge Luis Zapata Muga"
> > <[EMAIL PROTECTED]> babbled:
> >
> > > Hi all,
> > > i have some doubts
On 1/1/07, Brian Mattern <[EMAIL PROTECTED]> wrote:
> On Mon, Jan 01, 2007 at 03:43:42PM +0100, Jorge Luis Zapata Muga wrote:
> > On 7/2/06, The Rasterman Carsten Haitzler <[EMAIL PROTECTED]> wrote:
> > > On Mon, 19 Jun 2006 01:17:03 +0200 "Jorge Luis Zapata Muga"
> > > <[EMAIL PROTECTED]> babbled:
On Mon, Jan 01, 2007 at 03:43:42PM +0100, Jorge Luis Zapata Muga wrote:
> On 7/2/06, The Rasterman Carsten Haitzler <[EMAIL PROTECTED]> wrote:
> > On Mon, 19 Jun 2006 01:17:03 +0200 "Jorge Luis Zapata Muga"
> > <[EMAIL PROTECTED]> babbled:
> >
> > > Hi all,
> > > i have some doubts-ideas about evas
On 7/2/06, The Rasterman Carsten Haitzler <[EMAIL PROTECTED]> wrote:
> On Mon, 19 Jun 2006 01:17:03 +0200 "Jorge Luis Zapata Muga"
> <[EMAIL PROTECTED]> babbled:
>
> > Hi all,
> > i have some doubts-ideas about evas smart objects,
> >
> > 1. the API
> > in order to add an object to a smart object y
On Mon, 19 Jun 2006 01:17:03 +0200 "Jorge Luis Zapata Muga"
<[EMAIL PROTECTED]> babbled:
> Hi all,
> i have some doubts-ideas about evas smart objects,
>
> 1. the API
> in order to add an object to a smart object you have to do
> _member_add(o, s) and to delete _member_del(o,s). On the code of bo
Le Mon, 19 Jun 2006 01:17:03 +0200,
"Jorge Luis Zapata Muga" <[EMAIL PROTECTED]> a _crit :
> Hi all,
> i have some doubts-ideas about evas smart objects,
>
> 1. the API
> in order to add an object to a smart object you have to do
> _member_add(o, s) and to delete _member_del(o,s). On the code of
On Mon, Jun 19, 2006 at 01:17:03AM +0200, Jorge Luis Zapata Muga wrote:
> Hi all,
> i have some doubts-ideas about evas smart objects,
>
> 1. the API
> in order to add an object to a smart object you have to do
> _member_add(o, s) and to delete _member_del(o,s). On the code of both
> an evas smart
> > > 2. the implementation
> > > ive been playing with smart objects for evoak, so ill explain
> >
> > I thought evoak was considered to be laid to rest?
>
> No, it was just sleeping. B-)
>
> There has been a great desire amongst a few people to get evoak up
> and on it
On Mon, 19 Jun 2006 02:55:36 GMT "[EMAIL PROTECTED]"
<[EMAIL PROTECTED]> wrote:
> > 2. the implementation
> > ive been playing with smart objects for evoak, so ill explain
>
> I thought evoak was considered to be laid to rest?
No, it was just sleeping. B-)
There has been a great desi
> Hi all,
> i have some doubts-ideas about evas smart objects,
>
Ah yes, the saga of the evas smart object.
> 1. the API
> in order to add an object to a smart object you have to do
> _member_add(o, s) and to delete _member_del(o,s). On the code
> of both an evas smart object
Hi all,
i have some doubts-ideas about evas smart objects,
1. the API
in order to add an object to a smart object you have to do
_member_add(o, s) and to delete _member_del(o,s). On the code of both
an evas smart object actually stores the members on a list but theres
no function to retrieve them,
On Mon, 16 Dec 2002 18:05:48 -0600 [EMAIL PROTECTED] babbled:
> I've been playing around with the smart objects in evas a bit, and found
> something that I think would be nice to have (but haven't thought of any cons
> yet), so i'll run it by here first.
>
> I think if you set a callback on a sma
I've been playing around with the smart objects in evas a bit, and found
something that I think would be nice to have (but haven't thought of any cons
yet), so i'll run it by here first.
I think if you set a callback on a smart object it should put that callback
on all of the objects that are memb
31 matches
Mail list logo
