Difference between revisions of "Effort/Encapsulate the Win32 thread affinity"
From Apache OpenOffice Wiki
< Effort
m (Fixed section indention, some wording, added links.) |
|||
| (8 intermediate revisions by the same user not shown) | |||
| Line 1: | Line 1: | ||
| − | [[ | + | Type: [[Uno/Term/Effort|Effort]] Status: in progress Owner: [[KR|Kay Ramme]] |
| − | + | ||
| − | + | ||
| − | Status: in progress | + | |
==Problem== | ==Problem== | ||
| − | The Win32 [[Uno/Term/Thread Affine|thread affinity]] of the window create and managing functions is inherited by VCL | + | The Win32 [[Uno/Term/Thread Affine|thread-affinity]] of the window create and managing functions is inherited by [[VCL]] from Windows. This results in code to need explicitly taking care of this, e.g. by delegating function invocations into the "main" thread. |
==Solution== | ==Solution== | ||
| − | Use a private thread for window creation | + | Use a private thread for window creation and message handling. Delegate all calls leading to the invocation of these functions into the private thread. Use the [[Uno/Effort/Binary/Extend Threading-Model|extended Binary Uno threading-model]] to simplify the implementation. |
==Time Frame== | ==Time Frame== | ||
| Line 15: | Line 12: | ||
{|border="1" cellspacing="0" class="wikitable" | {|border="1" cellspacing="0" class="wikitable" | ||
|- style="background:#efefef;" | |- style="background:#efefef;" | ||
| − | | Title || State | + | | Title || State || [[CWS]] |
|- | |- | ||
| − | | Implement wrappers for VCL window related Win32 backend || 90% | + | | Implement wrappers for [[VCL]] window related Win32 backend. || 90% || {{Uno/CWS|SRC680|vclthreadtransparency1}} |
|} | |} | ||
| + | |||
| + | |||
| + | [[Category:Effort]] | ||
| + | [[Category:Architecture]] | ||
| + | [[Category:Multi-Threading]] | ||
Latest revision as of 07:14, 19 June 2007
Type: Effort Status: in progress Owner: Kay Ramme
Contents
Problem
The Win32 thread-affinity of the window create and managing functions is inherited by VCL from Windows. This results in code to need explicitly taking care of this, e.g. by delegating function invocations into the "main" thread.
Solution
Use a private thread for window creation and message handling. Delegate all calls leading to the invocation of these functions into the private thread. Use the extended Binary Uno threading-model to simplify the implementation.
Time Frame
Tasks
| Title | State | CWS |
| Implement wrappers for VCL window related Win32 backend. | 90% | vclthreadtransparency1 |
