Zugg Software :: View topic - [3.03a] Items being created under (root) bug

Posted: Wed Jan 28, 2009 4:00 pm

This was originally taken from here: Aliases being copied from where they belong

I'm not sure what is causing this or how to make it happen (my guess is it's something to do with the autosave every so often), but every once in a while, when I create triggers/classes/aliases/variables, instead of being in my session package, it stores it under ROOT. Here: this happened AFTER I created a couple new variables and closed out CMUD:

As you can see, it's clearly in the root section instead of any module. The kicker is, the originals are still where they belong...

I wish I had more information to pass on, but this must be addressed regardless so that a search can be made for determining how it's being done, I suppose.

Charneus

Posted: Wed Jan 28, 2009 5:33 pm

Well, we would need to see your scripts that access/creates these variables. Without a way to make it happen, there isn't much we can do to help with this.

But yes, as long as you have variables in the root of your package, they are going to cause a problem, so you need to delete them before any of your scripts will work properly.

Posted: Wed Jan 28, 2009 7:00 pm

Well, the PathWalker variable was created manually. The alias to execute it just does #LOOPDB @PathWalker {#EXEC %val}.

But the variables are not the only thing copied. Before this instance, I had my entire script copied there. Then I closed it out and it did only the variables. Most times, it happens. I know it's not a corrupt package because I've even done it on new sessions with clean packages. When I get home tonight, I'll attempt to find any ambiguities I can to help narrow this problem down.

Charneus

Magician Joined: 18 Dec 2006 Posts: 317 Location: Denmark

I've just experienced today that several items I created manually yesterday in a folder in my main window was suddenly placed in the root after starting CMUD. Not only variables, but also a folder and some aliases and triggers too. They had been moved - not copied.

I've experienced this earlier in 2.x too.

Posted: Wed Jan 28, 2009 10:42 pm

Magician Joined: 18 Dec 2006 Posts: 317 Location: Denmark

Posted: Wed Jan 28, 2009 11:59 pm

I had a mass input in the command line. You can change it to anything you really want, but at the command line, I had about 200 instances of the following syntax:

#ADDKEY PathWalker {Childs Play} {#FORALL ~%pathexpand(es6s4ws) {#MOVE ~%i}}

Of course, the Childs Play was for the different areas in Aardwolf, so it varied, as well as the speedwalk.

Now, it didn't create it initially in the root. It created the variable (and all my other settings) under the session folder. Then I created a new folder, selected anything and everything to do with the script, right-clicked, cut, paste. Worked fine. A while later, I noticed two aliases had been actually copied to the root (it didn't happen when I first copied it), but the aliases were also still in the class folder. Later on, I saw the class folder had been copied there as well. I deleted these, closed out CMUD (red X) and restarted. Aliases were there. Deleted, closed out, restarted, these variables. I can send you my package and maybe you can figure it out. One thing that might be the problem is onLoad events that I use. When I get home, I'll post all onloads to see if they might be causing the problem.

Charneus