Zugg Software :: View topic

Wizard Joined: 26 Mar 2008 Posts: 1547

I've slowly begun the migration over to a two package system. A "general" package for all of my DSL sessions, and a package for each character in their individual sessions.

I'm sure I'm going to have several complications, but right off the bat I have two important ones.

1) Variables across packages. It was my understanding that I could keep variables in my character session to be referenced by the General package. This is important to me because various characters may store different things in their variables and I would rather keep such variables in a session as opposed to the alternative. Some variables may be in the General package but plenty of them need to stay with the characters. However, upon moving my triggers over to the General package, all of the variables are now highlighted red, as if they don't exist.

2) Problem with my capture window. Now that all of my tell triggers, and spell fade triggers are in the General package they've all had to be disabled because, for no explicable reason, they create an infinite loop. I got rid of the triggers in the character package, nothing else has changed and yet suddenly they're now broken... Sad

SubAdmin Joined: 18 Nov 2001 Posts: 5182

Issue 1, the red coloring. This is very normal. The Package Editor can't determine any context for the script, all it can look at is the defined package scope. When the context of the window is applied to running that trigger then the scope expands and those variables become valid.

Issue 2, infinite loop with capture triggers. If your Tells window is defined outside of the General package, then disable to use of the General package for the Tells window. Otherwise set the module containing the triggers in the General package to External.

Wizard Joined: 26 Mar 2008 Posts: 1547

So... I moved the little tells thing (with all of its property information) to the general package, still having the same problem. Should I delete it and the triggers and try starting from scratch?

SubAdmin Joined: 18 Nov 2001 Posts: 5182

@#%,@#$% !#@$% #%^&. I feel better now.

Your Tells window should be part of your General package, as you want all your sessions to use it. You did this move even though I didn't suggest it. Good thinking.

Your triggers should be in a module in your General package, lets call that module X. The setting of module X needs to be External. That particular setting makes everything in the module unavailable to other modules in the same package. This will hide it from the Tells window.

Wizard Joined: 26 Mar 2008 Posts: 1547

Alright, well I set it to be external... but I'm still getting the same error. I reentered the triggers after setting the General Package to external but CMUD "crashed" it an error when I tried to capture a tell. I chose continue application and had to disable the trigger. I went back to edit the trigger and the background of the part where "Tells" was was black, which was really odd. Either way, it's still not working.

Edit:
grrr, I'm not going to touch it for now. It's way too frustrating.

SubAdmin Joined: 18 Nov 2001 Posts: 5182

Just post a stack of screen shots of how you have it, and I will either find the problem or request more.

Wizard Joined: 26 Mar 2008 Posts: 1547

Okay... this is odd.

So I closed the program, went out somewhere, came back and opened the program. When I logged onto the character I was experimenting with, I found that all of my triggers in that folder I moved were gone. They weren't on the character's package OR the general package. So I readded the tell triggers so I could take some screenshots, and they work just fine. Only problem is that even though the triggers are in the general package, it is still putting the tell window module above the character package (if I click on the tab that contains the character package I can select all of the stuff on my character or the tell module). Neutral

Wizard Joined: 22 Mar 2007 Posts: 2320

Are you having triggers CREATE the tells window? If so, it is normal for it to be created in your session package. If you create or move the tells window into the General package, it will stay there.

Wizard Joined: 26 Mar 2008 Posts: 1547

I used to only have the session packages. The triggers created (through #CAP Tells) a window. It worked fine.

I moved those triggers and window to the "General Package" which is where they all went haywire and disabled. I deleted them all and replaced them. Same problem. I deleted the window and the triggers, replaced them, and it went haywire. Tried a new window, went haywire. I gave up and did some other things. Came back, Vig asked for Screenshots, I opened it up to do just that only to found that now ALL of my triggers were gone, not just the ones involved with the window. They weren't in either General Packages or the Session Package. I put the triggers for the window back in, in the General Package, and it all worked! Great. Problem: The tells window module is in the Session Package tab.

Wizard Joined: 22 Mar 2007 Posts: 2320

Good, so move the Tells window to the General package.