Hi Christian, Thank you for your clarification. Now I understand.
I have misunderstood since there are some source codes using Mutex in the module 'sd,' and been confused since neither semaphore nor condition variable is used there. Even though OOo does not use multi-threading for two concurrent presentation documents, it would be better to carefully guard shared data. Graphical user interface with use of yield() to give a chance of processing to other instances could turn into a pseudo, parallel processing. I know there are several distinguished, talented software engineers have been working on the graphical application in Hamburg. I will try to find a cue of the unwanted phenomenon that people have reported. Best regards, Tora Christian Lippka wrote:
Hi Tora, there may be a misunderstanding. OOo does not use much threading, if you have two Presentation Documents open at the same time, user interface and core code of both documents run in the same thread. Threading problems can only occur if someone uses the API to fiddle with the office, f.e. java is a good candidate as it always runs in another thread as the office. Also our caching mechanisms to deal with graphics and ole objects never ever run in different threads than the application itself. Regards, Christian
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
