the next release, which we will probably make very soon
This is in a WinBoard match (-mg > 1) ?
This might be a problem with both engines trying to access the book file in too rapid succession.
H.G.Muller wrote:You are correct. At the end of the dialog popup routine I set focus to the last text-edit (-spin or -string). But if there is a dialog without any text edits at all, this tries to acces a widget with a random number, which makes XBoard crash.
The remedy would be to comment out the SetFocus call at the very end of SettingsPopUp() in xoptions.c. An alternative would be to declare edit at the beginning of that routine as initialized to NULL, and put "if(edit)" in front of the SetFocus call.
I am not sure if these SetFocus calls are still needed; I put them in at a time where we had big trouble giving keyboard focus to window elements, and even then it failed for people that were using "desktop effects". But this could later be traced to a wrong order of libraries in the linker command. Now that we corrected that, most of the SetFocus calls might actually not be needed at all, and controls might automatically get and retain focus when you click them. Anyway, I will make sure it will be fixed in the next release, which we will probably make very soon forced by the egtbpath bug.
Users browsing this forum: No registered users and 1 guest