Zugg Software :: View topic - Access class/variable from within an expression trigger? [3.33a Pro] (Solved)

Novice Joined: 22 Jun 2009 Posts: 38

I have a class named "stats." I have a trigger:

Wizard Joined: 22 Mar 2007 Posts: 2320

Right now, your code looks for a variable named @stats (let us assume that @stats contains the word "something"), and then triggers on text that looks like:
"something/var1 - something/var2"
and it puts that string into %1.

Can you explain exactly what you do want to do? Explain what @stats is, exactly where your variables are, and what string this is supposed to match.

Wanderer Joined: 21 Aug 2008 Posts: 85

[edit][/edit]

Novice Joined: 22 Jun 2009 Posts: 38

My apologies. for not being clear. I'm performing a math operation here. I want to subtract stats/var2 from stats/var1. Another way to write this is var1-var2. The variables are members of a class in my package called stats, so i'm referencing the variables by typing them as classname/varname, which works in the script of the trigger, but not in the pattern. I'm subtracting two variables, and comparing their difference to a constant number:

GURU Joined: 23 Dec 2000 Posts: 4834 Location: USA

@//module/class/.../varname.

Novice Joined: 22 Jun 2009 Posts: 38

I don't quite understand. What's the module? this trigger is in my "auto" class, and the variable is in the "stats" class. Both classes are under the root of the same window. But when I try to reference the variables in the "stats" class by using "stats/var1" it doesn't recognize the variable.

Wizard Joined: 22 Mar 2007 Posts: 2320

The module in Matt's example would be the name of the window. So, you could reference the variable as
@//windowname/stats/var1

Or you don't have to specify the window name:
@/stats/var1

When you use @stats/var1 it will interpret @stats as a variable itself. Are you certain you even need to specify the class? If you don't have any other var1 elsewhere, you can just do @var1. This is a good reason to use unique and descriptive variable names.

In addition, you cannot normally perform mathematics within a trigger pattern. Putting things within parentheses in a trigger pattern means something completely different from using it in a Cmud command. In a trigger pattern, it means "store whatever is captured by this sequence in a temporary variable", the variables being automatically named %1, %2, etc. That's why Myrkul suggested using %%eval, which is a way to force a function to be called within a trigger pattern. In this case, it would execute %eval() on the string and perform the subtraction and would match any string matching the resulting number.

However, now it looks like you actually are trying to do an expression trigger, which is completely different. Parentheses do work in expression triggers the way you expected. The trigger you have posted is a normal string-matching pattern. You have not specified that it should be an expression trigger. The trigger you want should be something like this:

Novice Joined: 22 Jun 2009 Posts: 38

Alright it seems I didn't use the right terminology. I am using an expression trigger, and I have exactly what's in rahab's code section above. It doesn't work, however. I'm using the package editor, and i can see that even with an expression trigger, cmud does not recognize the above code in parentheses as a variable. the entire @/stats/var1 isn't recognized as a variable. None of it is. Using the module when referencing the variable produces the same results. Does this mean i just can't reference a variable from within another class in an expression trigger?

thanks again for everyone's time and effort.

GURU Joined: 23 Dec 2000 Posts: 4834 Location: USA

Aren't () and {} mutually exclusive in expression-trigger patterns?

ie, this is wrong:

#trigger {expression}

and this is right:

#trigger (expression)

Novice Joined: 22 Jun 2009 Posts: 38

They may be true, but i'm not using the command line. I'm using the package editor.

Novice Joined: 22 Jun 2009 Posts: 38

Thanks Rahab. It looks like you were right. What confused me was that the variable name wasn't getting highlighted in blue. All my others did, so I expected this one to as well. The expression does not highlight the class variables at all, but this trigger does fire, and works as intented! Thank you all!