Wiring diagram keeps popping up during execution

[ken_eric@my-deja.com]

An easy newbie question for you die-hards out there...

I have a program that upon execution, forces the wiring window to the
forefront and pauses over a certain area of code. There is apparently
nothing wrong with this part of the code (a simple case structure), as I
can click to unpause or step over with no error messages whenever the
program gets to this point. This hold-up is annoying because it halts
up the rest of the program and I don't see the point of it.

My question is wheter or not it is possible to force the program not to
pause and ask me for redundant stepping requests. Conversely, is it
possible to force pauses at particular points in the program? Might
have done it uninentionally...

Th
anks


Sent via Deja.com
http://www.deja.com/

[wiebe@CARYA]

Hi,

You've probbably placed a breakpoint somewhere. This can be seen in the
diagram as a small red dot. If you cannot find it, use "project" from the
menu, "Find", select the object "Breakpoint" in "Other".

Regards,

Wiebe Walstra.

Note: To place them, make the tools palate visible, select the red dot, with
arrow, and put it in the diagram.

--
AIR technical Automation
www.air.nl
wrote in message news:95e40d$l83$1@nnrp1.deja.com...
An easy newbie question for you die-hards out there...

I have a program that upon execution, forces the wiring window to the
forefront and pauses over a certain area of code. There is apparently
nothing wrong with this part of the code (a simple case structure), as I
can click to unpause or step over with n
o error messages whenever the
program gets to this point. This hold-up is annoying because it halts
up the rest of the program and I don't see the point of it.

My question is wheter or not it is possible to force the program not to
pause and ask me for redundant stepping requests. Conversely, is it
possible to force pauses at particular points in the program? Might
have done it uninentionally...

Thanks


Sent via Deja.com
http://www.deja.com/

[ken_eric@my-deja.com]

Hi,

Thanks for the suggestion.

Checked for break points and there were none. Came up with neither the
red dot nor a positive on the deliberate search. Now I know how to
check for breaks in the future though...:)

Cheers



In article <981116177.21044.0.pluto.d4ee054f@news.demon.nl>,
"AIR Tech. Autom." wrote:
> Hi,
>
> You've probbably placed a breakpoint somewhere. This can be seen in
the
> diagram as a small red dot. If you cannot find it, use "project" from
the
> menu, "Find", select the object "Breakpoint" in "Other".
>
> Regards,
>
> Wiebe Walstra.
>
> Note: To place them, make the tools palate visible, select the red
dot, with
> arrow, and put it in the diagram.
>
> --
> AIR technical Automation
> www.air.nl
> eja.com> wrote in message
news:95e40d$l83$1@nnrp1.deja.com...
> An easy newbie question for you die-hards out there...
>
> I have a program that upon execution, forces the wiring window to the
> forefront and pauses over a certain area of code. There is apparently
> nothing wrong with this part of the code (a simple case structure), as
I
> can click to unpause or step over with no error messages whenever the
> program gets to this point. This hold-up is annoying because it halts
> up the rest of the program and I don't see the point of it.
>
> My question is wheter or not it is possible to force the program not
to
> pause and ask me for redundant stepping requests. Conversely, is it
> possible to force pauses at particular points in the program? Might
> have done it uninentionally...
>
> Thanks
>
> Sent via Deja.com
> http://www.deja.com/
>
>


Sent via Deja.com
http://www.deja.com/

[Stephen Gray]

Make sure that you don't have Execution Highlighting selected. That's
the light bulb on the menu bar of the wiring diagram.

Regards,
Stephen

ken_eric@my-deja.com wrote:
>
> Hi,
>
> Thanks for the suggestion.
>
> Checked for break points and there were none. Came up with neither the
> red dot nor a positive on the deliberate search. Now I know how to
> check for breaks in the future though...:)
>
> Cheers
>
> In article <981116177.21044.0.pluto.d4ee054f@news.demon.nl>,
> "AIR Tech. Autom." wrote:
> > Hi,
> >
> > You've probbably placed a breakpoint somewhere. This can be seen in
> the
> > diagram as a small red dot. If you cannot find it, use "project" from
> the
> > menu, "Find", select the object "Breakpoint" in "O
ther".
> >
> > Regards,
> >
> > Wiebe Walstra.
> >
> > Note: To place them, make the tools palate visible, select the red
> dot, with
> > arrow, and put it in the diagram.
> >
> > --
> > AIR technical Automation
> > www.air.nl
> > wrote in message
> news:95e40d$l83$1@nnrp1.deja.com...
> > An easy newbie question for you die-hards out there...
> >
> > I have a program that upon execution, forces the wiring window to the
> > forefront and pauses over a certain area of code. There is apparently
> > nothing wrong with this part of the code (a simple case structure), as
> I
> > can click to unpause or step over with no error messages whenever the
> > program gets to this point. This hold-up is annoying because it halts
> > up the rest of the program and I don't see the point of it.
> >
> > My question is wheter or not it is possible to force the program not
> to
> > pause and ask me for redundant stepping requests. Conversely, is it
> > possible to force pauses at
particular points in the program? Might
> > have done it uninentionally...
> >
> > Thanks
> >
> > Sent via Deja.com
> > http://www.deja.com/
> >
> >
>
> Sent via Deja.com
> http://www.deja.com/

[ken_eric@my-deja.com]

Heh heh heh. No, it wasn't that either. 🙂

Happens only if a particular case occurs. When the other case occurs,
the program doesn't even stop.

Cheers!


In article <3A7ACD41.30434FA1@swri.org>,
Stephen Gray wrote:
> Make sure that you don't have Execution Highlighting selected. That's
> the light bulb on the menu bar of the wiring diagram.
>
> Regards,
> Stephen
>


Sent via Deja.com
http://www.deja.com/

[Spencer]

I had about the same thing happen a while back on some code. It about drove
me nuts.

It turned out that there was a breakpoint but it was hidden. Unfortunately,
it didn't show itself until I started deleting portions of my code. When I
deleted a string control, all of a sudden a breakpoint appeared on the
broken wire where there was none before. I removed the breakpoint,
reassembled the code, and it worked fine. I would use the execution
highlighting to watch exactly where the breakpoint is triggered, and then
maybe delete small sections to see if the same thing happens. I know this
isn't a great solution, but it worked for me. Maybe it will work for you
(no guarantees).

Make sure you can re-create the code though, print it out
, back it up, I
don't want to be held responsible if you can't get it back to proper working
order.

Spencer

wrote in message news:95entl$6aj$1@nnrp1.deja.com...
> Heh heh heh. No, it wasn't that either. 🙂
>
> Happens only if a particular case occurs. When the other case occurs,
> the program doesn't even stop.
>
> Cheers!
>
>
> In article <3A7ACD41.30434FA1@swri.org>,
> Stephen Gray wrote:
> > Make sure that you don't have Execution Highlighting selected. That's
> > the light bulb on the menu bar of the wiring diagram.
> >
> > Regards,
> > Stephen
> >
>
>
> Sent via Deja.com
> http://www.deja.com/

[RolfO]

On Fri, 02 Feb 2001 14:11:03 GMT, ken_eric@my-deja.com wrote:

>Hi,
>
>Thanks for the suggestion.
>
> Checked for break points and there were none. Came up with neither the
>red dot nor a positive on the deliberate search. Now I know how to
>check for breaks in the future though...:)
>

You could also check out for a red frame on the inside of a case,
while, sequence or for loop. It indicates a brekpint set on that
frame.

Regards
Rolf

>
>
>In article <981116177.21044.0.pluto.d4ee054f@news.demon.nl>,
> "AIR Tech. Autom." wrote:
>> Hi,
>>
>> You've probbably placed a breakpoint somewhere. This can be seen in
>the
>> diagram as a small red dot. If you cannot find it, use "project" from
>the
>> menu, "Find", select the object "Breakpoi
nt" in "Other".
>>
>> Regards,
>>
>> Wiebe Walstra.
>>
>> Note: To place them, make the tools palate visible, select the red
>dot, with
>> arrow, and put it in the diagram.
>>
>> --
>> AIR technical Automation
>> www.air.nl
>> wrote in message
>news:95e40d$l83$1@nnrp1.deja.com...
>> An easy newbie question for you die-hards out there...
>>
>> I have a program that upon execution, forces the wiring window to the
>> forefront and pauses over a certain area of code. There is apparently
>> nothing wrong with this part of the code (a simple case structure), as
>I
>> can click to unpause or step over with no error messages whenever the
>> program gets to this point. This hold-up is annoying because it halts
>> up the rest of the program and I don't see the point of it.
>>
>> My question is wheter or not it is possible to force the program not
>to
>> pause and ask me for redundant stepping requests. Conversely, is it
>> possible to force pauses at particular points i
n the program? Might
>> have done it uninentionally...

[ken_eric@my-deja.com]

For the sake of posterity, here's how I got around the problem:

By clicking on the icon of the VI, choosing window options and disabling
the "allow debugging" option, I basically told the VI to stop bugging
me. There might be a minor nonideality in my code, but since it's
nothing to stop the program from doing what I want it to do (works when
I step through it manually anyway -- what more would I want to show me
it works?) I'm leaving it at that.

An old-hat trick to the pros, but at least now I know...

Thanks to all who helped.





In article <95e40d$l83$1@nnrp1.deja.com>,
ken_eric@my-deja.com wrote:
> An easy newbie question for you die-hards out there...
>
> I have a program that upon execution, forces the wiring window to the
> forefront and pauses
over a certain area of code. There is apparently
> nothing wrong with this part of the code (a simple case structure), as
I
> can click to unpause or step over with no error messages whenever the
> program gets to this point. This hold-up is annoying because it halts
> up the rest of the program and I don't see the point of it.
>
> My question is wheter or not it is possible to force the program not
to
> pause and ask me for redundant stepping requests. Conversely, is it
> possible to force pauses at particular points in the program? Might
> have done it uninentionally...
>
> Thanks
>
> Sent via Deja.com
> http://www.deja.com/
>


Sent via Deja.com
http://www.deja.com/

[judith m recca]

It is also possible to have accidentally set a breakpoint in a location that
is currently not being displayed, maybe on a wire that is under the border
of a case or loop. Try doing a project search for breakpoints.
- Vinny Recca

ken_eric@my-deja.com wrote:

> For the sake of posterity, here's how I got around the problem:
>
> By clicking on the icon of the VI, choosing window options and disabling
> the "allow debugging" option, I basically told the VI to stop bugging
> me. There might be a minor nonideality in my code, but since it's
> nothing to stop the program from doing what I want it to do (works when
> I step through it manually anyway -- what more would I want to show me
> it works?) I'm leaving it at that.
>
> An old-hat trick to the pros, but
at least now I know...
>
> Thanks to all who helped.
>
> In article <95e40d$l83$1@nnrp1.deja.com>,
> ken_eric@my-deja.com wrote:
> > An easy newbie question for you die-hards out there...
> >
> > I have a program that upon execution, forces the wiring window to the
> > forefront and pauses over a certain area of code. There is apparently
> > nothing wrong with this part of the code (a simple case structure), as
> I
> > can click to unpause or step over with no error messages whenever the
> > program gets to this point. This hold-up is annoying because it halts
> > up the rest of the program and I don't see the point of it.
> >
> > My question is wheter or not it is possible to force the program not
> to
> > pause and ask me for redundant stepping requests. Conversely, is it
> > possible to force pauses at particular points in the program? Might
> > have done it uninentionally...
> >
> > Thanks
> >
> > Sent via Deja.com
> > http://www.deja.com/
> >
>
> Sent via Deja.com
> http://w
ww.deja.com/

[wiebe@CARYA]

Hi,

Baybe a little late, but it could be the "Suspend When Called" option. The
VI will popup when called, and the run button will be changed in a arrow up,
with a line under it.

Regards,

Wiebe Walstra.
--
AIR technical Automation
www.air.nl

wrote in message news:95rkn4$cbk$1@nnrp1.deja.com...
For the sake of posterity, here's how I got around the problem:

By clicking on the icon of the VI, choosing window options and disabling
the "allow debugging" option, I basically told the VI to stop bugging
me. There might be a minor nonideality in my code, but since it's
nothing to stop the program from doing what I want it to do (works when
I step through it manually anyway -- what more would I want to show me
it works?) I'm leaving it
at that.

An old-hat trick to the pros, but at least now I know...

Thanks to all who helped.





In article <95e40d$l83$1@nnrp1.deja.com>,
ken_eric@my-deja.com wrote:
> An easy newbie question for you die-hards out there...
>
> I have a program that upon execution, forces the wiring window to the
> forefront and pauses over a certain area of code. There is apparently
> nothing wrong with this part of the code (a simple case structure), as
I
> can click to unpause or step over with no error messages whenever the
> program gets to this point. This hold-up is annoying because it halts
> up the rest of the program and I don't see the point of it.
>
> My question is wheter or not it is possible to force the program not
to
> pause and ask me for redundant stepping requests. Conversely, is it
> possible to force pauses at particular points in the program? Might
> have done it uninentionally...
>
> Thanks
>
> Sent via Deja.com
> http://www.deja.com/
>


Sent via Deja.com
http://www.de
ja.com/