question about multiwindow mode and application icons

[Harold L Hunt II]

Stay tuned... I am in the process of posting a test release.  In fact, 
the files are really already up if you want to them and start looking:

http://www.msu.edu/~huntharo/xwin/shadow/xwin-Test84-to-Test85.diff (22 KiB)

http://www.msu.edu/~huntharo/xwin/shadow/xwin-20030517-1320.tar.bz2 (110 
KiB)

http://www.msu.edu/~huntharo/xwin/shadow/XWin-Test85.exe.bz2 (1206 KiB)

Harold

Earle F. Philhower III wrote:

> Great news there Harold,
> At 01:17 PM 5/17/2003 -0400, you wrote:
> 
>> I think found the race condition and fixed it.
>>
>> From the manual, it sounds like XInitThreads is only supposed to be 
>> called once per process... either that, or, it is simply not thread 
>> safe.  I added the ppmServerStarted mutex code to 
>> winMultiWindowXMsgProc () and moved the unlocking of the mutex in all 
>> thread functions to occur after the call to XInitThreads.
>> Now, those blocks of three ERROR messages that I was getting from 
>> winClipboardErrorHandler () are now in the same place, but they are 
>> coming from winMultiWindowWMErrorHandler (), as they should.
>> So, it looks like we were having a problem with Xlib delivering events 
>> to the wrong thread.  Playing it safe with XInitThreads seems to have 
>> taken care of this problem.  I can now run with -multiwindow and 
>> -clipboard safely.
> 
> 
> There are few things more fun than debugging multithreaded race conditions,
> like having teeth drilled or listening to Britney Spears...
> 
> 
> -Earle F. Philhower, III
>  earle@ziplabel.com
>  cdrlabel - ZipLabel - FlpLabel
>  http://www.cdrlabel.com