KR100923457B1 - How to display a multi mouse pointer - Google Patents

Abstract

The present invention relates to a multi-mouse pointer display method, and more particularly, to a method of operating two or more mice by generating and displaying a pointer of one or more added mice using a logic driver.

In accordance with another aspect of the present invention, there is provided a method of displaying a multi-mouse pointer, loading a memory of a physical driver of a computer system, registering an added mouse device using the loaded physical driver's memory, and generating the mouse device. Setting an event to be executed, executing a thread to the mouse device, driving an application to which a multi-mouse is applied, and detecting an event occurring on the driven application, wherein the detected event is the set event. And an event detection step and dynamically calculating a total window size and an application window size to which the multi-mouse is applied based on the detected event, and outputting a mouse cursor as an image to display a mouse pointer. It provides a multi-pointer display method.

Multi Mouse, Multi Pointer

Description

How to display a multi-mouse pointer {METHOD FOR DISPLAYING MULTI MOUSE POINTER}

1 is a view for explaining the operation of the filter driver according to an embodiment of the present invention;

2 is a flowchart illustrating a method of displaying a multi-mouse pointer according to an embodiment of the present invention;

3 is a flowchart illustrating a detailed process of a registration step of a mouse device in a method of displaying a multi-mouse pointer according to an embodiment of the present invention;

4 is a diagram illustrating a relationship between an internal name and a symbolic link name in an object manager namespace in a method of displaying a multi-mouse pointer according to an embodiment of the present invention;

5 illustrates an example of a computer system architecture that may be used to practice the present invention.

The present invention relates to a multi-mouse pointer display method, and more particularly, to a method of operating two or more mice by generating and displaying one or more additional mouse pointers using a logic driver.

With the spread of computers, computers have become a necessity for life. In order to use an operating system (OS) to operate and operate such a computer, a mouse is used as an essential input device together with a keyboard.

The mouse currently used is mainly a ball mouse or an optical mouse, and the spread of the optical mouse is progressing actively in recent years. The mouse is used by detecting the movement of the mouse through a ball or light sensor mounted on the mouse and presenting it through a pointer generated on the monitor. The pointer of such a mouse is implemented by continuously displaying the mouse pointer on the monitor for each movement in response to the movement on the horizontal and vertical axes of the mouse.

In general, only one mouse is used as this essential input device. In other words, even if two or more mice are connected to the computer, the operating system (OS) creates only one mouse pointer on the monitor and implements the movement of two or more mice connected to the computer as one pointer. . Therefore, operating two pointers simultaneously using two mice is not implemented in the current OS.

However, it is necessary to use two or more independent pointers for various applications of the computer, for example, in surgery simulation in medicine, sports games or guided early childhood education.

SUMMARY OF THE INVENTION The present invention has been made in view of the above-described problems, and an object thereof is to provide a method for generating and manipulating a pointer for each mouse on a monitor in order to use two or more mice simultaneously.

In order to achieve the above object, an embodiment of the present invention provides a multi-mouse pointer display method, comprising: loading a memory of a physical driver of a computer system, adding the memory using the loaded physical driver; Registering a mouse device, setting an event generated by the mouse device, executing a thread for the mouse device, driving an application to which a multi-mouse is applied, and running on the driven application. Detect the generated event, wherein the detected event is the set event and image the mouse cursor by dynamically calculating the total window size and the application window size to which the multi-mouse is applied based on the detected event. Output to It provides a multi-mouse pointer display method comprising the step of displaying a mouse pointer.

Further, in one embodiment of the present invention, the event detection may be performed by hooking the event when an operating system (OS) of the computer system detects an event for the registered mouse device.

Further, in an embodiment of the present invention, registering the mouse device may include generating a filter device object for the mouse device and placing the generated filter device object on the top of a device stack and obtaining a pointer of the mouse device object. It may include a step.

In addition, an embodiment of the present invention may further include generating a symbolic link connecting a registered mouse device and a user visible name to the mouse device.

In addition, the set event may include left mouse button down, left mouse button up, right mouse button down, right mouse button up, vertical mouse movement, horizontal mouse movement, mouse wheel down, mouse wheel up, mouse wheel scroll down, and the like. It can include one or more of mouse wheel scroll ups.

DETAILED DESCRIPTION Hereinafter, exemplary embodiments of the present invention will be described in detail with reference to the accompanying drawings so that those skilled in the art may easily implement the present invention. As those skilled in the art would realize, the described embodiments may be modified in various different ways, all without departing from the spirit or scope of the present invention. In the drawings, parts irrelevant to the description are omitted in order to clearly describe the present invention, and like reference numerals designate like parts throughout the specification.

Throughout the specification, when a part is "connected" to another part, this includes not only "directly connected" but also "electrically connected" with another element in between. . In addition, when a part is said to "include" a certain component, this means that it may further include other components, except to exclude other components unless otherwise stated.

1 is a diagram illustrating an operation of a filter driver according to an exemplary embodiment of the present invention.

Filter Driver is a kind of intermediate driver that supplements the functions provided by existing drivers by intercepting I / O requests sent to already commercially available drivers such as file system drivers or disk drivers. Or provide new opportunities to add new features. For example, if you need to monitor data sent to a USB port, you need to create a USB filter driver because the operating system provides a USB driver. Each port installed on a personal computer, or the tools used to monitor specific tasks, are mostly built using filter drivers.

Another example of using a filter driver is a file system filter driver. File system drivers (FAT, NTFS, CDFS, LAN Manager redirector, etc.) do not provide encryption or decryption of files when they are stored or read from disk. Therefore, you can use file system filter driver to add encryption or decryption function to file or to perform functions such as virus scan.

The filter driver is divided into upper filter driver and lower filter driver depending on where the I / O request to the driver is intercepted in the driver layer.

The upper filter driver is a driver that intercepts I / O requests and does the necessary work before the user process's request reaches the file system driver. The lower filter driver is located under the file system driver. When an I / O request processed by a file system driver is passed to a driver that manages secondary storage devices, such as a hard disk, it intercepts and performs the necessary work.

The filter driver works by modifying the behavior in only a few aspects of the current driver without rewriting the entire driver. The SCSI filter driver works this way. The filter driver hides the limitations of lower-level device drivers.

For example, if the lower driver has a limitation on the size of the data transfer, the filter could break up large data transfers into smaller sizes and pass them down to the lower level. Filter drivers can add new features, such as compression or encryption, to a device without modification of the underlying device driver or the program using the device. Filter drivers can add or remove costly operations (such as performance monitoring) that the driver does not always perform.

The main difference between filter drivers and other layer drivers lies in the device object they create. Layer drivers export device objects with their unique names, whereas device drivers in filter drivers do not have names. The filter drivers work by attaching one of their unnamed device objects to the device object created by the lower level driver.

FLTDRIVER has a filter device object attached to FD0, which is one of the device objects of FD0DRIVER. All IRPs sent to FD0 are automatically routed to the dispatch routine in FLTDRIVER. This process is described below.

Create an invisible device object in the filter device's AddDevice routine and attach it to a named device object owned by its subdriver. Clients accessing the lower level driver open the connection to FD0. This is typically done by obtaining a handle via the Win32 CreateFile method, and kernel-mode clients can do this using the IoGetDeviceObjectPointer function. Regardless, the I / O manager actually establishes a connection between the client object and the device object of the filter driver.

When a client sends an I / O request to FD0, the I / O manager sends the request instead to the unnamed device object of the filter driver. The I / O Manager then uses the MajorFunction table of the filter driver object to select the appropriate dispatch routine. Dispatch routines in the filter driver either directly process the IRP or complete it immediately. Or send IRP down to FD0 via IoCallDriver. If the filter driver wants to regain control after completion of the IRP processing in the lower level driver, the filter assigns an I / O completion routine to the IRP.

Filters may be formed hierarchically on top of other filters. Putting a new filter back on a device object that is already filtered will result in the new filter being raised on top of the already formed hierarchy. In essence, a single device object can form any number of filters in a hierarchy.

The filter driver must export a routine named DriverEntry. This routine initializes the driver's data structure and prepares the environment for all other driver components. The process in the DriverEntry routine is as follows:

(1) DriverEntry acquires the hardware to be controlled by the driver. The hardware is assigned to be designated as under the control of this driver.

(2) The driver object is initialized by specifying the starting point of other functions in the driver. This specification is handled by storing a pointer to the functions in the driver object.

(3) If the driver manages a multi-unit or multi-function controller, use IoCreateController to create a controller object and initialize the controller extension.

(4) Use IoCreateDevice to create a device object for each physical or logical device under the driver's control and initialize the device extension.

(5) Make the created device object visible to the Win32 subsystem by calling IoCreateSymbolicLink.

(6) Connect the device to the interrupt object. If the ISR requires a DPC object, it is created and initialized in this process.

(7) Repeat steps (4) to (6) for each physical or logical device under the control of this driver.

(8) If successful, DriverEntry returns STATUS_SUCCESS to the I / O Manager.

In this case, the processes (1) and (3) to (6) are not performed by the DriverEntry routine of the WDM driver, but are processed by the AddDevice routine.

If DriverEntry fails in the initialization phase for some reason, it must release the system resources it has allocated and return the code for the correct NTSTATUS failure situation to the I / O manager.

As with all kernel-mode drivers, the filter driver has a main entry point called DriverEntry. Also, like any other WDM driver, it must have AddDevice, RemoveDevice, and Unload routines.

The AddDevice routine adds a device, and the initialization sequence that the filter driver must perform for the PnP request to add a device in the AddDevice routine is straightforward.

The filter calls the IoCreateDevice function to create a filter device object for the target device. The filter device object has no internal name and no symbolic link name.

Call the popular IoAttachDeviceToDeviceStack function to build itself on top of the low-level driver and get a pointer to the target device object.

Store the address of the target device object in the device extension of the filter device object. Other routines in the filter driver will use this pointer to call the target driver.

Next, copy the DeviceType and Characteristics fields from AddDevice to the filter device object from the target device object. Also, DO_DIRECT_IO, DO_BUFFERED_IO, DO_POWER_INRUSH and DO_POWER_PAGABLE bits are copied from the Flags field of the target device object. This means that the filter will have the same buffering policy as the target driver.

In the RemoveDevice routine, you must disconnect the filter from the target device object. This is done by calling IoDetachDevice and passing in a pointer to the target device object. When the filter device object is disconnected, the RemoveDevice routine calls IoDeleteDevice to delete the unnamed filter device object.

When the filter driver is attached to the target driver, all I / O requests to the target driver are first passed through the filter driver's dispatch routine. If the MajorFunction table of the filter driver object does not support the same IRP_MJ_XXX code as the target driver, problems will occur to the client after the filter driver is attached. Strictly speaking, a driver that performed well in the absence of a filter would behave incorrectly after the filter was attached.

To avoid this problem, the filter driver's MajorFunction table must support all IRP_MJ_XXX functions supported by the target driver. Also, even if the filter driver does not want to modify some specific MajorFunction code, the filter driver's dispatch routine should simply pass the IRP to the underlying driver.

The simplest way to solve this problem in the filter driver is to provide all of the dispatch routines in the filter driver's MajorFunction table as pass-through routines (routines that simply pass the IRP down). If you want to make modifications to the filter in the MajorFunction entry, you will need to provide non-pass-through simply by passing that part.

2 is a flowchart illustrating a method of displaying a multi-mouse pointer according to an embodiment of the present invention.

In operation S100, memory of a physical driver of the computer system is loaded. Physical drivers are drivers that manage the connection between hardware and computer systems.

In step S110, the added mouse device is registered using the memory of the physical driver loaded in step S100. Registration of the mouse device includes creating a mouse device and adding the mouse device to the device stack.

In step S120, a symbolic link is generated that connects the user visible name to the mouse device registered in step S110 and the mouse device.

In step S130, an event generated by the mouse device registered in step S110 is set. Events set in one embodiment of the present invention, for example, left mouse button down, left mouse button up, right mouse button down, right mouse button up, vertical mouse movement, horizontal mouse movement, mouse wheel down, mouse wheel And one or more of up, mouse wheel scroll down, and mouse wheel scroll up.

In step S140, a thread for the mouse device registered in step S110 is executed, and the event set in step S130 is prepared. When a computer program executes, a thread refers to a path of execution, that is, a series of executable codes that exist inside a process. When you run a computer program, the process is just a shell, and the actual work is the thread. When a process is created, one main thread is created to handle most of the work. When the main thread terminates, the process also terminates. Multitasking is an environment in which several processes run concurrently in one OS, and multiple threads are executed simultaneously in one process.

In operation S150, an application to which the multi-mouse is applied is driven, and an event occurring on the driven application is detected. In this case, the detecting event is an event set in step S130. Such event detection is performed by hooking when the OS of the computer system detects a mouse event of a registered logical driver.

In step S160, the mouse cursor is already placed on the window of the application driven in step S150 by dynamically calculating the total window size and the application window size to which the multi-mouse device is applied based on the event detected in step S150. Display the mouse pointer.

3 is a flowchart illustrating a detailed process of a registration step of a mouse device in a method of displaying a multi-mouse pointer according to an embodiment of the present invention.

In step S112, a filter device object for a mouse device is created. The filter device object has no internal name and no symbolic link name.

In step S114, the filter device object created in step S112 is placed on the top of the device stack to obtain a pointer of the mouse device object.

A stack is a data structure that is a linear list of data insertions and deletions that occur only at one end. The insertion and deletion of data occurs at the top of the stack, pushing data onto the stack, and popping data off the stack. The stack uses last-in-first-out (LIFO) method, in which data entered later is taken out first. It is mainly used when you want to remember something and use it again.

As described above, in one embodiment of the present invention, the same module as the existing mouse driver is used to generate a multi-mouse pointer. However, a new driver is used through a unique ID of the mouse, that is, a globally unique identifier (GUID). Register in the registry to recognize it. New driver mouse events, for example, left mouse button down, left mouse button up, right mouse button down, right mouse button up, vertical mouse move, horizontal mouse move, mouse wheel down, mouse wheel up, mouse wheel scroll down And a mouse wheel scroll up and the like, and dynamically calculate the total window size and the application window size to which the multi-mouse device is applied, and output the mouse cursor as an image so that two or more mice can be used.

FIG. 4 is a diagram illustrating a relationship between an internal name and a symbolic link name in an object manager namespace in a method of generating a pointer for using a multi mouse according to an embodiment of the present invention.

Devices can have one or more names. The name assigned internally by IoCreateDevice tells the OS what device it is. This internal name is hidden from Win32 user applications. A new device must be given a symbolic link name in addition to its internal name to inform the Win32 subsystem, Win16 subsystem, or virtual Dos environment.

These two kinds of names exist in different namespaces of the object manager. The object manager manages name directories for all resources managed by the operating system. Internal device names are stored under the \ Device section of the directory tree. The symbolic link name is ＼ ?? It exists under the tree. Also, when using IoCreateDevice, the ＼Device name must be given. For example, the form "\ Device \ Minimal0" would be a suitable device name string. Since the backslash is a special character like ＼t in C, it must be written as double backslash.

Symbolic link names follow a different device nomenclature than internal device names. Internal device names are usually long, and they always end in a number based on zero (eg FloppyDisk0 or FloppyDisk1). Symbolic link names usually follow the form A to Z for file system devices and end with a number of 1s (LPT1 or LPT2) for other devices.

To create a symbolic link name, use IoCreateSymbolicLink. This function takes as arguments the name of an existing device and a new symbolic name (UNICODE_TRING data type).

Finally, note that the choice of device name is not a mandatory option. In WDM, bus drivers, class drivers, and many PnP devices define their names.

The invention can also be embodied in the form of a recording medium containing instructions executable by a computer, such as a program module executed by the computer. Computer readable media can be any available media that can be accessed by a computer and includes both volatile and nonvolatile media, removable and non-removable media. In addition, computer readable media may include both computer storage media and communication media. Computer storage media includes both volatile and nonvolatile, removable and non-removable media implemented in any method or technology for storage of information such as computer readable instructions, data structures, program modules or other data. Communication media typically includes computer readable instructions, data structures, program modules, or other data in a modulated data signal such as a carrier wave, or other transmission mechanism, and includes any information delivery media.

Although the method of the present invention has been described in connection with specific embodiments, some or all of their components or operations may be implemented using a computer system having a general purpose hardware architecture.

5 illustrates an example of a computer system architecture that may be used to perform one or more of the components or operations described above. In one embodiment, hardware system 800 includes a processor 810, a cache 815, a memory 815, and one or more software applications and drivers related to the functions described above.

Additionally, hardware system 800 includes a high performance input / output (I / O) bus 840 and a standard I / O bus 870. The host bridge 820 couples the processor 810 to the high performance I / O bus 840, and the I / O bus bridge 850 couples the two buses 840 and 870 with each other. System memory 860 and network / communication interface 830 are coupled to high performance I / O bus 840. The hardware system 800 may further include a video memory (not shown) and a display device coupled to the video memory. Mass storage 880 and I / O port 890 are coupled to standard I / O bus 870. Hardware system 800 may optionally include a keyboard and pointing device, and a display device (not shown) coupled to standard I / O bus 870. Collectively, these elements are intended to represent a wide range of computer hardware systems, including but not limited to general purpose computer systems based on appropriate processors.

The components of hardware system 800 are described in more detail below. More specifically, network interface 830 provides communication between a hardware system and any wide range of networks, such as an Ethernet (eg, IEEE 802.3) network or the like. The network interface 830 connects between the hardware system 800 and the network so that the hardware system 800 manages their databases. Mass storage 880 provides permanent storage for data and programming instructions to perform the above-described functions implemented in the present invention, and system memory 860 (e.g., DRAM) is implemented by processor 810. It provides temporary storage for data and programming instructions as it is performed. I / O port 890 is one or more serial and / or parallel communication ports that provide communication between additional peripheral devices that may be coupled to hardware system 800.

Hardware system 800 may include various types of system architectures, and various components of hardware system 800 may be rearranged. For example, the cache 815 may be embedded in the processor 810. Optionally, cache 815 and processor 810 may be bundled together as a "processor module", where processor 810 may be referred to as a "processor core." In addition, certain embodiments of the invention may not require or include all of the foregoing components. For example, peripherals shown as being coupled to the standard I / O bus 870 may couple to the high performance I / O bus 840. In addition, in any embodiment there may be only one bus and components of hardware system 800 may be coupled to that one bus. Moreover, hardware system 800 may include additional components such as additional processors, storage devices, or memory. As discussed below, in one embodiment, the operation of the present invention may be implemented as a series of software routines driven by hardware system 800. Such software routines include a plurality or series of instructions that may be executed by a processor in a hardware system such as processor 810. First, a series of instructions are stored in a storage device such as mass storage device 880. However, the sequence of instructions may be stored on any suitable storage medium, such as diskette, CD-ROM, ROM, EEPROM, or the like. Moreover, the series of commands need not be stored locally, and can be received from a remote storage device such as a server on the network via the network / communication interface 830. The instructions are copied from a storage device such as mass storage device 880 to system memory 860 and accessed and executed by processor 810.

The operating system manages and controls the operation of the hardware system 800, including data input / output with software applications (not shown). The operating system provides an interface between the software applications running on the system and the hardware components of the system. The operating system according to an embodiment of the present invention may be Microsoft's Windows 95/98 / NT / XP / VISTA operating system. However, the present invention can also be used in other suitable operating systems, such as Apple Computer's Apple Macintosh operating system, UNIX operating system, Linux operating system, and the like.

The foregoing description of the present invention is intended for illustration, and it will be understood by those skilled in the art that the present invention may be easily modified in other specific forms without changing the technical spirit or essential features of the present invention. will be. Therefore, it should be understood that the embodiments described above are exemplary in all respects and not restrictive. For example, each component described as a single type may be implemented in a distributed manner, and similarly, components described as distributed may be implemented in a combined form.

Although the embodiments of the present invention have been described in detail above, the scope of the present invention is not limited thereto, and various modifications and improvements of those skilled in the art using the basic concepts of the present invention defined in the following claims are also provided. It belongs to the scope of rights.

According to the present invention, it is possible to apply two or more mice to various applications by detecting an event generated by two or more mice and displaying a mouse pointer for each mouse in response thereto.

Claims (6)

In the multi-mouse pointer display method, Loading the memory of the device driver of the computer system, Registering the added mouse device by using the memory of the loaded device driver; Setting an event generated by the mouse device, Executing a thread for the mouse device, Driving an application to which a multi-mouse is applied and detecting an event occurring on the driven application, wherein the detected event is the set event; Displaying a mouse pointer by dynamically calculating a total window size and an application window size to which the multi-mouse is applied based on the detected event; Generating a symbolic link connecting the registered mouse device and a user visible name to the mouse device; The mouse device registration step may include creating a filter device object for the mouse device; Placing the created filter device object on top of a device stack and obtaining a pointer to a mouse device object Multi-mouse pointer display method comprising a. The method of claim 1, The event detection is performed by hooking the event when an operating system (OS) of the computer system detects an event for the registered mouse device. delete The method of claim 1, The set event includes left mouse button down, left mouse button up, right mouse button down, right mouse button up, vertical mouse movement, horizontal mouse movement, mouse wheel down, mouse wheel up, mouse wheel scroll down and mouse of the mouse device. And at least one of wheel scroll ups. delete A computer-readable recording medium having recorded thereon a program for generating and operating a pointer of a multi-mouse, comprising: A computer-readable recording medium having recorded thereon a program for performing each step according to any one of claims 1, 2 and 4.

Images