Originally Posted by Nobody Special
I only follow bugs that come in through customer service or through our own test program (don't have time to comb the web). I have fixed a number of related issues, so your problem may have been addressed.
If you read the thread attached to my post, you would see it HAS been submitted through customer service. So my question is legitimate.
For the record, your own posting statistics show you post on Gearslutz approximately once every three days....and YOU started this thread....that's hardly "combing" the web as you put it. You have more posts than me and I have been a member since 2002.
As the developer and writer of the code, I would hope you take ownership of the product and are open to free testing from a variety of sources (I, however, paid full retail price for the privilege).
I understand you have a process and are busy...so am I. However, if I get a chance to give information of value directly to the source that can affect a positive outcome...I usually do so rather than wade through the mire of faceless trouble-ticket bureaucracy.
My apologies for the misstep in this case, and thank you for your valuable time.....I'll not waste any more of it.
I look forward to a resolution of this BUG in the upcoming release since its presence has already been forwarded and subsequently acknowledged through the proper channels. (see my earlier post)