Zugg Software :: View topic

Posted: Mon Nov 03, 2008 7:32 am

I had a package with 5 modules within it.

I exported this package to xml.
I then installed 2.37 to a fresh directory (clean install in other words) and opened up a new character on a brand new package.
From within the PE, File>ImportXML

All 5 of the modules are imported as modules in the root class. I cannot drag or copy them into a proper package - they seem to be acting as individual packages. They do not show on the "list of packages enabled for this module" field, and nor do they have package files in the packages (or other) folder.

The settings within them do work though, and they do remain if I restart CMUD.

I can select one within the PE and go "File>Save As" to make it a real package, and then add it to the session; but I don't want them to be packages, I want them to be modules within a package of my choosing.

Can anyone shed any light on this?

Posted: Mon Nov 03, 2008 6:14 pm

A "Package" is a *.PKG file. You cannot make a module into a package unless you store it into a separate *.PKG file.

All modules *should* be at the root level of the tree on the left side of the settings editor. So I think there might be some confused terminology here (see Terminology help topic).

So, a "module" is never going to show in the "list of packages enabled for this module" because it isn't a package. A package appears as a separate tab in the settings editor normally, and you should be able to drag/drop a module into a package tab.

Maybe you can show us a screen shot of the problem you are talking about. But it actually sounds like it's working correctly and that the modules got imported into your normal character package like they should be.

I just don't know what you mean by "I cannot drag or copy them into a proper package".

Posted: Wed Nov 05, 2008 10:58 pm

In a brand new, blank session.
Import xml file for a single package.
In the screenshot you will see it appearing as a package in the tree view, but not in the list of packages that I can enable/disable for the main session window.

You will also see that the "packages" folder in the 'Save As' window, doesn't have a package file for "AetCuringBackBone" or anything similar. (I've checked other folders in the CMUD directory as well, such as the "Aetolia" folder. Its not there.)

Maybe there is just more to the export/import process that I still have to do. Its different to how it worked the last time I did this though (months ago).

In the second image, I have selected the "AetCuringBackBone" package in the tree view field, right clicked and selected "Delete". A dialogue then asked me if I wish to delete all settings within the package. On choosing no, the package is deleted and all the settings within end up in the root class. Which you told me once before means I have corrupted settings. This might be a separate issue to the first (its just something I noticed when playing around with it all.)

Posted: Thu Nov 06, 2008 5:21 pm

It's a terminology problem...

In the screen shot that you gave, the "AetCuringBackbone" is a *module*, not a package. Click on it and you'll see that it will say "Module: AetCuringBackbone" on the right. Your XML file is just a collection of modules and/or windows. It is not a "package" itself. The only thing that is a package is a *.PKG file on your hard disk. The XML file just contains the modules/windows that were within the original package that you exported from. This allows you to import these modules/windows into any other package.

In your above case, you have imported the "AetCuringBackbone" MODULE into your Aetolia.PKG file (which is stored within the MUD subfolder for your session, and not stored in the general "Packages" directory). So now your Aetolia PACKAGE contains the Aetolia WINDOW along with the AetCuringBackbone MODULE.

So all of that is working as designed.

Posted: Thu Nov 06, 2008 11:20 pm

I do understand the difference.

I didn't understand why it imported as a module, when it was a package when I exported it.

Does this mean that to do this import/export, I need to import all of my xml files, create all of the original packages (file>new package), and then cut/paste the contents of the module into the new package I have created?

Or is there a more direct way to manage this?

Posted: Fri Nov 07, 2008 1:04 am

If you use the "Import XML" option, which I can only guess is what you used, then that adds the settings contained in the XML file you selected to the current package - that's working as intended. The proper way to remove a package from one session and add it to another is just to File->close the package in the first session, and then File->Open the .pkg file in another session. You can also manually add it to the list of packages for a session in the session's properties.

Posted: Fri Nov 07, 2008 7:13 am

Fang, I know this. However, the proper way to make sure there are no corrupted settings, is to export to xml, and import.

Having not done that for quite a few months I decided to do a fresh install when the latest version of CMUD came out, and import everything to fresh packages from xml. I thought perhaps some of the weird things that happen to me in CMUD may be because of corrupted settings. (Though it is still probably just because of WinXP-64.. but its worth a try).

Incidentally, there was nothing wrong with my original terminology or understanding of what a module or package is. I called them modules, but said that they seemed to be behaving like packages because I could not drag and drop them into actual packages. However, I have found that I can cut/paste them and that its just that modules cannot be drag-and-dropped, which is just what caused a bit of confusion.

I still think though, that its an awkward way to have to do this export/import process to ensure no corrupted settings.

1. Select each package individually and "File>Export XML(All)"
2. Install fresh copy of CMUD
3. Open, create the new session. Open the session.
4. Create each package with "File>New Package"
5. Import each xml file to each package.
6. Settings that were in the base module for each package will now be in a separate module within that package, so cut/paste them all from that to the base module, then delete the other one.

I really do wish it was possible to just export my entire session to xml, then import it and have my session recreated.

Posted: Fri Nov 07, 2008 9:15 pm