Zugg Software :: Copy an existing package

Making a copy of a package

To create a copy of an existing package, you can either copy the *.PKG file to a new filename using the normal Windows File Explorer, or you can go into the Package Editor in CMUD, load an existing package, and then use the "Save Package As" command in the File menu.

The "Save Package As" command will save the package to a new *.PKG filename. But nothing else will change. You'll still see the same original package name, module name, and scripts.

Example

In our example of editing the "English Keypad" package, we select the "English Keypad" package tab and then use File/Save Package As. Let's enter a filename of "mykeypad.pkg". It doesn't look like anything obvious has happened, but if we select the Edit/Package Properties menu, we will see our new filename displayed at the bottom of the window.

While viewing the Package Properties, edit the name of the Package to be "My Keypad Package" and click the Save Changes button. The Package Properties will close and you will see that the tab for this package has changed to "My Keypad Package".

But notice the contents of the package in the tree view on the left. It still shows "English Keypad". What's the deal with this?

This illustrates an important point: A Package is a FILE, and has both a FileName (the name of the file you see on disk, like mykeypad.pkg), and it has a Name (which you view in the Package Properties). Each package file contains one or more Modules or Windows. In this example, there is a published Module called "English Keypad". Changing the name of the Package does not change the name of the Modules or Windows stored inside of the Package.

Some people get confused by this fact because they think the first module displayed in the tree-view on the left is the same as the package itself. It isn't. A package can contain many modules and windows.

Let's go back to our example. Click on the "English Keypad" MODULE in the tree-view on the left side of the screen. Edit the name in the field on the right to be "My Keypad Module". Then click Save Changes.

Finally, find the KEY5 macro within the Keypad class folder on the left and change the script command to be "scan" instead of "look".

Now we have a new package, called "My Keypad Package", stored in the file mykeypad.pkg. It contains a single Module called "My Keypad Module". This Module contains two class folders: Keypad and KeypadDiag. In the Keypad class folder, we have changed the KEY5 macro to send "scan" instead of "look".