Copy, Cut, and Paste Operations

UIKit Facilities for Copy-Paste Operations

Several classes and an informal protocol of the UIKit framework give you the methods and mechanisms you need to implement copy, cut, and paste operations in your application:

• The UIPasteboard class provides pasteboards: protected areas for sharing data within an application or between applications. The class offers methods for writing and reading items of data to and from a pasteboard.

• The UIMenuController class displays an edit menu above or below the selection to be copied, cut, or pasted into. The default commands of the edit menu are (potentially) Copy, Cut, Paste, Select, and Select All. You can also add custom menu items to the edit menu (see “Adding Custom Items to the Edit Menu”).

• The UIResponder class declares the method canPerformAction:withSender:. Responder classes can implement this method to show and remove commands of the edit menu based on the current context.

• The UIResponderStandardEditActions informal protocol declares the interface for handling copy, cut, paste, select, and select-all commands. When users tap one of the commands in the edit menu, the corresponding UIResponderStandardEditActions method is invoked.

Pasteboard Concepts

A pasteboard is a standardized mechanism for exchanging data within applications or between applications. The most familiar use for pasteboards is handling copy, cut, and paste operations:

• When a user selects data in an application and chooses the Copy (or Cut) menu command, the selected data is placed onto a pasteboard.

• When the user chooses the Paste menu command (either in the same or a different application), the data on a pasteboard is copied to the current application from the pasteboard.

In iOS, a pasteboard is also used to support Find operations. Additionally, you may use pasteboards to transfer data between applications using custom URL schemes instead of copy, cut, and paste commands; see “Communicating with Other Applications” in iOS App Programming Guide for information about this technique.

Regardless of the operation, the basic tasks you perform with a pasteboard object are to write data to a pasteboard and to read data from a pasteboard. Although these tasks are conceptually simple, they mask a number of important details. The main complexity is that there may be a number of ways to represent data, and this complexity leads to considerations of efficiency. These and other issues are discussed in the following sections.

Representations and UTIs

Pasteboard operations are often carried out between two different applications. Neither application is required to know about the other, including the kinds of data it can handle. To maximize the potential for sharing, a pasteboard can hold multiple representations of the same pasteboard item. For example, a rich text editor might provide HTML, PDF, and plain-text representations of the copied data. An item on a pasteboard includes all representations of that data item that the application can provide.

Each representation of a pasteboard item is typically identified by a Unique Type Identifier (UTI). (A UTI is simply a string that uniquely identifies a particular data type.) The UTI provides a common means to identify data types. If you have a custom data type you wish to support, you must create a unique identifier for it. For this, you could use reverse-DNS notation for your representation-type string to ensure uniqueness; for example, a custom representation type could be com.myCompany.myApp.myType. For more information on UTIs, see Uniform Type Identifiers Overview.

For example, suppose an application supported selection of rich text and images. It may want to place on a pasteboard both rich text and Unicode versions of a text selection and different representations of an image selection. Each representation of each item is stored with its own data, as shown in Figure 5-1.

In general, to maximize the potential for sharing, pasteboard items should include as many different representations as possible.

A pasteboard reader must find the data type that best suits its capabilities (if any). Typically, this means selecting the richest type available. For example, a text editor might provide HTML (rich text) and plain-text representations of copied text data. An application that supports rich text should retrieve the HTML representation and an application that only supports plain text should retrieve the plain-text version.

First Steps: Identify the Selection and Display the Edit Menu

If you are going to copy, cut, or paste something, you first must select it. (A paste operation often operates on an empty selection such a caret, indicating a position within a collection of items.) After selecting an item—and visually indicating the selection—you should display the edit menu. The edit menu is a system menu that can potentially have the following commands in it: Copy, Cut, Paste, Select, and Select All. The edit menu points at the selection. When the user taps a menu item, the appropriate UIResponderStandardEditActions method implementation (such as cut: or paste:) is invoked.

For more about selections and to learn how to display and manage the edit menu, see “Managing the Selection and the Edit Menu.”

Copying and Cutting the Selection

When users tap the Copy or Cut command of the edit menu, the system invokes the copy: or cut: method (respectively) of the responder object that implements it. Usually the first responder—your custom view—implements these methods, but if the first responder doesn’t implement them, the message travels up the responder chain in the usual fashion. Note that the UIResponderStandardEditActions informal protocol declares these methods.

In response to a copy: or cut: message, you write the object or data represented by the selection to the pasteboard in as many different representations as you can. This operation involves the following steps (which assume a single pasteboard item):

1. From the selection, identify or obtain the object or the binary data corresponding to the object.

   Binary data must be encapsulated in an NSData object. If you’re going to write another type of object to the pasteboard, it must be a property-list object—that is, an object of one of the following classes: NSString, NSArray, NSDictionary, NSDate, NSNumber, or NSURL. (For more on property-list objects, see Property List Programming Guide.)

2. If possible, generate one or more other representations of the object or data.

   For example, if in the previous step you created a UIImage object representing a selected image, you could use the UIImageJPEGRepresentation and UIImagePNGRepresentation functions to convert the image to a different representation.

3. Obtain a pasteboard object.

   In many cases, this is the general pasteboard, which you can get through the generalPasteboard class method.

4. Assign a suitable UTI for each representation of data written to the pasteboard item.

   See “Pasteboard Concepts” for a discussion of this subject.

5. Write the data to the first pasteboard item for each representation type:

   • To write a data object, send a setData:forPasteboardType: message to the pasteboard object.

   • To write a property-list object, send a setValue:forPasteboardType: message to the pasteboard object.

6. If the command is Cut (cut: method), remove the object represented by the selection from the application’s data model and update your view.

Listing 5-1 shows implementations of the copy: and cut: methods. The cut: method invokes the copy: method and then removes the selected object from the view and the data model. Note that the copy: method archives a custom object to obtain an NSData object that it can pass to the pasteboard in setData:forPasteboardType:.

Listing 5-1  Copying and cutting operations

- (void)copy:(id)sender {

    UIPasteboard *gpBoard = [UIPasteboard generalPasteboard];

    ColorTile *theTile = [self colorTileForOrigin:currentSelection];

    if (theTile) {

        NSData *tileData = [NSKeyedArchiver archivedDataWithRootObject:theTile];

        if (tileData)

            [gpBoard setData:tileData forPasteboardType:ColorTileUTI];

    }

}

- (void)cut:(id)sender {

    [self copy:sender];

    ColorTile *theTile = [self colorTileForOrigin:currentSelection];

    if (theTile) {

        CGPoint tilePoint = theTile.tileOrigin;

        [tiles removeObject:theTile];

        CGRect tileRect = [self rectFromOrigin:tilePoint inset:TILE_INSET];

        [self setNeedsDisplayInRect:tileRect];

     }

}

Pasting the Selection

When users tap the Paste command of the edit menu, the system invokes the paste: method of the responder object that implements it. Usually the first responder—your custom view—implements this method, but if the first responder doesn’t implement it, the message travel up the responder in the usual fashion. The paste: method is declared by the UIResponderStandardEditActions informal protocol.

In response to a paste: message, you read an object from the pasteboard in a representation that your application supports. Then you add the pasted object to the application’s data model and display the new object in the view in the user-indicated location. This operation involves the following steps (which assume a single pasteboard item):

1. Obtain a pasteboard object.

   In many cases, this is the general pasteboard, which you can get through the generalPasteboard class method.

2. Verify that the first pasteboard item contains data in a representation that your application can handle by calling the containsPasteboardTypes: method or the pasteboardTypes method and then examining the returned array of types.

   Note that you should have already performed this step in your implementation of canPerformAction:withSender:.

3. If the first item of the pasteboard contains data that the application can handle, call one of the following methods to read it:

   • dataForPasteboardType: if the data to be read is encapsulated in an NSData object.

   • valueForPasteboardType: if the data to be read is encapsulated in a property-list object (see “Copying and Cutting the Selection”).

4. Add the object to the application’s data model.

5. Display a representation of the object in the user interface at the location specified by the user.

Listing 5-2 is an example of an implementation of the paste: method. It does the reverse of the combined cut: and copy: methods. The custom view first sees whether the general pasteboard holds its custom representation of data; if it does, it then reads the data from the pasteboard, adds it to the application’s data model, and marks part of itself—the current selection—for redrawing.

Listing 5-2  Pasting data to a selection

- (void)paste:(id)sender {

    UIPasteboard *gpBoard = [UIPasteboard generalPasteboard];

    NSArray *pbType = [NSArray arrayWithObject:ColorTileUTI];

    ColorTile *theTile = [self colorTileForOrigin:currentSelection];

    if (theTile == nil && [gpBoard containsPasteboardTypes:pbType]) {

        NSData *tileData = [gpBoard dataForPasteboardType:ColorTileUTI];

        ColorTile *theTile = (ColorTile *)[NSKeyedUnarchiver unarchiveObjectWithData:tileData];

        if (theTile) {

            theTile.tileOrigin = self.currentSelection;

            [tiles addObject:theTile];

            CGRect tileRect = [self rectFromOrigin:currentSelection inset:TILE_INSET];

            [self setNeedsDisplayInRect:tileRect];

        }

    }

}

Ending an Operation

When your implementation of the cut:, copy: or paste: command returns, the edit menu is automatically hidden. You can programmatically keep it visible if you want. For more information, see “Dismissing the Edit Menu”