ALESIS K2661 - Manual (Page 40)

5-6
Editing Conventions
Deleting Objects
Deleting Objects
Within most editors, there are soft buttons for deleting objects. When you want to delete an
object, press the Delete soft button, and the K2661 will ask you if you want to delete the object.
(At this point in the dialog, you can select another object with any of the data entry methods.)
Press OK if you want to delete it, or press Cancel if you don’t. Although it seems that you can
delete ROM objects, you can’t actually do it. The K2661 will behave as if it’s deleting the ROM
object, but it will still be there the next time you select it. (What actually happens is that the
ROM object is copied to RAM as soon as you press Edit, and when you “delete” the ROM object,
you’re actually deleting the RAM copy. The original ROM object remains in memory.)
RAM objects, on the other hand, are gone when you delete them! If you’ve “replaced” a ROM
object by saving a RAM object with the same ID, the ROM object is invisible, but still there.
Deleting the RAM object stored at the same ID will restore the ROM object.
You’ll often delete objects to gain RAM space, or to organize the memory banks before saving
objects to disk. To delete multiple objects, use the Delete Objects utility available in Master
mode. It’s described on page 11-18.
Dependent Objects
A dependent object is an object that’s linked in memory with at least one other object. For
example, if you create a setup that uses a program that you also created, that program is a
dependent object of the setup.
When you start to delete an object that has dependent objects, the Delete dialog gives you a
choice: Delete dependent objects? If you press Yes, the K2661 will delete the object and all its
dependent objects when you execute the Delete function. In our example, if you were deleting
the setup you created, and you chose to delete dependent objects, the dependent program
would get deleted as well. If you press No at the Delete dependent objects? prompt, the K2661
deletes only the object, but keeps the dependent objects. In our example, the setup would get
deleted, but the dependent program would remain.
When deleting objects and their dependents, the K2661 deletes only those dependent objects
that aren’t dependent on other objects that you’re not deleting. For example, suppose you have
two setups that contain the same program. If you delete one of the setups, and delete dependent
objects with it, the setup gets deleted, but the program that’s contained in the other setup
remains in memory.