Bug #99
Kick reason is not sent correctly
Start date:
Due date:
% Done:
0%
Estimated time:
Version:
0.13.1
OS:
Any
Description
/kick This is a long kick message
This results in the kick reason being "message" only. Probably something about the parameter handling in the kick user handler.
Associated revisions
History
#1 Updated by Sputnick over 16 years ago
Fixed.
Encodings are now honored for both sending and receiving. Cleaned up encode/decode
stuff in the handlers and switched putCmd() et. al. to accepting (encoded) QByteArray only instead
of QString.
Also fixed notices being shown in a separate buffer upon reconnect, and the kick message problem (BR #99).
Oh, and the default kick reason defined in your identity is used if appropriate now.