|
From: John G. <jge...@ny...> - 2002-01-30 20:06:01
|
> Hi Jgellene, > > Thanks for your response. Since I last reported, I have now > fixed this bug... and I don't quite know how. I did install > a different driver from nvidia, and that screwed up things > really bad as I couldn't even start my computer. Then I > reverted back to the original driver, and from then on > jEdit works fine. Go figure. > > That said, I also realize this is a Java bug, not a jEdit > bug. However, since jEdit is built on Java, it becomes a > jEdit bug as well. :-(. After all, someone's gotta fix it, > and if the user can't then we can't just ignore the problem > > Anyway, it works for me now, and I hope if someone else > faces the same problem they get some insight from these > emails. I'm glad you fixed it. "We" didn't ignore the problem. "We" found the manufacturer's website and posted detailed instructions on how you could check your driver for a possible upgrade. But the fact that Sun's native AWT code appears to have choked on your video settings is not the result of a programming error in jEdit's source code. Yes, it was a problem. No, it was not a bug. I can't help but wonder what insight anyone could possibly obtain from these emails, except "kick the car and it might start". But insight is in the eye of the insightee. John |