If you want to use GUI with every thread, you can make them separate
projects and start them with main project.
There are a lot of options how the projects can interact with each other,
depending on your needs.
File, pipe, DBus, ...
Jussi
On Mon, May 6, 2013 at 12:03 PM, Olivier Cruilles
wrote:
Hi Benoit,
Forget my problem about TASK object. I think this not for my usage.
After many time trying different solutions about my problem of xcb_io.c, if I
use TIMER to chain each step of the treatment
this bug appear mutch later but it alway appear.
So I completely forget TASK to solve my pro
Le 04/05/2013 12:33, Olivier Cruilles a écrit :
> Hi Benoit,
>
> I found that on internet. Does it help you or talk to you ?
>
> http://www.unix.com/programming/153046-fork-thread-assertion-failed-x11.html
>
> Cordialement,
>
> Olivier Cruilles
> Mail: linu...@club-internet.fr
>
Mmm... and so? If
Hi Benoit,
I found that on internet. Does it help you or talk to you ?
http://www.unix.com/programming/153046-fork-thread-assertion-failed-x11.html
Cordialement,
Olivier Cruilles
Mail: linu...@club-internet.fr
Le 1 mai 2013 à 17:44, Olivier Cruilles a écrit :
> gbx3: xcb_io.c :221 : poll_for
Le 01/05/2013 17:44, Olivier Cruilles a écrit :
> Hi Benoit,
>
> I'm adding a part in my project witch use intensely TASK objects.
>
> I start the treatment of many files, analyzed by each TASK object.
> After sometime, this bug appear:
>
> gbx3: xcb_io.c :221 : poll_for_event: L'assertion « (((lo
Hi Benoit,
I'm adding a part in my project witch use intensely TASK objects.
I start the treatment of many files, analyzed by each TASK object.
After sometime, this bug appear:
gbx3: xcb_io.c :221 : poll_for_event: L'assertion « (((long) (event_sequence)
- (long) (dpy->request)) <= 0) » a écho
