Guys, I'm hoping Sig will see this an immediately know what is at play. I don't even know if there is a fix, but there appears to be in 1.4. If backporting that to 1.3 is feasible, it should be done. I *think* I know some keywords that might pull his relevant reply (something like "you are a victim of") from the archive. Can't do it right now.
BTW, I took Stef's reply and used it to good effect - might have even figured out why I couldn't build images. All part of testing. If you look, you'll find code of mine in the image. Have you noted some of my responses to help others - probably not. But I would rather not play "I haven't seen" games. Bill ________________________________________ From: [email protected] [[email protected]] on behalf of Sven Van Caekenberghe [[email protected]] Sent: Friday, February 24, 2012 6:02 AM To: [email protected] Subject: Re: [Pharo-project] [Bug Tracker] Issues tagged 1.3 On 24 Feb 2012, at 11:12, Schwab,Wilhelm K wrote: > There is a tracker entry, but please understand it's the middle of the night > here and I'm in and out. I think Sig will know the details more off the top, > otherwise I'll search later. Would you rather I say nothing about a known > bug? I can't find anything with Schwab, Bill or Wilhelm in any issue ever in http://code.google.com/p/pharo/issues/list (there are a handful that are more than half a year old, magically you even received help). I read this mailing list all the time, I can't remember seeing a concrete, reproduceable bug report. Please, correct me if I am wrong. Some, like Stef, even took the trouble of trying to load some of the stuff that was causing you trouble, only to report that it worked for them. I and many others ask for help and report problems here all the time. It is incredible how people spring up all the time to help others with both simple and deep problems. It is often so that the one reporting a problem did something wrong himself, I am guilty here as well, but even then people took the trouble to look and give some of their valuable time. The way you ask the question makes a huge difference: provide details, make it reproduceable, don't include negative stuff. I'll make you a promise: I'll give you some of my personal time to try whatever you report next as 'BAD bug, makes 1.3 unstable, rendering the image useless', provided there is a description of how I should do it. Sven
