You would think that two commits are enough for fixing formulations in the document, but I can easily prove you wrong... Modified: branches/win32k rewrite attempt/win32k/docs/refs.txt _____
Modified: branches/win32k rewrite attempt/win32k/docs/refs.txt --- branches/win32k rewrite attempt/win32k/docs/refs.txt 2005-08-04 18:01:47 UTC (rev 17046) +++ branches/win32k rewrite attempt/win32k/docs/refs.txt 2005-08-04 18:11:03 UTC (rev 17047) @@ -18,7 +18,7 @@
So if you want the queue to hang around, you reference the thread instead.
^ This is wrong, one can attach message queue to different thread using -AttachThreadInput. The number of thread sharing a queue is stored in the +AttachThreadInput. The number of threads sharing a queue is stored in the message queue structure and can be considered a reference count. Also on Windows systems there is maintained a global list of thread attachments.
@@ -36,12 +36,13 @@ NtUser/NtGdi/win32k syscalls ----------------------------
-A process and/or thread automatically gets converted to a GUI thread when -the first syscall from the shadow service table is called (ie. any NtUser* -or NtGdi* call). GUI threads have bigger kernel stack (FIXME: not the case -on ReactOS yet) and have associated storage for the Win32 structures. The -conversion itself happens in the syscall handler and the win32k callbacks -(registered with PsEstablishWin32Callouts) are called accordingly. +A process and/or thread automatically gets converted to a GUI thread / +process when the first syscall from the shadow service table is called (ie. +any NtUser* or NtGdi* call). GUI threads have bigger kernel stack (FIXME: +not the case on ReactOS yet) and have associated storage for the Win32 +structures. The conversion itself happens in the syscall handler and the +win32k callbacks (registered with PsEstablishWin32Callouts) are called +accordingly.
A process automatically establishes a connection to a window station on the GUI thread conversion. The Win32 process initialization callback routine