On Wed, 22 Nov 2000, Andre Poenitz wrote:
> > My current plan calls for a toolkit dependant SendEvent() that will send
> > the event to the main gui loop, and by some magic this will call the
> > correct event handler (possibly by signal/slot) inside the main thread.
> > ...
> > Is this idea acce
> =
> ## Main tread
> For xforms we can use a filedescriptor driven message queue and bind
> a callback that knows what to do with fl_add_io_callback.
> =
> Unfortunately is xforms not threadsafe so we must be very careful to
> not use xforms functions in the thread.
> =
> For a fork/exec we
Andre Poenitz <[EMAIL PROTECTED]> writes:
| > My current plan calls for a toolkit dependant SendEvent() that will send
| > the event to the main gui loop, and by some magic this will call the
| > correct event handler (possibly by signal/slot) inside the main thread.
| > ...
| > Is this idea acce
> My current plan calls for a toolkit dependant SendEvent() that will send
> the event to the main gui loop, and by some magic this will call the
> correct event handler (possibly by signal/slot) inside the main thread.
> ...
> Is this idea acceptable?
"toolkit dependent method" does not really s
Baruch Even <[EMAIL PROTECTED]> writes:
| In my work on the graphics inset I find myself with a need for internal
| events, namely to announce internally that an image has been loaded. The
| problem starts when I want to do the image loading in a second
| thread/fork/whatever, since LyX
In my work on the graphics inset I find myself with a need for internal
events, namely to announce internally that an image has been loaded. The
problem starts when I want to do the image loading in a second
thread/fork/whatever, since LyX isn't necessarily (read: isn't) thread
safe, I
