| FYI, I have been having problems with a ListView with about 100 items, and
| when I try to scroll vertically or horizontally by dragging the scroll
bar,
| it doesn't catch up immediately, but it looks highlighted and frozen, and
| catches up later.
|
| It turned out the reason for it was that I was using OutputDebugString too
| much, printing the text for each item and sumitem(There are 8 columns in
| this list view), and DebugView was open to view the output. When I close
| DebugView, the problem is gone. I was using OutputDebugString at a rate of
| 1000/Second.
|
| The items also appeared to flicker more frequently, I am not sure if it's
| related.
|
| Just a FYI, in case someone else is having this problem.
|
|

On Sat, 21 Aug 2010 10:43:28 -0400, "Nobody" <nob***@nobody.com>
wrote:

>"Mayayana" <mayayana@invalid.nospam> wrote in message
>news:i4ogsj$njl$1@news.eternal-september.org...
>>  I've seen you mention this function before.
>> I just looked up both, but I don't get it.
>> What's the advantage/reason for using
>> OutputDebugString rather than Debug.Print?
>> Likewise, what's the advantage of DebugView
>> over the Immediate window?
>
>If you have subclassing code that crashes the IDE when you stop it, then you
>have to compile it, but Debug.Print output won't show up.
>
>Note that when Debug.Print is compiled into an EXE, the call is not removed,
>but the result is discarded. If you have a statement like:
>
>Debug.Print "LicenseKeyVerify: UserName = " & UserName
>
>Then anyone can view your EXE with a Hex editor, or trace where the call is
>in the disassembly, and break the licensing scheme if it's shareware.
>
>However, Debug.Assert is removed from the EXE, so don't add code that take
>action like a function call. You can test this be compiling the following:
>
>Option Explicit
>
>Private Sub Form_Load()
>    Debug.Print MsgBox("Hello from Debug.Print")
>    Debug.Assert vbOK = MsgBox("Hello from Debug.Assert vbOK")
>    Debug.Assert vbYes = MsgBox("Hello from Debug.Assert vbYes")
>End Sub
>
>When I run this in the IDE using VB6, I get all three MsgBoxes, but the IDE
>breaks at the last Debug.Assert because the result is False. When I run this
>in an EXE, I only see the first MsgBox.
>