find breakpoint programmatically

[craigc]

Hi Altenbach,

I have been doing that method, in fact i usually remove all my breakpoints as soon as i have finished with them.  However as i said in post #3  The only problem is my memory!  However thanks to ben i have found what i have been looking for, which is ideal for my situation.

Failing that the other option would have been a huge dialog box telling myself to remove all the break points.  I swear id lose my head of it wasnt screwed on.

Craig

Edit - replaced crass version of losing my head if it wasnt screwed on with more pc counterpart.

Message Edited by craigc on 09-14-2007 10:07 AM

[altenbach]

It might be really useful if a VI that contains a breakpoint somewhere in the hierarchy would stand out in some way. Maybe the run button should have a red color or frame, or red run arrow, for example.

 (Suggestion!)

There is always the product suggestion page. 🙂

Message Edited by altenbach on 09-14-2007 08:35 AM

[Ben]

I beleive "Show Warnings" will reflect the Breakpoints being set.

All you have to do is WRITE PERFECT CODE to be able to use that option.

Ben

[craigc]

Altenbach,

That would have saved me many a blood sweat and tear!  I think you should definitely suggest that, i would do it for you but that would be plagiarism he he.

Craig

[craigc]

BEN - "All you have to do is WRITE PERFECT CODE to be able to use that option. "

LOL, write code is a good start for me 🙂  I have had to re-write a lot of my code after i came across the gold rumberg thread. (Forgot his name - see i told you my memory sucks)

[Ben]

"... the gold rumberg thread..."

Thats fine. I'm dyslexic so my brain automatically unscrambles that text as "Rube Goldberg". Thank you for accomodating me.

Ben

[craigc]

lol, No problem,  Thanks for reminding me. it will stick eventually, however breakpoints and names are sort of low down in the "committ to storage" priority list.  (Although i think the remove breakpoints should be moved up the list a couple of notches)

[altenbach]

SImilarly, it happened to me in the past that I had a subVI left in execution highlighting mode and was really puzzled why my toplevel was suddenly so slow. I this case, we could have a yellow run arrow on the toplevel to indicate that fact. 🙂

[craigc]

Yep i have had that before as well, it doesnt help that the sub vi had a while loop in it homing in something to the nth degree!  As you say a yellow arrow would do the job.  Mayby a orange (Red and yellow mixed) arrow if there are both! 🙂

Its just really frustrating knowing you got to wait another day to do any "real" work, i came in to work in the morning and there was no data to look at! so my day has been setting off the program again minus one little Break point and watching it go while doing paperwork on the side.  And believe me paperwork is always my last priority 🙂

[TCPlomp]

Orange if it uses 'Retain wire values' because of the excessive memory use.
Blue if it uses scripting

Ton