Hi Philipp,
Philipp Lohmann - Sun Germany wrote:
Kay Ramme - Sun Germany - Hamburg wrote:
Hi Philipp,
Philipp Lohmann - Sun Germany wrote:
may I summarize the requirement this way, that VCL must cooperate (read:
properly synchronize) with GTK/GDK in a way, that GTK/GDK may be used by
any other subsystem (e.g. a Uno component) independently of VCL? So, it
seems (because of the need to call "gdk_threads_set_lock_functions"
before "gdk_threads_init") that VCL must be initialized first, before
any other subsystem (which obviously is not a problem with the current
centralistic approach, but may become one if thinking in components
terms only (which I agree is hypothetical :-) ).
Yes, that's about it I think.
So it seems I got it :-)
If I understand correctly, I see a problem with our current support of
Gnome < 2.4, as the SolarMutex may run out of sync with the GDK mutex,
which may lead to deadlocks in case of multiple threads. Possible
solutions IMHO are:
- In general use the GDK mutex as the underlying mutex for the Solar
Mutex. Unfortunately this is not as simple as it could be, as the GDK
mutex is non-recursive, while the Solar Mutex is recursive.
- Drop support for Gnome < 2.4 .
- Forbid per policy the direct use of GDK respectively
"gdk_threads_enter" etc.
Did I miss anything?
Kind regards, pl
Thanks
Kay
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
