Highlight execution and breakpoints not working correclty

[Dave76]

HI,

I have a vi I am working on that I am trying to debug, before I run the vi I can select highlight execution mode and that works.  but If I run the vi then try to enable highlight execution mode nothing happens, I am sure I have been able to do this in the past.

likewise with breakpoints I can set them while the vi is not running and they pause when the code reaches them.  I cant un pause them or run highlight execution mode if fact do anything except stop the vi. The cursor shows as a text select cursor no mater where I place it. 

both of these problems seem to be triggered by a certain event but I cant figure it out because sometimes they do work. it is on an event case I am trying to debug that only has about 5 cases.  The vi is not re-entrant and is normal priority.

the code is too large to share on here but I'll work on trying to create a simplified version that shows the fault. that I can share.

I am using LabVIEW 2018 with the latest updates, has anyone else seen anything like this?  

[paul_cardinale]

I have seen very sluggish IDE response when a VI is running (usually when something in the VI is hogging resources).

[ikaiser]

Text cursor sounds wrong. I think I remember something similar, but I did not connect that to any problem with LabVIEW itself, but with computer issues (100% CPU).

When having a clone or password-protected VI in front of you, it can behave like this, but you mentioned "not re-entrant" so this should be fine.

Just to check: You had selected the breakpoint tool, or automatic tool selection, right?

[Dave76]

My PC is now intermittently playing up (showing 100% CPU) and the problem i had has gone away, i am due to get a new pc within the next month so i will see how things are after that.

thanks for your comments 

[Dave76]

HI sorry for bringing this one back up again but i never did get it sorted.  i thought it was because my windows 7 PC was playing up, i have since been given a new windows 10 laptop and i have upgraded to Labview version 19.0f2(32bit) and i still have the same problem.

I have attached a very cut down version of the VI used, the vi doesn't do anything so please don't comment on that side of things.  What i would like you to try is to click the run button then try these 4 things, try to add a probe or stop it using the abort execution button or try to turn on highlight execution or try to enable a breakpoint somewhere in the code.  when i try any of these 3 things with this vi they do not do anything and i don't know why.  

Anyone know why?

[JÞB · Accepted solution]

---

@Dave76 wrote:

HI sorry for bringing this one back up again but i never did get it sorted.  i thought it was because my windows 7 PC was playing up, i have since been given a new windows 10 laptop and i have upgraded to Labview version 19.0f2(32bit) and i still have the same problem.

I have attached a very cut down version of the VI used, the vi doesn't do anything so please don't comment on that side of things.  What i would like you to try is to click the run button then try these 4 things, try to add a probe or stop it using the abort execution button or try to turn on highlight execution or try to enable a breakpoint somewhere in the code.  when i try any of these 3 things with this vi they do not do anything and i don't know why.  

Anyone know why?

---

Yes, I know why

The Front panel is modal

[Dave76]

Thanks, school boy error.  i should have spotted that.

[ikaiser]

Good thing that you are not in school anymore 

(Guessing from the "76" in your username)

[Mark_Yedinak]

Your VI is set to run as a dialog window so the focus is locked to the front panel, hence you can't interact with the block diagram.

[JÞB]

---

@Mark_Yedinak wrote:

Your VI is set to run as a dialog window so the focus is locked to the front panel, hence you can't interact with the block diagram.

---

Well spotted Mark