From 89beef678314d90d64cf62b632257e094b939ea4 Mon Sep 17 00:00:00 2001 From: "saijanai.kuhn" Date: Tue, 28 Oct 2008 04:24:54 +0000 Subject: [PATCH] block.block_type vs block.type issues --- pyogp/lib/base/message/udpserializer.py | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/pyogp/lib/base/message/udpserializer.py b/pyogp/lib/base/message/udpserializer.py index e4945ab..65bf466 100644 --- a/pyogp/lib/base/message/udpserializer.py +++ b/pyogp/lib/base/message/udpserializer.py @@ -104,14 +104,14 @@ class UDPPacketSerializer(grok.Adapter): #that make up this message, with the number stored in the template #don't need to add it to the buffer, because the message handlers that #receieve this know how many to read automatically - if template_block.type == MsgBlockType.MBT_MULTIPLE: + if template_block.block_type == MsgBlockType.MBT_MULTIPLE: #LDE 230ct2008 block_type vs block.type issue if template_block.number != block_count: raise exc.MessageSerializationError(template_block.name, "block data mismatch") #variable means the block variables can repeat, so we have to #mark how many blocks there are of this type that repeat, stored in #the data - if template_block.type == MsgBlockType.MBT_VARIABLE: + if template_block.block_type == MsgBlockType.MBT_VARIABLE: #LDE 230ct2008 block_type vs block.type issue block_buffer += struct.pack('>B', block_count) bytes += 1