Zugg Software :: View topic

Wanderer Joined: 24 Jun 2008 Posts: 68 Location: Texas

Process:

Step 1: Open CMud and 'x' out of the sessions listing to the default window.
Step 2: Open the package editor and create a class folder
Step 3: Export the class folder to XML
Step 4: Import the XML

The importing creates a new window module for the imported data. This does -not- happen when importing aliases/triggers/etc. This happens whether or not there are any actual settings in the class folder (Aliases, triggers, etc)

Posted: Tue Jul 01, 2008 10:09 pm

I could not reproduce this.

In Step 3 I exported the class folder by right-clicking on the class in the tree and select "Export selection to XML". In step 4 I didn't get any duplicate class.

You might post the XML that you exported within [CODE] tags here in the forum so I can look at exactly what is being exported.

Wanderer Joined: 24 Jun 2008 Posts: 68 Location: Texas

Just following the above method on an untitled window with creating a few triggers inside of a class folder, I ended up with this:

Wanderer Joined: 24 Jun 2008 Posts: 68 Location: Texas

I just had my gal at home try this on her comp and she has the same issues with it, so it is reproducable on at least 1 other computer. I know it should be negligible that I'm running CMud Pro.

Posted: Tue Jul 01, 2008 11:24 pm

In your original instructions you said you were just exporting the CLASS folder. But your XML shows that you are exporting the entire package and window. That's why I asked *exactly* HOW you were exporting the class. If you right-click on the class folder and select "Export selection" then you don't get this problem because it only outputs the class and not the whole window. Or maybe you are right-clicking on the window name and calling this a "class" by mistake.

The reason you get a duplicate when you export the entire window because you are exporting the "Untitled" window. The "Untitled" window is recreated each time you run CMUD and is assigned a new unique identifier (thats the UID field show in your XML export). When the UID field doesn't match anything in your settings, then a new window/module is created. Since CMUD assigns a new UID to the Untitled window each time you run it, then this is going to happen.

Shouldn't happen within a normal session however. So try this in one of your real sessions. When you export the window you'll see the UID for that window in the XML output. When you import that file, CMUD will see the matching window UID and won't create any new window.

Wanderer Joined: 24 Jun 2008 Posts: 68 Location: Texas

Wanderer Joined: 24 Jun 2008 Posts: 68 Location: Texas

Here you go:

http://www.mediafire.com/?jtkngonnnjm

Watch that (Preferably in as big of a window as you can) to see my process. I know it has an ugly banner plastered across it, but you can still see what needs to be seen. (And I don't feel like paying 40 - 300 bucks for screen cap software right now.)

Here's another one I threw together real quick to show what happens when you try to save out a class folder stored inside another class folder:

http://www.mediafire.com/?ngoukgxd5nz

Wanderer Joined: 24 Jun 2008 Posts: 68 Location: Texas

I've just tried my process on a 3rd computer now. Both of the same problems exist on it as well. It'd help if some other people running 2.29 would give it a try as well.

Posted: Wed Jul 02, 2008 8:10 pm

Yes, in your second message you mentioned that you were right-clicking, but it wasn't perfectly clear what you were right-clicking on. From what you posted it looked like you were right-clicking the window instead of the class, and we have had enough terminology confusion that this wasn't clear.

But when I looked at the actual file being exported by right-clicking the Class and selecting Export Selection I was able to confirm the problem. There are two problems here that I have fixed for v2.30. The first problem was that exporting a class was actually exporting the entire window/module instead of just the class.

The other bug was that when importing it was sometimes getting confused as to whether to what module and class to import into. If you clicked on a class and then right-clicked a window/module and selected import, then it was importing the file into the class that was previously clicked on, causing some nested classes to be created. I think this bug was responsible for a lot of problems when importing XML. Hopefully 2.30 fixes all of these problems correctly. Thanks for your patience with this.

Wanderer Joined: 24 Jun 2008 Posts: 68 Location: Texas

No problem. I'm just glad it's fixed. Like I said, it wasn't something I was too worried about personally, but I'm sure alot of people would like to be able to save out their class folders.

Personally I was just trying to prove that I wasn't a complete idiot :P