07-25-2008 02:51 PM
JoeLabView wrote:
You know what SS, I never saw your file until you just mentionned it.. 😮
07-25-2008 03:06 PM
smercurio_fc wrote:
"You've probably got automatic error handling turned on."
07-25-2008 03:33 PM
07-25-2008 04:19 PM - last edited on 06-04-2024 08:27 AM by Content Cleaner
Yep... it was because it of being centered.
SS, your underscore is a link to CLAD https://learn.ni.com/pages/certified-labview-associate-developer
R
07-25-2008 04:32 PM
ShotSimon wrote:
Ravens Fan,
I made the change and now my signature has a "_" before the attachment. I can't figure out how to get rid of it
07-25-2008 10:21 PM
ShotSimon wrote:
Nope it's turned off see below...and it's not my .vi it's an example straight out of LabVIEW
07-26-2008 04:42 AM - edited 07-26-2008 04:42 AM
Altenbach,
Nope I disagree, you see the confusion quite clearly...SS is not so good at error handling logic Thanks for clearing things up for me.
I have a side question since I currently don't have LabVIEW with me at home. If you were to put two of these on a front panel will LabVIEW only handle the last error in a sense chaining the error messages. I seem to recall when two were on the screen only one error out when you hit the cancel dialog twice?
Regards,
-SS
07-28-2008 09:11 AM
Got it...
So basically...put the error handeling in the canceled True case...and put the operable code in the canceled False case.
Thanks...once again I was overthinking things.
12-08-2014 02:16 PM
Hi,
I am developing a small app and I was checking this topic.
I went around the problem by using Clear Errors.vi
I think it is the quickest way to simply null the specific 43 error
12-08-2014 02:30 PM - edited 12-08-2014 02:34 PM
FabrizioDonnarumma wrote:I am developing a small app and I was checking this topic.
I went around the problem by using Clear Errors.vi
I think it is the quickest way to simply null the specific 43 error
Well, this is typically not a viable solution, for example if you are trying to read from or write to a file, and none is actually selected, the read operation will error out later. You actually want to skip all subsequent file IO if the dialog is canceled (e.g. using a case structure).
Your solution works only in a very small subset of scenarios.
Also, "clear errors" clear everything. Maybe there is a different error coming from upstream that is inportant.