On Tue, 1 Mar 2016 05:20:56 +0100 Cedric BAIL said:
> On Tue, Mar 1, 2016 at 4:11 AM, Carsten Haitzler wrote:
> > On Mon, 29 Feb 2016 18:10:02 -0800 Cedric BAIL said:
> >> On Feb 29, 2016 17:46, "Carsten Haitzler" wrote:
> >> > On Mon, 29 Feb 2016 18:45:15 + Tom Hacohen said:
> >> > > Yes
On Tue, Mar 1, 2016 at 4:11 AM, Carsten Haitzler wrote:
> On Mon, 29 Feb 2016 18:10:02 -0800 Cedric BAIL said:
>> On Feb 29, 2016 17:46, "Carsten Haitzler" wrote:
>> > On Mon, 29 Feb 2016 18:45:15 + Tom Hacohen said:
>> > > Yes, I already told him that on IRC. The cost of caching is most li
On Mon, 29 Feb 2016 18:10:02 -0800 Cedric BAIL said:
> On Feb 29, 2016 17:46, "Carsten Haitzler" wrote:
> >
> > On Mon, 29 Feb 2016 18:45:15 + Tom Hacohen said:
> >
> > > Yes, I already told him that on IRC. The cost of caching is most likely
> > > higher than the cost of calculating every
On Feb 29, 2016 17:46, "Carsten Haitzler" wrote:
>
> On Mon, 29 Feb 2016 18:45:15 + Tom Hacohen said:
>
> > Yes, I already told him that on IRC. The cost of caching is most likely
> > higher than the cost of calculating every time, and anyway, it's rare
for
> > an object to need to have infor
On Mon, 29 Feb 2016 18:45:15 + Tom Hacohen said:
> Yes, I already told him that on IRC. The cost of caching is most likely
> higher than the cost of calculating every time, and anyway, it's rare for
> an object to need to have information about the mainloop, adding a cache on
> every object i
On Mon, Feb 29, 2016 at 10:45 AM, Tom Hacohen wrote:
> Yes, I already told him that on IRC. The cost of caching is most likely
> higher than the cost of calculating every time, and anyway, it's rare for
> an object to need to have information about the mainloop, adding a cache on
> every object is
Yes, I already told him that on IRC. The cost of caching is most likely
higher than the cost of calculating every time, and anyway, it's rare for
an object to need to have information about the mainloop, adding a cache on
every object is a bad idea, calculating on creation is the way to go.
On Mon
Hello,
On Fri, Feb 26, 2016 at 4:32 PM, Carsten Haitzler wrote:
> we were discussing this and i don't remember an adequate solution.
>
> so we're needing to allow multiple event loops (main loop).
>
> ok = first loop created == main loop. fine. store that in a global.
>
> but after this... what l
we were discussing this and i don't remember an adequate solution.
so we're needing to allow multiple event loops (main loop).
ok = first loop created == main loop. fine. store that in a global.
but after this... what loop does an object belong to? ok - timers:
create timer. set parent to the l
