QUOTE(Groovedude @ Mar 1 2008, 03:48 PM)

hmmm didnt work first time iused it..
just kept scrolling
RESPONSE:
RESPONSE:
RESPONSE:
RESPONSE:
RESPONSE:
RESPONSE:
with nothing else.. close and re-run it, and its loaded fine. odd though dunno why it did that

but Thank you!

I also noticed this error (once so far) the other day, do you know what server it was trying to connect to?
As I coded the irc routines myself, their stability had only been tested in a limited number of scenarios by myself, but you'd think that running it several hundred times would make any bugs apparent (I guess that's what beta testing is for.)
As you are the first to report it, and I have only ever seen this bug once, after running the application many, many, many times, I don't think this bug warrants an immediate fix.
From what i've seen, it's just a problem with the integrity of the buffer being checked, and it's causing no flooding to the IRC server, nor causing any disruptive cpu usage. The error-handling I have added will sort this problem out after 20 seconds anyway (it jumps to the next IRC server after 20 seconds of inactivity, which will cause the buffer to be filled with VALID data.)
So it's more of a very rare inconvenience, where the user either waits 20 seconds for the routine to continue flow, or restarts it (the application still responds, with no need to force quit.)
As it is annoying nonetheless (and I have already identified what piece of code to correct), I will slip a fixed version into the official distribution channels within the coming weeks.
As they say... first impressions count, so sorry about this.
Thanks for reminding me of this bugs existence, and letting me know it occurs more often than I first thought
