Option (b) is better, as far as I can tell. On windows, those
messages have their own HWND anyway.
Adam
On Fri, Apr 10, 2009 at 1:15 PM, Ricardo Vargas wrote:
> I opened bug 7379 a while ago to implement option b on the windows side.
>
> On Fri, Apr 10, 2009 at 1:03 PM, Brett Wilson wrote:
>
On Fri, Apr 10, 2009 at 1:03 PM, Brett Wilson wrote:
>
> On Fri, Apr 10, 2009 at 12:42 PM, Evan Stade wrote:
> > a) wrap the clipboard calls in gtk_threads_{enter,leave}(). This makes
> > the calls thread safe, but it does so by locking a process-wide mutex,
> > which will block our UI thread's
I opened bug 7379 a while ago to implement option b on the windows side.
On Fri, Apr 10, 2009 at 1:03 PM, Brett Wilson wrote:
>
> On Fri, Apr 10, 2009 at 12:42 PM, Evan Stade wrote:
> > a) wrap the clipboard calls in gtk_threads_{enter,leave}(). This makes
> > the calls thread safe, but it does
On Fri, Apr 10, 2009 at 12:42 PM, Evan Stade wrote:
> a) wrap the clipboard calls in gtk_threads_{enter,leave}(). This makes
> the calls thread safe, but it does so by locking a process-wide mutex,
> which will block our UI thread's main loop.
I personally think this is OK. These calls "should"
On Fri, Apr 10, 2009 at 12:42 PM, Evan Stade wrote:
>
> glib and x aren't thread-safe. To work around this our intention is to
> only call into them from the UI thread. Unfortunately we currently
> don't follow through on this.
>
> To query the clipboard the renderer sends a sync IPC call to the
