Zugg Software :: View topic - [1.34] Bug: expression trigs not working in packages

Posted: Tue Jul 17, 2007 9:25 am

1. Open a blank settings file.

2. Create the following expression trig and variable from the command line:

#TR (@testvar=1) {#SH testvar is 1}
testvar=0

3. Now enter "testvar=1" to command line. "testvar is 1" is displayed in the window as expected.

4. Because no class was specified, this expression trigger was created in the default package/window. So now, move this trigger and variable to a new package, and attempt to make it fire by entering "testvar=0" and then "testvar=1" to the command line. It won't fire.

Edit: I changed the subject and content, as I am fairly sure it is a bug now, while originally I thought I was just being a retarded user ;)
Edit2: I changed the bit in bolded italics.

Posted: Tue Jul 17, 2007 9:44 am

Deleted as I edited the original post instead. No need for you to read through all my 'working stuff out as I post and edit multiple times' hehe.

Posted: Tue Jul 17, 2007 1:31 pm

Working as intended, really. Settings inside windows aren't visible outside that window by design. If you put @testvar in a global module in the same package as the window, and the trigger in a global module in another package, it should be working fine.

But it isn't. It's still not working even then. Which sucks.

Posted: Tue Jul 17, 2007 10:53 pm

I wasn't clear in my post. When moving the trigger, move the variable with it.