Re: Bug Commentary
The problem here is GrobRim failing to report the bug properly. I'll check this when I get home, then add it to the shortlist.
This should highlight why it is important to report bugs properly like mivayan here did. If a bug report is so vague that it is impossible to divine what the person reporting it meant, then it's likely to get dismissed out of hand.
I am no mind reader and neither are the devs, so when reporting a bug, it's better to go into detailed descriptions and step by step instructions on how to reproduce the bug (as mivayan did) rather than assuming that everyone knows what you meant. That will save everyone a lot of headache.
As an aside, I should mention that some of the bug reports gleaned from earlier readings of the thread only made sense when combined with other reports. In some cases things were so badly formulated that neither post (sometimes separated by several pages) by its lonesome made much sense or gave enough useful information to get anywhere, but together there was enough to produce a bug report. If ANYONE here thinks such reports are going to pass in the future, they had better think again, because in such events I WILL give them a piece of my mind. VERY firmly.
Edi
|