-
Code:
' Error 1:
If TypeOf MyControl Is CommandButton Then Call ColorWordInBlue("TypeOf")
' Error 2:
Remove the problems with green coloring! In a Rem-keyword remark,
' there must be a space after "Rem" for it to be considered a remark.
' Error 3:
On Local Error Resume Next ' IsBlue("Local") = False, ShouldBeBlue("Local") = True
' Error 4:
SomeCodeGoesHere ' Something is wrong with remarks-after-code... Aren't these colors wrong?
' Well, it's working OK if it's not after code.
' Error 5:
MyString = "Well... If some of this Is colored blue, Then there's definitely a problem... Correct Me if I'm wrong."
' Error 6:
' The following line should be green, and the underline should be black. _
But they are not.
Administration? Are you there?
Get fixin'! :rolleyes:
-
[code]
Forgot the ending...
-
Well, I guess John will not have a good weekend while James goes crusing in Cyberland.
While that Is real, we can say "For you is an: Each !"
Function.Sub is obvious
[/code]
-
Well, I guess John will not have a good weekend while James goes crusing in Cyberland.
While that Is real, we can say "For you is an: Each !"
Function.Sub is obvious
Code:
MsgBox "For Next Loop!"
Remove it Is of course
-
Noticed? How my 2nd post was messed up? The same happened to Dennis Wrenn.
-
We do know about the limitations about the code colouring algorithms, but it is very hard to write one that counts for all prossible occurences while still being light and fast.
Consider it work-in-progress.
John
-
Yes! We actually had an administrator responding to this post! That is VERY rare these days!
-
What was that last comment about Escaflowne? Even if we do not reply to posts, we make a point of reading EVERY post in this forum, as well as looking over the General forum frequently.
John
-
Yeah...be kind to our administrators. I'm sure they have better things to do occasionally than spend all day going through the forums ;).
-
OK, I was just kidding.
Why are some people too sensitive?
