Computer graphics processing and selective visual display system – Display driving control circuitry – Controlling the condition of display elements
Reexamination Certificate
2000-11-29
2004-02-03
Bella, Matthew C. (Department: 2676)
Computer graphics processing and selective visual display system
Display driving control circuitry
Controlling the condition of display elements
C345S619000, C345S620000, C345S624000, C345S630000, C345S215000, C345S215000
Reexamination Certificate
active
06686930
ABSTRACT:
BACKGROUND OF THE INVENTION
1. Field of the Invention
The invention relates to the art of document processing. More specifically, the invention relates to the art of copying a first image or portion of a first image and pasting the copy into a second image or portion of a second image where the source of the first image is a TWAIN data source. For example, the invention finds use where the first image data source is a TWAIN compliant scanner or image database. While the invention is described in relation to a TWAIN compliant scanner, the invention may be used in association with any TWAIN complaint data source.
2. Description of Related Art
TWAIN is the name of a protocol or communications standard that has been developed in order to help image processing devices communicate with each other. For example, TWAIN is used to help computers communicate with scanners and digital cameras. Additionally, TWAIN is used in some xerographic environments. Complete details of the TWAIN standard are available from The TWAIN Working Group, 13090 Hwy. 9, Suite 3, Boulder Creek, Calif. 95006.
Understanding of aspects of the invention may be aided by a review of some aspects of the TWAIN standard.
TWAIN defines a standard software protocol and application-programming interface (API) for communication between software applications and image acquisition devices (the source of the data). Three main elements in TWAIN are: 1) an application, such as, for example, a document scan and make ready tool, a desktop publishing application, a word processing application and document or image processors; 2) source software, which is software that controls an image acquisition device and is written by the image acquisition device developer to comply with TWAIN specifications; and 3) source manager software, which is software that manages interactions between the application and the Source.
FIG. 1
shows exemplary components of TWAIN compliant image processing systems
110
. An application
114
sends commands to a source
118
by sending commands, in the form of TWAIN operation triplets, to the Source Manager
122
. The Source Manager sends the triplets on to the source software (“Source”)
126
.
An operation is an action that the application
114
or Source Manager
122
invokes. A triplet is a command that uniquely, and without ambiguity, specifies a particular action. No operation is specified by more than a single triplet. Three parameters make up a triplet. The three parameters are Data Group, Data Argument Type, and Message ID. Each parameter conveys specific information.
Operations are divided into large categories by the Data Group identifier (Data Group (DG_xxxx)). There are only three data groups currently defined in TWAIN. A Control Data Group (DG_CONTROL) includes operations that involve control of a TWAIN session. An example where DG_CONTROL is used as the Data Group identifier is the operation to open the Source Manager. An IMAGE Data Group (DG_IMAGE) includes operations that work with image data. An example where DG_IMAGE is used as a Data Group is an operation that requests the transfer of image data. An AUDIO Data Group (DG_AUDIO) includes operations that work with audio data from, for example, some digital cameras. An example where DG_AUDIO is used as a Data Group is an operation that requests the transfer of audio data.
One of TWAIN's benefits is it allows applications to easily interact with a variety of acquisition devices. Devices can provide image or audio data. For instance, some devices have automatic document feeders. Furthermore, some devices are not limited to one image but can transfer multiple images. Some devices support color images. Some devices offer a variety of halftone patterns. Some devices support a range of resolutions while others may offer different choices. For example, many devices operating in a xerographic environment have automatic document feeders. Many xerographic devices can transfer multiple images between a scanner and an application. Some devices operating in xerographic environments operate in color and offer a variety of halftone patterns. Some devices allow the recording of audio data associated with an image.
It is important for an application to be aware of a Source's capabilities. For example, the capabilities of a source may influence the way an application chooses to scale or resize an image. Therefore TWAIN allows an application to perform capability negotiation with a source. The application generally follows this process: 1. Determine if the selected Source supports a particular capability. 2. Inquire about the Current Value for this capability. Also, inquire about the capability's Default Value and a set of available values that are supported by the Source for that capability. 3. Request that the Source set the Current Value to the application's desired value. The Current Value will be displayed as the current selection in the Source's user interface (“UI”). 4. Limit, if needed, the Source's available values to a subset of what would normally be offered. For instance, if the application wants only black and white data, it can restrict the Source to transmit only black and white data. 5. Verify that the new values have been accepted by the Source.
There are three modes that can be used to transfer data from the Source to the application. The three modes are native, disk file, and buffered memory.
Every Source must support Native transfer mode. It is the default mode and is the easiest for an application to implement. However, it is restrictive (i.e. limited to Device-Independent Bitmap (DIB) or PICT formats and limited by available memory). The format of the data is platform-specific. For example Windows applications use DIB. The Source allocates a single block of memory and writes the image data into the block. The Source passes a pointer to the application indicating the memory location of the block. The application is responsible for freeing the memory after the transfer.
A Source is not required to support Disk File transfer mode but it is recommended. In Disk File transfer mode, the application creates the file to be used in the transfer and ensures that it is accessible by the Source for reading and writing. A capability exists that allows the application to determine which file formats the Source supports. The application can then specify the file format and file name to be used in the transfer. The Disk File mode is ideal when transferring large images that might encounter memory limitations with Native mode. Disk File mode is simpler to implement than the Buffered Memory mode. However, Disk File mode is a bit slower than Buffered Memory mode and the application must be able to manage the file after creation.
Every Source must support Buffered Memory transfer mode. The transfer occurs through memory using one or more buffers. Memory for the buffers is allocated and deallocated by the application. The data is transferred as an unformatted bitmap. The application must use information available during the transfer to learn about each individual buffer and be able to correctly interpret the bitmap.
If using the Native or Disk File transfer modes, the transfer is completed in one action. With the Buffered Memory mode, the application may need to loop repeatedly to obtain more than one buffer of data. Buffered Memory transfer offers the greatest flexibility, both in data capture and control. However, it is the least simple to implement.
Referring to
FIG. 2
, it is logical that a process for communicating between image processing devices, such as the TWAIN protocol, must occur in a particular sequence. For example, the application cannot successfully request the transfer of data from a Source before the Source Manager is loaded and prepared to communicate the request. To ensure the sequence is executed correctly, the TWAIN protocol defines seven states
210
that exist in TWAIN sessions. A session is, for example, a period while an application is connected to a particular source via the Source Manager. The period w
Feygin Boris M.
Powers John G.
Bella Matthew C.
Fay Sharpe Fagan Minnich & McKee LLP
SaJous Wesner
Xerox Corporation
LandOfFree
Technique for accomplishing copy and paste and scan to fit... does not yet have a rating. At this time, there are no reviews or comments for this patent.
If you have personal experience with Technique for accomplishing copy and paste and scan to fit..., we encourage you to share that experience with our LandOfFree.com community. Your opinion is very important and Technique for accomplishing copy and paste and scan to fit... will most certainly appreciate the feedback.
Profile ID: LFUS-PAI-O-3350701