Parsing the colors

[hismajesty]

Why do you want to add support for a bug? I just filter them out.  

[Eli_1]

"There are no such thing as bugs, only features" - don'tknowwho

I other words, it's pretty. And for a bot that has a primary purpose of chatting, that "feature" should be supported. The majority of the bot users on b.net use their bot for chatting, and they like talking in colors. Why deprive their little hearts the joy it causes them?  

[edit] Looking up "deprive" because it doesn't look right to me.

[edit] Nope it's right.  

[Mephisto]

hmm...this has nothing to do with helping, but when you have a single character constant shouldn't you put it in single parenthasis, or does it no matter in VB?

I'm assuming your asking that because you program in C++? No, it doesn't matter in VB. There is no such thing as single quotes -- that is reserved for comments.

Yes.

[Eric]

Would be pretty hard to copy the clients flaw correctly.  
If you log on using a client, you'd notice that the color stops at the end of each line, so unless your chat box has the same dimensions as Starcraft's, replicating the bug correctly is pretty much impossible.

[Networks]

Example:
ÁY Test for multiple ÁR words?

Using you addtext function this causes it to still show it up in the rtb as shown:

Test for muliple
words

I was looking for it to be a whole entire sentence.

[Newby]

Example:
ÁY Test for multiple ÁR words?

Using you addtext function this causes it to still show it up in the rtb as shown:

Test for muliple
words

I was looking for it to be a whole entire sentence.

Don't append Chr(10) || Chr(13) to the end of each line you add.

[Networks]

It'll addtext which makes it addtext the colorparse(i) which is at every split.

[Eli_1]

Don't append Chr(10) || Chr(13) to the end of each line you add.

That's vbCrLf btw, networks. This is because most of the AddChat functions people use have it automaticly append vbCrLf to the text you pass to it.

[Networks]

Don't append Chr(10) || Chr(13) to the end of each line you add.

That's vbCrLf btw, networks. This is because most of the AddChat functions people use have it automaticly append vbCrLf to the text you pass to it.

I am using the addtext function you posted. Am i still wrong. You might as well give me your AIM s/n if you have one. You seem to answer a majority of my questions. :p

[Eli_1]

Before we go to AIM, post how your calling the AddText function I posted. I think you might be doing something like:

Code Select Expand


AddText RTB, GetColor(qwerty), Parse(i) & VbCrlF


[iago]

Why do you want to add support for a bug? I just filter them out.  

haha, I was going to say that, too.

[Networks]

Code Select Expand


Private Function AddText(OutputTO As RichTextBox, _
ByVal Color As ColorConstants, _
ByVal Data As String)
   With OutputTO
       .SelStart = Len(.text)
       .SelColor = Color
       .SelText = Data
       .SelStart = Len(.text)
   End With
End Function


Code Select Expand


'Color Parsing
Dim ColorParse() As String
Dim ColorByte As String
Dim i As Integer

If InStr(1, Message, "Á", vbTextCompare) <> 0 Then
   ColorParse = Split(Message, "Á")
   For i = 0 To UBound(ColorParse)
       If ColorParse(i) <> "" Then
           ColorByte = Left(ColorParse(i), 1)
           ColorParse(i) = Right(ColorParse(i), Len(ColorParse(i)) - 1)
           AddText Form1.RTB1, GetColor(ColorByte), "[" & Time & "] < " & Username & "> " & ColorParse(i) & vbNewLine
       End If
   Next i
   Exit Sub
End If
'End of color parsing




At least provide your s/n on battle.net? And server?

[Eric]

Example:
ÁY Test for multiple ÁR words?

Using you addtext function this causes it to still show it up in the rtb as shown:

Test for muliple
words

I was looking for it to be a whole entire sentence.

Missing the point.  Unless your chat box is the exact width of Starcrafts, the bot will have a possibility of seeing colors differently than it would on a Blizzard client.

[Eli_1]

Code Select Expand


AddText Form1.RTB1, GetColor(ColorByte), "[" & Time & "] < " & Username & "> " & ColorParse(i) & vbNewLine

is where your problem lies -- Chr(10) & Chr(13), vbCrLf, and vbNewLine are all exactly the same thing. Instead, try rewriting your function like this.

Code Select Expand


If InStr(1, Message, "Á", vbTextCompare) <> 0 Then
   AddText Form1.RTB1, vbGreen, "[" & Time & "] < " & Username & "> "
   ColorParse = Split(Message, "Á")
   For i = 0 To UBound(ColorParse)
       If ColorParse(i) <> "" Then
           ColorByte = Left(ColorParse(i), 1)
           ColorParse(i) = Right(ColorParse(i), Len(ColorParse(i)) - 1)
           AddText Form1.RTB1, GetColor(ColorByte), ColorParse(i)
       End If
   Next i
   
   AddText Form1.RTB1, vbBlack, vbCrLf '// go to next line
   Exit Sub
End If


[MyndFyre]

Why not just parse the damn thing and rather than using AddChat, make a modified function such as AddC that doesn't append a NewLine to it.  Then when you're done parsing colors, append a NewLine.

You don't need to *replicate* the UTF-8 bug as it is shown in the Blizzard clients -- I suspect that if color lives longer than to the end of the line, people will be happier.