A few minor bugs:
========== In the CHB's window menu, Method->Browse->Category... only prompts for the category if the focus isn't in the categories pane. This may be by design, but I find it confusing, and anyway it's not windows compatible since the '...' promises that there are further choices to be made. ========== Evaluating View desktop publishedAspects. gives a walkback. ========== Inspecting: Array with: ProtoObject new. gives a "recursion too deep" error. I'm not surprised to get an error, but I think there are two unintended problems here. One is that MessageNotUnderstood>>_descriptionArguments sends #class to its receiver, rather than #basicClass. The other is that -- if I'm reading the intent of DevelopmentSessionManager>>logError: correctly -- it is assuming that the error handler, [:e | e toTrace], will not itself cause errors. Would it be a good idea to put a further empty error handler inside this block to make sure ? ========== BTW, does anyone else find that doing 1 to: 10000 do: [:i | Transcript display: i ; display: '...'; cr]. causes screen corruption (and outside the boundaries of the Dolphin windows) ? Only one of my machines does it (a Win2K laptop) so it's probably a driver issue, but it only happens from Dolphin. -- chris |
Chris
You wrote in message news:[hidden email]... > A few minor bugs: Thanks, as ever, for your reports. > ========== > > In the CHB's window menu, Method->Browse->Category... only prompts for the > category if the focus isn't in the categories pane. This may be by design, > but I find it confusing, and anyway it's not windows compatible since the > '...' promises that there are further choices to be made. I agree. Defect #364. Should be fixed in the next release. > ========== > > Evaluating > View desktop publishedAspects. > gives a walkback. Defect #365. Fixed for the next release. > > ========== > > Inspecting: > Array with: ProtoObject new. > gives a "recursion too deep" error. I'm not surprised to get an error, but > I think there are two unintended problems here. One is that > MessageNotUnderstood>>_descriptionArguments sends #class to its receiver, > rather than #basicClass. The other is that -- if I'm reading the intent of > DevelopmentSessionManager>>logError: correctly -- it is assuming that the > error handler, [:e | e toTrace], will not itself cause errors. Would it be > a good idea to put a further empty error handler inside this block to make > sure ? Agreed. Defect #s 366 and 367. Fixed for the next release. > ========== > > BTW, does anyone else find that doing > 1 to: 10000 do: [:i | Transcript display: i ; display: '...'; cr]. > causes screen corruption (and outside the boundaries of the Dolphin windows) > ? Only one of my machines does it (a Win2K laptop) so it's probably a > driver issue, but it only happens from Dolphin. No, I've never seen that, and on the face of it it doesn't seem likely to be a problem in Dolphin (bearing in mind that the Transcript text window is a Windows control and that the corruption is occuring on the desktop too). The only thing I can suggest is turning off the "flashOnOutput" option, but I would have thought it more likely to be something to do with all that scrolling. Regards Blair |
Free forum by Nabble | Edit this page |