Closed GoogleCodeExporter closed 9 years ago
im using MSNP-Sharp v4.0.1 for MSNP21 just to be clear, never had the problem
with the other version. msnp18
Original comment by sander-d...@hotmail.com
on 1 Jun 2011 at 10:05
Original comment by freezing...@gmail.com
on 1 Jun 2011 at 10:22
I think that's the problem in example client, it will send typing messages once
the content of input box has been changed, so it will flood the msn server then
you get the error message. Give me some time and have a check.
Original comment by freezing...@gmail.com
on 1 Jun 2011 at 10:24
ah ok, so i can put an interval into sending the typing notice. but sometimes
it comes even when theres no typing going on wouldnt know how to reproduse that.
thanks for the reply!
Original comment by sander-d...@hotmail.com
on 1 Jun 2011 at 10:30
Hi,
For those error coming out without typing, that's because something goes wrong
in the remote contact side (sometimes their p2p capacities doesn't match the
protocol they supported), you can comment out line 1228 in DotMSNClient.cs or
filter the useless error message there. BTW, I just make a commit for the
typing message issue, you can use SVN to check it out in
branches/MSNPSHARP_40_STABLE folder
Original comment by freezing...@gmail.com
on 1 Jun 2011 at 10:39
Or if it still doesn't fix the issue, would you please attach a trace log here?
Original comment by freezing...@gmail.com
on 1 Jun 2011 at 10:40
thanks again for the reply.
I'm not using the msnpsharp client directly though i have used it as an example
to use your framework. i will try to check out the svn and that line in the
dotmsnclient when im done with work.
if i still cant fix it i will attach a trace log.
thanks for the effort.
Original comment by sander-d...@hotmail.com
on 2 Jun 2011 at 8:27
Hi,
simply blocking out the line you said from the exceptionoccured event fixed the
msgbox, thanks alot for pointing that out.
Original comment by sander-d...@hotmail.com
on 5 Jun 2011 at 2:43
Original comment by freezing...@gmail.com
on 10 Jun 2011 at 2:15
Original issue reported on code.google.com by
sander-d...@hotmail.com
on 31 May 2011 at 11:05