No problem, the fix to get around how Wine behaves is actually useful as an extra check under Windows. While Wine was behaving differently, I am not sure I would class this as a Wine bug simply due to how complex the order and timing of windows messages can be sometimes.
Wine developer here — could you share more details? What assumption was mIRC making about message order?
We often consider divergence from Windows that an application relies on to be a bug, whether documented or not, and even if mIRC isn't making these assumptions anymore, well, if one application relies on them another might that's less likely to change, so we'd probably like to fix this in Wine as well.
