Zugg Software :: View topic

Novice Joined: 26 Jan 2009 Posts: 32

I can not work out how to access Package variables via room scripts is there some additional syntax that needs to be applied?

Additionally Right clicking in the mapper and selecting execute room scripts only appears to work once.

Magician Joined: 17 Apr 2005 Posts: 496

Looks bugged to me. Edit: Or more specifically, looks like a problem with scoping and having the mapper as its own object.

I can't verify the second part because now I can't get execute room scripts to work at all from the mapper, but I think I have a whole new post worth of problems.

Novice Joined: 26 Jan 2009 Posts: 32

Hmm well I seem to get some rather dubious and flaky success from using :

:Package:@Variable

So

#IF (:Achaea:@Personal.FoodLevel < 3) {#ECHO You're Hungry lets eat}

The variables are listed as undefined (red) in the editor in the room script though the above #if works for me as my package is called Achaea.mud and I have record variable Personal with a key Foodlevel.

#ECHO Level :Achaea:@Personal.FoodLevel

produces :
Level :Achaea:.FoodLevel

But interestingly :

:Achaea:_Debug {Your Food Level is @Personal.FoodLevel}

Successfully runs my _Debug alias which is a only a redirect alias to a window called debug and the text in that window is :

23:28:26 Your Food Level is 6

So partial success.

Posted: Thu Jan 29, 2009 6:01 pm

No, that is not the correct syntax. The :windowname: syntax is only intended to be used on the command line, or to send a command to another window. For example:

:Achaea:aliasname

*will* run your alias within the Achaea window. So that is correct. But you can only use this syntax at the beginning of a line with a command. It doesn't work within a #IF statement, etc.

The proper way to access a variable within a different window/module is with the syntax:

@//ModuleName/class/variable

For example:

#ECHO @//Achaea/Personal.FoodLevel

would be the correct syntax.

Magician Joined: 17 Apr 2005 Posts: 496

Zugg, I think there still is a bug with accessing variables in another PACKAGE from the map. (A simple test of creating a room script #echo @test and creating a variable @test in another package--that should be visible, and is visible from other modules in the same package as the map--fails for me.)

Variables in another module within the same package seem OK. Variables in windows aren't visible (because... variables in windows aren't published), and that's OK.

Novice Joined: 26 Jan 2009 Posts: 32

Ahh I see what's going on. There is an import complication with Zmud files. My stuff got imported as Achaea.mud

On renaming it as Achaea it all became a lot clearer. The syntax for referencing variables across packages doesn't like "."'s in the name, maybe they should be prohibited and the Zmud import ditch the .mud when creating the window?

Interestingly before making this change :Achaea: was working for the alias though the window was called Achaea.mud

Novice Joined: 26 Jan 2009 Posts: 32

But yeah then this doesn't even seem to compile, which is a guess as there is no reference to the compiler in the mapper scripts

#IF (@//Achaea/Personal.FoodLevel > 4) {#ECHO Fatty} {#ECHO Skinny}

doesn't do anything at all so I'm guessing failed a failed compile.

Ahhhhhhhhh

The cross package notation doesn't support the dot notation for record variables, leading to a failed compile which you're not notified about other than the non bold text in the script window for that room.

Now it is all clear to me.

The correct way to do this is :

#IF (%db(@//Achaea/Personal,FoodLevel) < 4) {eat} {go for a jog}

Posted: Fri Jan 30, 2009 12:22 am

Another alternative is to do this

Novice Joined: 26 Jan 2009 Posts: 32

Posted: Fri Jan 30, 2009 5:44 pm

I'll add the bug about the dot notation not working with the module/class syntax to the bug list.

gamma_ray: Yes, there is already a bug in the bug list from another post about accessing variables from within the map scripts

Novice Joined: 26 Jan 2009 Posts: 32

I'll highlight my suggestion that package naming should prohibit names containing "."'s else using dots in syntax for record variables will require additional code for you Zugg with no perceivable benefit for the user. If you agree then maybe have a look at Zmud, Cmud import routine to lose the ".mud" naming on found Zmud packages.

Posted: Fri Jan 30, 2009 11:42 pm

I'll certainly change the zMUD import so that it doesn't add the ".mud" to the window name. Otherwise, there are a lot of cases where various non-alphanumeric characters are not allowed in various names (aliaes, variables, etc) and I have yet to design a good system for dealing with that.