memory game vi

[A.A.A.]

Ahh, thanks. It's the first time I work with enum variables.

I fixed it.

I got errors regarding latch problems and comparison.

Between, what does enum stand for?

EDIT: Haven't noticed your edit, Ill fix the latch. Can you also tell me why there is such an error? Thanks

[RavensFan]

Enum is short enumerated datatype.  Basically words are given number values.

Latching means the boolean stays at its pressed value until the code reads the terminal at which time LabVIEW will return it back to its original value.  When you have local variables or value property nodes that can programmatically change the value of the control, or where you can read the value at multiple locations, how should LabVIEW handle the setting of the value and the "latching" of popping it back to its original value.  It can all lead to very indeterminate behavior of your program.

[abhi03215]

hello,

I am trying to make a memory game but my numbers (i.e) 0, 1, 2, 3 . . . , are not working. I am attaching my file below. Could anyone tell me the reason why are these buttons not working? and what can I do to fix them?

[altenbach]

---

@abhi03215 wrote:

I am trying to make a memory game but my numbers (i.e) 0, 1, 2, 3 . . . , are not working. I am attaching my file below. Could anyone tell me the reason why are these buttons not working? and what can I do to fix them?

---

You are making a huge number of beginner mistakes, so I recommend to go back to the LabVIEW tutorials. (The reason none of the buttons work is because the "Start" event locks the front panel until the event completes, but it never will because you cannot operate the controls.... 🐵

• Never have event structures inside event structures.
• A toplevel event structure typically has a while loop around it.
• There is little need for local variables or sequence structures

All you needs is a simple state machine. Look up that term and see how far you get.

[cbutcher]

I'd also suggest that this thread was 7 years old and your problem, whilst similar, is in fact separate.

You want to write your own version, and may well have your own problems (distinct from the original poster).

You should create a new thread and post there (after doing as was suggested and looking at the available learning materials and some details on the State Machine architecture)