[Gtk-sharp-list] Gtk# threading problem?

[Bob Smith]

Isnt this extremely dangerious from the standpoint of running applications
securely? If any old app can just spawn off a few threads and call into
gtk# at once, we're in trouble. :)

While I like the idea of doing this in C, since we're worried about
performance there, the .NET bindings should take care of this stuff so
that we can have a secure environment.

On 9 Oct 2002, Miguel de Icaza wrote:

>
> > What I found out is that getting all the gnome stuff from my program
> > out, it does what it is meant. I mean, commenting all the gnome stuff
> > from my program.
>
> You are using Gtk from two threads (one is the main loop, and you are
> pushing data onto a widget in the other).  Gtk is not thread safe, you
> can not do this.
>
> You need to have your thread load the data, and when it is ready to
> process it, wake up the main thread and have the main thread (which has
> the Gtk main loop) feed the data to the widget.
>
> Look at the ThreadNotify class in Gtk# which simplifies the complexicty
> of doing this.
>
> Miguel
>
> _______________________________________________
> Gtk-sharp-list maillist  -  Gtk-sharp-list@ximian.com
> http://lists.ximian.com/mailman/listinfo/gtk-sharp-list
>