LabVIEW
more descriptive text in 2 button dialog
To answer the first question, you can simply use the "Concatenate Strings" function and build whatever text string you would like displayed. So you would have 3 terminal "Concatenate Strings" function with a string constant of 'Is ' on the first terminal, your serial number on the second terminal and ' correct?' on the third. (all without the quotes, that's just to show spaces) This will build the string you want.
As for the second question, I've never seen a control disappear on it's own. You can hide front panel objects using property nodes, but they should not do it by themselves. It's hard to guess what's happening without seeing your code. The only thing I can suggest is to delete the control and replace it. It may be corrupted somehow, but this do
esn't even seem vary likely.
Ed
As for the second question, I've never seen a control disappear on it's own. You can hide front panel objects using property nodes, but they should not do it by themselves. It's hard to guess what's happening without seeing your code. The only thing I can suggest is to delete the control and replace it. It may be corrupted somehow, but this do
esn't even seem vary likely.
Ed
Using the Abort button to stop your VI is like using a tree to stop your car. It works, but there may be consequences.
Well, the text on the dialog is just a string. You can build any string you want, e.g. wire your number to "format into string" first, using Is %04d correct ? as format specifier, and wire the output to the two button dialog.
If the entry box disappears from the front panel, somebody must have programmed it this way. Look for a property node setting with visible set to "false". (right-click on the control, the select "find property nodes").
Are you modifying somebody elses program?
If the entry box disappears from the front panel, somebody must have programmed it this way. Look for a property node setting with visible set to "false". (right-click on the control, the select "find property nodes").
Are you modifying somebody elses program?
The Visable attribute of a property node is what hides the control on the front panel. A 'False' on the Visable attribute will hide the control. There is a String Length function reading the serial number length as it is entered, as soon as the length = 4, the 'Not Equal' function will output a False to the Visable property node hiding the control on the front panel.
For help on property nodes, right click on the attribute itself (Visable in this case) and select 'Help for Visable'. This will open the help to the page for that attribute and tell you what it does.
The Value node outside the loop on the left is clearing the string control by writing an empty string to Value attribute.
I've modified you VI to what I think you want
it to do. The number lenght is read until it is 4 characters, then opens the dialog for conformation and either stops and outputs the number, or clears the control so it can be re-entered. It's setup to used as a sub-vi so you can just drop it on the diagram where you need it.
Ed
For help on property nodes, right click on the attribute itself (Visable in this case) and select 'Help for Visable'. This will open the help to the page for that attribute and tell you what it does.
The Value node outside the loop on the left is clearing the string control by writing an empty string to Value attribute.
I've modified you VI to what I think you want
it to do. The number lenght is read until it is 4 characters, then opens the dialog for conformation and either stops and outputs the number, or clears the control so it can be re-entered. It's setup to used as a sub-vi so you can just drop it on the diagram where you need it.
Ed
Well, your code sure looks like beginners work and it is ever worse to leave it to another beginner to clean it up a bit ;-). Don't despair, you'll quickly get the hang of it!
The "value write" at the beginning clears the entry box in case there are some leftovers in it from an earlier run.
The entire diagram is overly complicated, e.g. the feedback node is a kludge to fix a wiring loop that would otherwise break the code. Also there is no time control in the loop. Basically, it checks the input and rewrites the property nodes inside the loop as fast as the machine can handle it (thousands of times per second), bogging down everything else. Personally, I also don't like the hiding of the control. If it should not be changed later, disable it. It
is nice if the operator can check the serial number even at a later point in time.
Think about the task as you would explain it to someone, it is much simpler that your code would suggest:
(1) Check the entry field until the length is four.
(2) Once this happens, verify input with popup.
I would use a simple event structure as in the attached example. Modify as needed. You might add some extra input checking, e.g. remove leading and trailing spaces and check for disallowed characters.
The "value write" at the beginning clears the entry box in case there are some leftovers in it from an earlier run.
The entire diagram is overly complicated, e.g. the feedback node is a kludge to fix a wiring loop that would otherwise break the code. Also there is no time control in the loop. Basically, it checks the input and rewrites the property nodes inside the loop as fast as the machine can handle it (thousands of times per second), bogging down everything else. Personally, I also don't like the hiding of the control. If it should not be changed later, disable it. It
is nice if the operator can check the serial number even at a later point in time.
Think about the task as you would explain it to someone, it is much simpler that your code would suggest:
(1) Check the entry field until the length is four.
(2) Once this happens, verify input with popup.
I would use a simple event structure as in the attached example. Modify as needed. You might add some extra input checking, e.g. remove leading and trailing spaces and check for disallowed characters.
