Zugg Software :: View topic

Wanderer Joined: 01 Aug 2005 Posts: 76

I'm trying to understand the scope rules for the new package feature, and I need some help. I've created a new session called TEST, so it gets a package called TEST. I then created another package called YAP (yet another package) that got added to the session. I then created another package called YAP2. Now, I then created a variable in TEST named testVariable. In the YAP package, I created an alias named test that attempts to print the value of testVariable with the #ECHO command. Even if I enable the TEST package as visible for the YAP package/module, I cannot access testVariable from inside YAP. I cannot get access to testVariable until I move it into YAP2 and make YAP2 visible to YAP.

If this description of the packages/settings isn't clear, here's a picture of the 'All Packages' view in the package/settings editor.

What is going on? If I enable it making is visible/usable, should I not be able to see/use it, even if it's in the default session package?

Posted: Fri Mar 16, 2007 2:36 am

The variable's inside a window. Settings inside windows aren't ever visible to any settings outside that window. In order to make the setting visible outside the window, you need to put it in a module. In order to make the setting visible outside the package, you need to set that module either to Global or External publication.

So to make the variable accesible to the YAP alias, create a module inside the TEST package and set it to Global. Move testVariable inside it and you're done.

Wanderer Joined: 01 Aug 2005 Posts: 76

Ah, interesting. Thank you very much for clearing that up.

Posted: Fri Mar 16, 2007 11:07 am

Fang, that simple explanation was wonderful. I've not really needed or tried to mess with packages and modules and such, but your short reply "clicked" and helps me understand them and their relationships better than everything I've seen, even if I still don't need to use them.

Sometimes concise is very cool. Well done!

Wanderer Joined: 01 Aug 2005 Posts: 76

Beginner Joined: 20 Mar 2007 Posts: 27

I have been having a similar problem.

I have this:

- [Main Window]
| |
| |_ [Main Module] (set to global)
|
|
|
|
-[New Package] (set to global)

In "Main Module" I have the HEALTH variable.
In "New Package" I have the following alias;
#ALIAS autosip {#IF (@health<@htd) {drink health} {#ECHO Nothing}}

Very basic, but every time I autosip, I drink health no matter what my health is. HTD is a set number that is figured with triggers in "New Package".
Thought I set everything as mentioned in this topic, but doesn't seem to work for me.

Any advice?

Later I tried just moving everything need to the "New Package" and for some reason my #IF is reading backwards?! My Health is GREATER THEN the htd number and it tries to drink health?!

Posted: Tue Mar 20, 2007 6:37 pm

Well for starters, you have you module under your window. This should not be. They are not designed to work like that (it's an outstanding to-do for Zugg to disable the capability to do so.).

Try this organization.

- [Main Window]
|
- [Main Module]
|
|
- [New Package]

If that still doesn't work try putting a space in the command like so. I'm not are of any parsing issues in this scenario but it's possible you uncovered a parsing error. i can't test this since I'm not able to access CMUD at work.

#ALIAS autosip {#IF (@health < @htd) {drink health} {#ECHO Nothing}}

Posted: Wed Mar 21, 2007 1:34 am

Also, my advice would be that if you don't intend to give out your packages, you probably don't need to use them. Packages overcomplicate things in most situations. That said, there's definitely something weird going on here.

I recreated the scenario you describe (minus the improper module placement) and had the alias print the value of @health that it was seeing - it always printed null. Since null's interpreted as 0 by expression evaluation, that's why it's always coming out as true.

This shouldn't be happening, because the alias will look in global modules after it's looked in the current package, won't it? Can anyone else confirm this happening.

If it does turn out to be a bug you should start another thread too.

Beginner Joined: 20 Mar 2007 Posts: 27

Posted: Thu Mar 22, 2007 1:04 am

Post a new thread about this bug and Zugg will take a look at it. I can't get the different classes thing to fail, which would suggest that your package is corrupt, but the different packages thing still fails even with totally new packages. They'll probably suggest that you mail the package to support@zuggsoft.com, but post the thread to make sure.

Posted: Thu Mar 22, 2007 7:48 am

I agree with Fang... I just tested your #if statement and it works perfectly fine here. So I suspect your package maybe messed up from earlier versions.