Thanks! <br>I missed the allocation in the enet_packet_create() code.<br>Just completely overlooked it. <br><br>I wanted to make sure I could delete the buffer and not get a rude surprise when it tried to read data that might not still be there.<br>
<br>Have a good weekend all!<br><br><br><div class="gmail_quote">On Fri, Dec 18, 2009 at 4:46 PM, Nuno Silva <span dir="ltr"><<a href="mailto:little.coding.fox@gmail.com">little.coding.fox@gmail.com</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">And just in case you didn't get it, you can delete the data after you tell enet to send the packet, since enet creates it's own copy of the data.<div>
<div></div><div class="h5"><br><br><div class="gmail_quote">On Fri, Dec 18, 2009 at 10:38 PM, Lee Salzman <span dir="ltr"><<a href="mailto:lsalzman1@cox.net" target="_blank">lsalzman1@cox.net</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">Packets allocate their own copy of the data, so once you send them, you don't need to free anything since ENet handles that itself. However, the packets ENet gives to you on RECEIVE events, you must remember to destroy them when you are done with them.<br>
</blockquote></div></div></div></blockquote></div><br>