Re: [Bug-XBoard] Latest developments

[h.g. muller]

> I have no problem with wrong windows having focus. Never happened for me.

OK, good Then we can leave out this rather complex patch. The GhostView 
file browser is kind of a special window anyway, since it has its own event 
loop, and seems to bypass Xaw. This probably prevents the problems I had 
now with Xaw windows. I reember I hd similar problems when the GhostView 
browser always popped up as a child of the main window, (focus returning to 
the main window,instead of to the dialog that invoked the browser), but I 
guess that this is in fact just what it should do, and the problem 
disappeared when I made the browser a child of the dialog. I also could not 
get any wrong behavior there, no matter how I tried, so it seems we are OK 
there.

I found a bad memory corruption bug in 4.6.x (freeing allocated memory to 
which a live pointer still existed), when replacing the second engine. This 
makes it even more compelling to release a 4.6.1 quickly.

A completely different thing: in my refactor branch I now have a version 
that pops up a second board window (with just board, message and clocks; no 
menu or button bars) when you use the backgroundObserve + dualBoard options 
in ICS mode. (The old version just doebled the width of the window to show 
two boards side by side, which was less flexible. It also did not support 
extra clocks or highlighting of the moves in this board.) Please comment if 
this is useful, or if the old method was better.