Zugg Software :: View topic - Problem with variables

Beginner Joined: 12 Mar 2012 Posts: 23

Hello!

I am having some issues with my variables. All of them seem to loose their value for a few ms every now and then. Then problem is, when I'm evaluating an IF statement, this can ruin everything.
An example for the issue I am having:

#if ((@healthperc<40) || (@staminaperc <20)) {#say P - first true - @healthperc @staminaperc} {#say P - first false - @healthperc @staminaperc}
#if ((@healthperc<40) || (@staminaperc<20)) {
#if ((@healthperc<40) || (@staminaperc<20)) {#say second true - @healthperc @staminaperc} {#say second false - @healthperc @staminaperc}
*something here*
}
} {#NOOP}

Alright, so what this does: Check whether healthperc or staminaperc under a specific value. If at least one of them is, it says true/false and value of the variables.
Next line, same variables, same check, enters the next block only if it is true, else {#NOOP}.
Next line checks again, same as the first line. rest isn't important.

Problem is what I receive in my window:
P - first false - 100 100
second false - 100 100

The 2nd line should not even appear, because the previous statement should not have been evaluated as true. After a while my command line doesn't accept any alias, only if I send them with #EXEC.

Another extreme:
#if ((@healthperc<40) || (@staminaperc<20)) {#say second true - @healthperc @staminaperc} {#say second false - @healthperc @staminaperc}

What I receive:
second true - 84 77

Note: This block is within an alias which is looping until a a statement is true.It may loop for a very long time (0-2+ hours). the no-value periods reach such a time frame over time that I can notice the variable go blank on my status window.
Note: Version 3.34

Wizard Joined: 22 Mar 2007 Posts: 2320

Could you please actually cut and paste the entire relevant section of code within [code]...[/code] markers? Something is clearly missing because it looks like the last "} {#NOOP}" is not part of any of your #IF statements. The {} braces don't match. It is impossible to tell whether you have an error in your code.

Are there other scripts which are setting @healthperc and @staminaperc? Are those scripts running in separate threads? If so, you could very easily have thread conflict. When writing code that runs in separate threads, it can take some care to keep the threads from conflicting. You may want to study the documentation for #WAIT, #SECTION, and Threads. Without a great deal more information about all of your code, we can't give much help to make it thread-safe.

Beginner Joined: 12 Mar 2012 Posts: 23

Oh, I am sorry, I probably left in an extra } after cutting out the irrelevant loop part. My bad.

Wizard Joined: 22 Mar 2007 Posts: 2320

Any time you use #WAIT, #WAITFOR, #WAITSIGNAL, etc., you are creating a new thread which runs in the background. I think you must have been using threads if this alias was "looping until a a statement is true" as you said. Whenever you start using threads, you have the potential for collisions, where different pieces of code are trying to set or get the value of the same variable.

You say "threading the looping alias seems to work wonders". What do you mean by that? Do you mean you inserted a #SECTION command?

Use of #SECTION commands is good for preventing other threads from changing variables when you don't want them changed. But you also have to be careful not to put too much of your code inside #SECTION. Whenever a bit of code inside #SECTION is running, no other threads can run. Essentially, it temporarily halts threading so only the one bit of code is running. If you use it more often than you need, you end up eliminating all the advantages of threading, and potentially prevent other parts of your code from ever running.

Wizard Joined: 22 Mar 2007 Posts: 2320

Oh, by the way, you don't need to use a #NOOP for your FALSE command statements. Simply drop the FALSE command statement completely. The FALSE statement is optional. Both of these syntaxes are valid: