Karl,

Yes, I would love that. I would like a break based upon a certain value:

examples
break if sTempStr > ""
break if iRetVal = 0

etc.

Jim

"Karl A. Sørensen" <kas@kamstrup-ems.no> wrote in message
news:69H1D2M$FHA.1632@dacmail.dataaccess.com...
> Conditional breakpoints would be great in the debugger
>
> Regards
> Karl
>
>
> "Bob Worsley" <bworsley@comcast.net> wrote in message
> news:ymUg2yg9FHA.2156@dacmail.dataaccess.com...
>>
>> I'm not sure if this has been suggested before or not, if so then it's a
>> reinforcement for that argument.
>>
>>
>>
>> The debugger, IMHO, as it currently exists in VDF 10, is a) too complicated
>> and b) tries to do too much.
>>
>>
>>
>> For the complicated part, years ago when it first came out I was able to
>> easily set watches and some other associated stuff, today I find it
>> difficult at best, and in some cases near impossible. The last time I tried
>> to set a watch I think I got it to sorta work, but finally gave it up and
>> went back to showln's and logging to a file. Sometimes I use the tracing,
>> and that works well, but even that's got way too much output to be
>> practical. I realize others are successfully using the debugger, but I
>> think that newbies to VDF are going to be in my boat - figuring out how to
>> make it work is really tough and maybe it just isn't worth it.
>>
>>
>>
>> As to the "tries to do too much" part, I'd really like to see a simple
>> switch that permits me to eliminate anything in dfallent from being stepped
>> through. In almost 100% of my problems it's me that causes the difficulty
>> (surprise!) and it's my code that I need to troubleshoot, not DAC's. Of
>> course that capability being available is good, and sometimes necessary, but
>> in most cases by knowing the symptoms and stepping through my own code I can
>> see what the problem is and fix it quickly. I don't need all the grief of
>> having to walk through all the boilerplate code, most of the time it's just
>> not necessary. Yes, I can step over stuff, but that's sometimes like
>> walking through a minefield. One wrong click and I'm wading through miles
>> of dfallent stuff and can't get out of it unless I kill the process.
>>
>>
>>
>> I'm going to go out on a limb here and bring up the vb.net debugger which I'
>> ve been using of late in my day job. For the most part it's doing what I
>> mentioned above. One really great feature is that when you get to a
>> breakpoint or start stepping, all you have to do is hold the cursor over a
>> variable to see what the current value is - a tooltip pops up to tell you,
>> no need to go to menus or jump through other hoops.
>>
>>
>>
>> I think the point here is that "less is more", at least for me. Haven't
>> looked at the VDF 11 debugger to see if it's any different...
>>
>>
>>
>> Set Soap_box_mode to off
>>
>> Bob
>>
>>
>>

>
>