Why I think this is a bug is that mIRC acts if it were in fact two lines because mIRC processes the linechange. An empty line is still a line and that is what the confirmation message should be there for.
Even in the case of
"Hello
a."
I'm still pasting only one line, because mIRC does the default action of /say on the first line and the second line is left in the editbox because it doesn't end in a linechange. If I have made my editbox sizing automatic, it makes no difference between:
"Hello.
"
and
"Hello.
a"
mIRC has moved the blinking line to the second line in both cases, so clearly it thinks that there are in fact two lines being pasted on both occasions. If what you're saying is true, then pasting:
"Hello.
"
Would have the blinking cursor/line/whatever it's called still in the first line right after "Hello.", but it's not, it's on the second line. Empty, as in "", isn't the same thing as null.
EDIT: This wouldn't be impossible or even that hard to fix. There's the right way the wrong way and the quick way to do things. The quick way being the wrong way but only faster.
It isn't called optimization, it's called lazy coding. It would be like asking for an amount and someone enters $123. Instead of doing it correctly and removing the illegal character $, you just set the amount to 0.
Last edited by krypto; 01/09/12 10:39 PM.