Zugg Software :: View topic - [2.22] all of my variables are being created as duplicates into the sytem folder

Apprentice Joined: 11 Oct 2007 Posts: 154

[2.22] all of my variables are being created as duplicates into the sytem folder

So now my system folder has TONS of variables from all my various class scripts. what is going on?

Wizard Joined: 22 Mar 2007 Posts: 2320

By system folder, do you mean under your session window? or in some class called System?

Where are the original variables at? Are they in your session package or in another package? Are the original variables or the classes they are within disabled?

Where are these variables being used--in the same package as the variables, or in separate packages? If separate packages, is the package with the original variables set to global?

Beginner Joined: 14 Jan 2004 Posts: 18

I've noticed this as well. The original variables as well as the triggers and gauges that reference them are all in my session's main package in the same class folder called vitals. They're now also duplicated in a class folder called System within the same package and my gauges no longer work.

Posted: Tue Apr 08, 2008 5:41 pm

This was actually reported before, and Zugg stated that it had something to do with the Mapper scripts. We're still trying to track it down, though... Check the sticky about Online BUG list. :P

Charneus

Posted: Wed Apr 23, 2008 7:34 pm

I'll need more details on how to reproduce this in order to fix it. It probably depends upon exactly what sort of Room Scripts you are using.

Novice Joined: 17 Dec 2007 Posts: 49

The same problem on my side.
I know when it happens.
Every time i pass through location with a roomscript operating on variables(write), all next variable changes go to system folder. Vars ar dupped and not read properly. This is huge disfunction.

Mentioned bug with Themes? Cant save theme (got always this ugly office xp theme)

Posted: Mon Apr 28, 2008 5:08 pm

Can you please show me the exact room scripts that you are using that are causing the problem?

Please create separate forum posts for different bugs. The Theme is saved in the CMUD.INI file, so as long as you have proper write access to that file, then it should be saving properly. Set the Theme to Normal to use your default Windows theme instead of the OfficeXp blue theme.

Novice Joined: 17 Dec 2007 Posts: 49

Any scripts writing to variables i think.
I use roomscript for setting waypoints.

#va waypoint 4 4 waypoints

I got mapper working, everything is ok, variables are correct, than i go into location with this script, and all goes messed. All variables/triggers/alarms which are changed/added/created since this moment are stored in System or _MapperRoom, no difference if they exist or not. What do i do to repair this? I erase all extra variables created in System, set #class 0 and everything is correct UNTIL the moment i meet another location with #va in roomscript.

It looks like we missed #class 0 after operating on variable command CALLED FROM ROOMSCRIPT.

I noticed such things WHEN USING VA FROM ROOMSCRIPT:
- Variable (without class assigned) fe. "#va location 0" is created properly in _MapperRoom and dissapears correctly when i leave the room, but all operations changing/adding variables since then are stored in _MapperRoom folder until it exists, after leaving location (_MapperRoom deleted) all new var operations go to System folder(1 folder up).

- Variable (with class assigned) fe. "#va location 0 0 waypoints" are created properly and set ok in "waypoints" folder BUT since then all new/changed variables are stored in System folder!

After using variable command from roomscript, all other go wrong (check #trigger, #temp, #alarm, are set in wrong place - System folder when no _mapperroom folder or _MapperRoom if exist even when they are called from normal script)

Novice Joined: 17 Dec 2007 Posts: 49

Checking this scripts i noticed another strange thing, can any1 check this for me ?

When you put anything into roomscript field, save this and try to delete...
You delete all letters and hit ok, instead of empty field we got word "All" :)
Impossible to delete this! You can delete, and save, and still get "All" word. Phew.

Posted: Mon Apr 28, 2008 6:59 pm

OK, I'll add this to the bug list and see if it's something I can fix without waiting for the mapper rewrite. I think you are correct that somehow it's not doing a proper "#CLASS 0" after executing the room script.

On the "All" problem, I have also added that to the bug list.

Novice Joined: 17 Dec 2007 Posts: 49

Adding #class 0 at the end of the roomscript is a quick workaround of this bug. Helps 100% in all my cases.

Posted: Tue Apr 29, 2008 6:37 pm

OK, I think I have this fixed for v2.23