search

GalFe / lidgren-network-gen3

Automatically exported from code.google.com/p/lidgren-network-gen3
0 stars 0 forks source link

NetPeer.WaitMessage blocks even if there are messages in the queue #85

Closed GoogleCodeExporter closed 9 years ago

GoogleCodeExporter commented 9 years ago 
What steps will reproduce the problem?

1. Send two messages. In debug build, standard debug messages "Socket bound to 
0.0.0.0:55555: True" and "Network thread started" will do the job.
2. Use this to process them: while ((msg = server.WaitMessage(10 * 1000)) != 
null) {...usual message process code...}
3. See that first message is processed right away, the second only 10 seconds 
later.

What is the expected output? What do you see instead?

Expected behavior is that WaitMessage will not block if there are messages in 
queue. Currently it blocks after first message in queue is processed.

What version of the product are you using? On what operating system?

lidgren-network-gen3-2011-06-27.zip
Windows 7

Original issue reported on code.google.com by smiledi...@joystickninjas.com on 19 Aug 2011 at 12:24

GoogleCodeExporter commented 9 years ago 
Oops; slight oversight. Fixed in revision 257.

Original comment by lidg...@gmail.com on 19 Aug 2011 at 12:34