>Please in turn forgive my laziness in not checking the FAQ before sending >my report. ;) No problem. :) >However, I would suggest that it would be very helpful to include some code >in gGo to prevent this situation from occurring. I am not a programming >expert but I hope it would not be too difficult to include a check of the >pathname when resuming a game against GnuGo, and if it includes spaces, put >up a brief message box explaining the problem, and reject resuming a game >from such a path. That idea is allright. However, I think before I write a parser for spaces in filenames, I rather try and see if I can fix the thing in GNU Go. The time and work might be better invested that way. >Under Windows, gGo by default saves games to the "My Documents" >folder. Also by default it looks in "My Documents" to open games when >resuming against GnuGo. I expect that a significant portion of your >program's users are running it on a Windows platform (it sounds like this >problem can also occur on non-Windows machines as well). So therefore by >default a large number of gGo users will currently experience failure on >trying to resume a game against GnuGo, and have to figure out the cause of >the problem and the workaround on their own. I hope that my suggestion for >a user-friendly failure mode is feasible. Yes, that was reported quite a lot already, that's why it was added to the FAQ. But I admit that might be not enough and people probably stumble about this too often, and it certainly is not an obvious problem. But as I said above, I will rather try to fix it than giving some warning message first. If I fail to fix it, then I can do the warning dialog. Generally Java has no trouble with those Windows filenames. So this is basically no problem to save into the operating systems default directory which unfortunately has a horrible directory name on Windows NT/2000/XP that is very unfriendly for programs of unix'ish origin. Ah well, you are not supposed to run this evil Unix stuff anyways, according to Bill. :) >I did not bring up the following in my previous mail, but I encountered >another issue with GnuGo 3.2 and gGo 3.3 when playing on a 333 MHz Win98 >(java 1.4) laptop last night. I checked the FAQ and I don't see it >mentioned. ;) Hahar, you are getting too careful now. :) >This perhaps has more to do with running the client on a slow processor >than anything else. I found that if I responded to GnuGo's move too >quickly, the computer would not take its next turn. By watching the GTP >control window during play I noticed that somehow moving very closely after >GnuGo moves prevents the "genmove_white" (or "genmove_black", as >appropriate) command from issuing. My clock would continue to tick down >after I had made a move in these circumstances. The only way to continue >the game was to save and resume (thus the previous issue). > >This issue arose mostly in and after the middle game, and I have not >experienced it on my considerably faster (1.4 GHz) WinXP box. This is very unlikely a CPU issue, as a PII 333 MHz is exactly the system I am writing gGo on. I need to check this, so far GNU Go playing works fine on this 333 MHz machine, without getting the issue you mentioned. I will try to reproduce it, I did not see the described effect yet myself (what of course does not mean it does not occur). 333 MHz is sufficient fast enough to run a simple Java program like gGo. GNU Go is occasionally getting a bit slow especially when in level 10. But I personally hate fast games anyways, so this does not disturb me too much. I'd guess the reason of the described problem is not the CPU speed but Win98, which is unable to handle Java threads properly. And gGo is making heavy use of threads. >gGo is a fine program and it is my favorite client as it has a good >interface and supports IGS and GnuGo quite well. I hope my comments have >been helpful. Thanks. :) Just do yourself a favour and don't run it on Windows 95/98/ME. Peter PS: Please use the email you subscribed with for posting, then I don't need to approve the posts first. The whole subscription is only meant to stop some kiddies from spamming the list, I basically don't mind if people subscribe or not before posting. But if you subscribe, then please post with that email address. No big deal, but saves me some work.