Just a quick note on this part... mIRC does not go through and parse your entire pasted text to find empty lines. This was mentioned earlier either in this thread or the other one. So any empty lines in the middle will still be treated as a line when pasting regardless of whether or not it pastes it. It certainly could check for that, but that would be processing more information when you paste.
The current versions of mIRC require a modern operating system. It isn't running on Windows 3.11 on a 286 cpu with 256kb of RAM. I have not seen the source code of mIRC, so I wouldn't know how it's done internally. The operation wouldn't even be noticeable on any modern-ish (from 15 years old to this day) desktop, laptop or netbook. Or are you seriously saying that people would notice some VERY simple operations done to a string compared to whatever it's doing right now?
After all, if the last line doesn't end in a new line character, then it's not being sent to the server, so should not be counted.
But it
is being sent to the server if it's not empty regardless if it ends in a new line character or not when pasting more than one line. Didn't you do any testing on this bug before replying on how it works?
The purpose of the confirmation isn't to prevent you from pasting text into your edit box by accident, but to keep you from sending it to the server by accident.
As I already said, it doesn't do that. If what you say is it's intended purpose, then it's broken.
And, so you are aware, telling people why something works the way it does or why something isn't a good idea does not make someone a "troll".
I'm just pointing out the obvious based on what I have seen. But you're right, I was overreacting on calling all the regulars trolls when I should have just called you one.
There has to be a discussion of all sides (pros and cons) for a developer to decide what is worth doing and what is not. If no one was allowed to disagree, then you'd have a ton of suggestions where most of them are things that a lot of people wouldn't want.
This isn't a feature request. This is a bug report. A bug either exists or it doesn't. Although the two, bug report and feature request, are pretty much the same thing in the end at least in this case. The discussion is pretty one sided anyways. It's basically you saying "I think this is what the developer wanted anyways, so it's not going to be changed" or "This is how it is and this is how it should and will be". That's your silver bullet against all bug reports and feature requests that YOU don't like (and I'm pretty sure it's a logical fallacy as well).
Why I'm replying is that I don't want Khaled to read the first post, then skip to the last post and read:
And think he can skip over the bug.
EDIT: Just as a reminder, there are other clients out there and the number increases every year.
