Hi Philipp,
Philipp Lohmann - Sun Germany wrote:
You'd be dropping Solaris 8 and 9 then; since even with requiring
"gdk_threads_set_lock_functions" you'll still need a separate YieldMutex
implementation I think it won't hurt to keep the existing fallback
without them as it won't cost much - granted it is a little ugly but
there are far worse problems in out code IMHO.
Agreed, what about dropping support for "gdk_threads_set_lock_functions"
then and to always acquire (which AFAIK is already the case for Gnome <
2.4) the GDK mutex (gdk_threads_enter / ..._leave) before calling into
GDK? You are actually right, that from a coding standpoint the
difference isn't too big, but it IMHO is from testing point of view.
Just my 2 cents, pl
Again thanks for your help
Kay
Kay Ramme - Sun Germany - Hamburg wrote:
Hi again,
on my way to restructuring VCL locking etc. I just took a deeper look at
the GTK backend (as recommended by Philipp). I also had a chance to
briefly talk with Michael Meeks about it.
The GTK backend somehow differentiates between Gnome >= 2.4 and below
while utilizing "gdk_threads_set_lock_functions" in the >= 2.4 case.
My question is, would it be an option to drop support for Gnome < 2.4
wrt the GTK backend, basically falling back to plain X11? At least
Michael would be fine with it but certainly others have an opinion as well.
Thanks for help
Kay
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
