DebugOutput for Double-Byte

[Grok]

Just yesterday I realized that my DebugOutput function displays double-byte character sets as single-byte output.  If someone wants something to do, how about updating it to properly show doublebyte output?

[TheMinistered]

Sure, start with posting the code to method debugoutput in this thread.

[Grok]

Function DebugOutput

[Adron]

I think double-byte output should be optional. When you receive b.net packets, some of the low ascii might be interpreted as double-byte characters, and outputting those as such would ruin the use of it for displaying binary data / single-byte characters.

[Tuberload]

I think double-byte output should be optional. When you receive b.net packets, some of the low ascii might be interpreted as double-byte characters, and outputting those as such would ruin the use of it for displaying binary data / single-byte characters.

I have very little knowledge of VB, but wouldn't you just convert the string to a byte array and handle it that way?

[Adron]

I think double-byte output should be optional. When you receive b.net packets, some of the low ascii might be interpreted as double-byte characters, and outputting those as such would ruin the use of it for displaying binary data / single-byte characters.

I have very little knowledge of VB, but wouldn't you just convert the string to a byte array and handle it that way?

Well, what I mean is that the contents of a packet can be interpreted either as single-byte characters, as is mostly the case with b.net, as multi-byte characters, or as double-byte characters, and this is protocol dependent. The DebugOutput function can't know how to interpret the data you pass it, so there must be a way of telling it.

[TheMinistered]

Here is a good way to tell it...

Code Select Expand


Public Enum CharacterType
   Single = 0
   Double = 1
   Multiple = 2
End Enum

Public Function DebugOutPut(... , Optional ByVal CharacterType as CharacterType = Single)