Well, you weren't originally belittling me and I was happy with what you contributed until you started in on the "whining" thing. That's just not conducive to discussion in any forum (that word is big in political discourse these days and, IMHO, it's one of the reasons the country is so polarized at the moment). But that aside, I don't think you have been reading these posts very well, because your statements about what I've said are simply not accurate. The conversation went off on other issues and if I mentioned the letter again, then you will see, if you read the posts, that I was responding to a question.

Search on downloads, last name Campbell, one of the main bugs I'm dealing with right now is detailed in that form (should be the only item in the results list). With all the other stuff taking place here, I did not have a chance to mention that I did talk with a beta tester about this bug and he gave a very vague response that may have indicated it was fixed, but it was so vague I was left wondering. I felt he did not want to break the NDA and I did not want to pressure him to do that, so I dropped it.


>Sorry, Russell...I don't use JVP's tactics in my discussions. I don't have any need to feel important nor belittle anyone. I was willing to give some weight to your "bug", but you declined my offer. You complained about no letter from Ken, and continued to complain when plausible reasons for him not posting one were given by several people.
>
>I said nothing about publishing in any of my posts on this thread. However, I have authored articles dealing with things that people may or may not call bugs.
>
>http://www.craigberntson.com/Articles/kb001.htm
>http://www.craigberntson.com/Articles/kb008.htm
>http://www.craigberntson.com/Articles/kb005.htm
>
>These articles don't discuss bugs being fixed, but rather how to deal with them, which, IMO, as important as saying "it's been fixed in version x.x" because not everyone is using an updated version.
>
>My offer to help is still open. There are no strings attached to the offer. You simply package up the code, a description of the error, and the expected behavior. I'll do everything I can to see if it's been resolved in a later beta version.