Technical Field

The present disclosure relates generally to user interaction with an electronic device having a touch screen display, and a more specifically to precision selection of items and/or points using an electronic device having a touch screen display.

Background Information

Touch screen displays are becoming increasingly common on a variety of types of electronic devices. For example, most mobile devices (e.g., smartphones, tablet computers, etc.) employ some form of touch screen display, and use touch input as their primary mode of user input. By its very nature, touch input may be quick and intuitive, making it well suited for many types of applications. However, for some types of applications, touch input may be less than ideal. In its native form, touch input often lacks the level of detail and precision provided by traditional keyboard and mouse based input. A high level of detail and precision may be important to some applications, for example, to computer aided design (CAD) applications, where a user may be called upon to discriminate between nearby items or points, to select a desired one.

The lack of detail and precision in touch based input stems from a variety of sources. One source is the reduced number of input types that are possible with touch based input, as compared to keyboard and mouse based input. With a keyboard and mouse, a user may enter a large number of distinct types of input, using the movement sensor of the mouse, the various buttons on the mouse, the scroll wheel of the mouse, and the various keys of the keyboard, alone, or in combinations. Each of these distinct types of input can be directly mapped to types of actions in an application.

However, with touch based input, a user generally has fewer types of input they may enter, being limited to movements recognized on the touch screen display. For example, while a user may tap, hold, pinch, drag, swipe, etc., on the touch screen display, there are a fairly limited number of different things the user can do. This may pose a problem when designing a user interface for an application. While a designer may desire to directly map a variety of actions supported by the application to distinct types of input, there may simply be more actions than input types. Another source of the lack of detail and precision stems from the typical lack of persistent position tracking on touch screen displays. With a typical keyboard and mouse based user interface, a cursor is persistently displayed to designate a position. Even if the user is not moving the mouse, the cursor is still shown, and its lingering presence can be used to trigger actions. For example, a "hover over" may be detected, where the cursor is maintained over an object for a short period of time. This may trigger an action (e.g., displaying information, such as a "tool tip", about the object). However, this type of interaction is typically not available on touch screen displays. Traditionally, on touch screen displays, position is only designated momentarily, when a user touches the screen. As such, interactions such as "hover overs" are generally not enabled.

Still another source of the lack of detail and precision stems from ambiguity in position designation on touch screen displays. With a mouse, a user can generally select a single pixel in a user interface. A user can see the cursor, and move it to exactly where they desire, making tiny adjustments as needed. However, with a touch screen display, this type of operation is generally not possible. When a user touches the screen, their finger (or the stylus, if one is used) typically obscures their view of the position they are trying to designate. The position is somewhere under their finger (or the stylus tip), but the user cannot generally see where. Further, the entire area of contact is generally registered as being touched, rather than a distinct point. Algorithms must be employed to try to guess where in this area the user really intended to designate. Given this guesswork, when items or points are close together, a user may have to repeatedly touch the display screen, until they happen upon the desired result.

Accordingly, there is a need for improved techniques for selection of items and/or points using a touch-screen display. While this need may be applicable to a variety of types of applications executing on electronic devices (e.g., mobile devices), it may be particularly acute for CAD applications executing on mobile devices.

SUMMARY

In one embodiment, a virtual mouse is provided for interacting with an electronic device (e.g., a mobile device) having a touch screen display. The virtual mouse, when displayed on the touch screen display, may include a pointer, and a control region proximate to, but offset from, the pointer. The pointer identifies a position of an item (e.g., an element of a computer aided design (CAD) model) or a point (e.g., a point within a view of the CAD model) displayed in the user interface of an application (e.g., a CAD application). In one implementation, the pointer is represented as a crosshairs, whose appearance may change depending upon whether it is being used to select an item or a point. The control region of the virtual mouse may include a movement area for receiving touch input, and one or more buttons for performing actions related to the item or point identified by the pointer. Input (e.g., a touch and drag) received in the movement area may be mapped to movement of the entire virtual mouse. As such, by interacting with the movement area, a user may move the pointer such that the pointer is displayed at a position that identifies a desire item or point, with the movement area and buttons displayed proximate to, but offset from, that position. By selecting one of the buttons, a user may trigger actions related to the item or point. The actions may include selecting the item or point, deselecting the item or point, changing one or more settings related to the item or point, or another type of action possible in the user interface of the application. The number and functions of the buttons may vary depending on the present usage of the virtual mouse.

Among other benefits, the virtual mouse may enable more detailed and precise control than generally possible on a touch screen display. Since the virtual mouse provides buttons whose number and functions may vary based on usage, a greater number of input types can be supported than with traditional touch input techniques. Further, the presence of the pointer may provide persistent position tracking, allowing user interface interactions such as "hover over". Still further, by utilizing an offset movement area, the user' s view of the pointer is un-obstructed, allowing the user to readily discriminate between nearby items or points.

It should be understood that a virtual mouse may include a variety of additional or alternative features, which provide additional or alternative advantages. This Summary is intended simply as an introduction to the reader, and does not indicate or imply that the features mentioned herein cover all aspects of the invention, or are necessary or essential aspects of the invention. BRIEF DESCRIPTION OF THE DRAWINGS

The detailed description below refers to the accompanying drawings of example embodiments, of which:

Fig. 1 is a block diagram of an example electronic device, for example, a mobile device, on which a virtual mouse may be implemented;

Fig. 2 is a diagram of an example virtual mouse that may be displayed on a touch screen display;

Fig. 3 is a flow diagram of an example sequence of steps for using a virtual mouse to interact with an electronic device (e.g., a mobile device) to perform certain operations;

Fig. 4 is a screen shot of a user interface of an example CAD application, illustrating an example way of activating the virtual mouse;

Fig. 5 is a screen shot of the user interface from Fig. 4, updated to show the virtual mouse after activation;

Fig. 6 is a screen shot of a user interface of an example CAD application, illustrating an example first step in measuring the volume of an element;

Fig. 7 is a screen shot of the user interface from Fig. 5, updated to show a next step in measuring the volume of an element;

Fig. 8 is a screen shot of the user interface from Figs. 5 and 6, updated to show the measured volume of a selected element;

Fig. 9 is a screen shot of a user interface of the example CAD application, illustrating an example first step in measuring a distance between two points;

Fig. 10 is a screen shot of the user interface from Fig. 9, updated to show a next step in measuring the distance between two points;

Fig. 11 is a screen shot of the user interface from Figs. 9 and 10, updated to show still another step in measuring the distance between two points;

Fig. 12 is a screen shot of the user interface from Figs. 9-11, updated to show the measured distance between two points. DETAILED DESCRIPTION

Fig. 1 is a block diagram of an example electronic device 100, for example, a mobile device, on which a virtual mouse may be implemented. As used herein, the term "mobile device" refers to a computing device that is adapted to be transported on one's person. Devices such as tablet computers and smartphones are generally considered mobile devices. Devices such as desktop computers are generally not considered mobile devices. The electronic device (e.g., mobile device) 100 may include at least one processor 110 coupled to a host bus 120. A volatile memory 130, such as a random access memory (RAM), may be coupled to the host bus 120 via a memory controller 125. The memory 130 may store at least a portion of executable instructions for an operating system 135 (e.g., a Windows®, Android®, or iOS® operating system), an application 140 (e.g., a computer aided design (CAD) application), and a virtual mouse module 144, as well as other applications and software 146. In an implementation where the application is a CAD application, the CAD application may be any of a variety of types of CAD model creation, viewing and/or analysis application. In one implementation, the CAD application may be the Bentley® Navigator V8i application, available from Bentley Systems Inc.

The virtual mouse module 144 may include executable instructions to implement a virtual mouse. In one implementation, the virtual mouse module 144 is part of the application 140 (e.g., the CAD application) itself. In such a case, use of the virtual mouse may be confined to be within a user interface of the application 140. Alternatively, the virtual mouse module 144 may be implemented as a stand-alone application, or as part of the operating system 135. In such a case, it may be possible to use the virtual mouse across user interfaces of multiple applications, for example, in both the application 140 (e.g., the CAD application) and the other applications and software 146, as they are executed on the electronic device 100. The virtual mouse module 144 may interact with a number of application program interfaces (APIs) and functions (not shown) of the application 140, operating system 135, and potentially other applications and software 146. In an example where the operating system 135 is a Windows® operating system, the APIs and functions may include the well known SetCapture, ReleaseCapture, GetCursorPos, SetCursorPos, GetPhysicalCursorPos, SetPhysicalCursorPos, and Sendlnput functions of the Windows® operating system. In an example where the operating system 135 is an Android® or iOS® operating system, the APIs and functions may include components that have analogous functionality.

The host bus 120 of the electronic device 100 may be coupled to an input/output (I O) bus 150 through a bus controller 145. A video display subsystem 155 that includes a touch screen display 170 may be coupled to the I/O bus 150. The touch screen display 170 may show a user interface of the application 140 (and potentially of the other applications and software 146) with which the virtual mouse may be utilized. The touch screen display screen 170 may be designed to receive touch input from a user (e.g., via their finger(s) and/or a stylus), which includes single-touch gestures (involving one point of contact with the touch screen display) and/or multi-touch gestures (involving multiple points of contact with the touch screen display).

In addition to the touch screen display 170, one or more other types of input devices 160 may be included in mobile device and coupled to the I/O bus 150. For example, various physical buttons or sensors (e.g., an orientation sensor, a camera, etc.) may be included. A persistent storage device 165, such as a solid-state drive, flash memory, or other type or persistent data store, may be coupled to the I/O bus 150, and used to persistently store executable instructions that are loaded into the volatile memory 130 when needed. For example, executable instructions for the operating system 135, application 140, virtual mouse module 144, and the other applications and software 146 may be stored thereon, and then loaded when needed. The I/O bus 150 may further be coupled to a network interface 180, for example a wireless network interface, which interfaces with a computer network 190. The computer network 190 may allow communication between the electronic device 100 and other electronic devices, using any of a number of well known networking protocols, to permit a variety of distributed, collaborative or remote computing configurations.

Fig. 2 is a diagram of an example virtual mouse 200 that may be displayed on a touch screen display. The virtual mouse 200 includes a pointer 210 and a control region 220 proximate to, but offset from, the pointer. The pointer 210 identifies a position of an item or a point displayed in a user interface on the touch screen display. In an implementation where the application 140 is a CAD application, the user interface may be a user interface of the CAD application, the item may be an element of a CAD model shown in the user interface of the CAD application, and the point may be a point within a view of the CAD model. In other implementations, the item or point may take on different forms.

The pointer 210 may be represented as a crosshairs or other designator of position. In some cases, the appearance of the pointer 210 may dynamical change, depending on the usage of the virtual mouse 200, for example, based on a task being performed with the virtual mouse. The differing appearance may include multiple styles of crosshairs (e.g., an open centered crosshair, a closed center crosshair, etc.), different colors of crosshairs, entirely different pointer styles, etc.

The control region 220 may include a movement area 230 for receiving touch input, and one or more buttons 240 for performing actions related to the item or point identified by the pointer 210. The movement area may be sized to accommodate a user's fingertip, for example, be about 7-9mm in diameter. Touch input (e.g., a touch and drag) in the movement area 230 may be mapped to movement of the entire virtual mouse 200, such that the pointer 210, movement area 220, and the buttons 230, move together. The movement area 230 may be maintained proximate to, but offset from, the pointer 210 as any movement occurs.

The buttons 230 may be used to trigger actions related to the item or point disposed at the position identified by the pointer 210. The actions may include selecting the item or point, deselecting the item or point, displaying or changing one or more settings related to the item or point, or another type of action. In an implementation where the application 140 is a CAD application, the action may be to select an element of a CAD model or a point within a view of the CAD model, deselect the element or point, display or change properties of the element or point, or another type of CAD specific action.

Depending on the current usage of the virtual mouse 200, the number of buttons 230, their type, and the actions they trigger, may vary. Similarly, depending on the item or point that may be at the position identified by the pointer 210, the number of buttons 230, their type, and the actions they trigger may change. In such manner, the nature of the buttons 230 that are provided may be responsive to both a current usage and the item or point at the position identified by the pointer 210. In some cases, no buttons 230 may be displayed, for example, where no action is appropriate given the current usage or the item or point at the position. In an implementation where the application 140 is a CAD application, the current usage may be, for example, a measurement operation involving an element of the CAD model or one or more points within the view of the CAD model, such as a volume measurement operation, a distance measurement operation, etc.

Fig. 3 is a flow diagram of an example sequence of steps 300 for using a virtual mouse 200 to interact with an electronic device (e.g., a mobile device) to perform certain operations. At step, 310, the virtual mouse 200 is activated. When activated, the virtual mouse module 144 may interact with the operating system 135, the application 140 (e.g., the CAD application) and/or the other applications and software 146, to cause the virtual mouse 200 to be displayed on the touch screen display 170, for example, superimposed over a portion of a user interface of the application 140 and/or the other applications and software 146. Activating the virtual mouse 200 may coincide with entering a certain mode, for example, a precision selection mode, that is adapted for receiving more precise input than generally possible with a normal interface. The virtual mouse may be activated in response to a gesture on the touch screen display 170 (e.g., a two finger tap_, a selection in a context menu, or some other type of touch input.

Once activated, the virtual mouse 200 may be utilized. At step 320, touch input (e.g., a touch and drag) may be received in the movement area 230 of the virtual mouse 200, indicating a user's desire to move the virtual mouse. At step 330, in response to the touch input in the movement area 230, the virtual mouse module 144 may move the virtual mouse 200, including the pointer 210, to track the supplied input. Eventually, the pointer 210 may be disposed over a desired item or point (e.g., an element of a CAD model or a point within a view of the CAD model).

At step 340, touch input (e.g., a touch) is received on a button of the one or more buttons 230. At step 350, in response to the touch input on the button, the virtual mouse module 144 interacts with the application 140 and/or the other applications and software 146, to cause an action related to the item or point to be performed. For example, the item or point may be selected.

Steps 320-350 may be repeated to move the virtual mouse about, to identify different items or points, and to perform different actions. Eventually, at step 360, when the virtual mouse 200 is no longer needed, the virtual mouse may be deactivated and removed from touch screen display 170. Similar to activation, the virtual mouse may be deactivated in response to a gesture on the touch screen display 170, for example, a one finger tap away from the virtual mouse 200, a selection in a context menu, or some other type of touch input. In some cases, the virtual mouse 200 may be deactivated automatically, for example, in response to an action being performed.

Fig. 4 is a screen shot 400 of a user interface of an example CAD application, illustrating an example way of activating the virtual mouse 200. A view (e.g., an elevation) 410 of a building derived from a CAD model is shown in the user interface. The user may trigger the display of a context menu 420 with touch input (e.g., a hold gesture). The context menu 420 may be displayed about the position of the user's hold, and provide a number of selectable options, including an option to enter a precision selection mode in which the virtual mouse 200 is used. The user may select (e.g., touch) that option (the touch being represented by marker 430) to enter the precision selection mode, and activate the virtual mouse 200.

Fig. 5 is a screen shot 500 of the user interface from Fig. 4, updated to show the virtual mouse 200 after activation. The virtual mouse 200 may initially be positioned where the context menu 430 was previously displayed, superimposed upon a portion of the view (e.g., elevation) 410 of the building. In addition, information 420 about using the virtual mouse 200 may be displayed, at least upon the first few uses of the virtual mouse. The information 420 may include tips regarding alternative ways of activating the virtual mouse. For example, a tip may be provided reminding the user that a gesture, for example, a two finger tap, may be used to activate the virtual mouse by entering a precision selection mode.

Fig. 6 is a screen shot 600 of a user interface of an example CAD application, illustrating an example first step in measuring the volume of an element. The user may initially select (e.g., touch) an icon 610 for a measurement tool group to cause a menu 620 to be displayed in the user interface. The user may then select (e.g., touch) an icon for a volume measure tool in the menu 620 (the touch being represented by marker 630). Thereafter, the user may be prompted (not shown) to select an element whose volume is to be measured.

Fig. 7 is a screen shot 700 of the user interface from Fig. 6, updated to show a next step in measuring the volume of an element. The user activates the virtual mouse 200 by entering a precision selection mode. The user may then move the pointer of the virtual mouse to be over an element (in this example, a 90° elbow of a pipe), by interacting with the movement area of the virtual mouse 200. A listing 720 showing the name of the element under the pointer 210 may be displayed. In some cases, if there are multiple elements under the pointer, multiple elements may be displayed in the listing 720, and the user invited to choose between them. Each such element may be highlighted in the user interface. The user may select a particular element by interacting with (e.g., touching) a button of the virtual mouse 200 (the touch being represented by marker 710).

Fig. 8 is a screen shot 800 of the user interface from Figs. 6 and 7, updated to show the measured volume of a selected element. The virtual mouse 200 may be deactivated by exiting the precision selection mode (e.g., automatically upon the element being selected and the volume being measured). The measured volume of the element may be displayed in a text box 810.

Fig. 9 is a screen shot 900 of a user interface of an example CAD application, illustrating an example first step in measuring a distance between two points. This time, after the user initially selects (e.g. touches) an icon 610 for the measurement tool group, the user may select (e.g., touch) an icon for a distance measure tool (the touch being represented by marker 930). Thereafter, the user may be prompted (not shown) to select a first point, from which distance is to be measured.

Fig. 10 is a screen shot 1000 of the user interface from Fig. 9, updated to show the next step in measuring the distance between two points. The user again activates the virtual mouse 200 by entering the precision selection mode. The pointer of the virtual mouse 200 may have a different appearance than in Fig. 7, providing a visual reminder that a point, rather than an element is being selected. The user may move the pointer to be over a first point, that distance is measured from, by interacting with the movement area of the virtual mouse 200. The user may then select the first point by interacting with (e.g., touching) a button of the virtual mouse (the touch being resented by marker 1010).

Fig. 11 is a screen shot 1100 of the user interface from Figs. 9 and 10, updated to show still another step in measuring the distance between two points. The user may move the pointer of the virtual mouse 200 to be over a second point, to which distance is measured, by interacting with the movement area of the virtual mouse 200. The user may then select the second point by interacting with (e.g., touching) a button of the virtual mouse (the touch being represented by marker 1110). Additional information 1120, for example coordinates from an origin centered at the first point, may be displayed to the user to assist in selection of the second point.

Fig. 12 is a screen shot 1200 of the user interface from Figs. 9-11, updated to show the measured distance between the two points. Again, the virtual mouse 200 may be deactivated by exiting the precision selection mode (e.g., automatically upon selection or the second point and the distance being measured). The measured distance may be displayed in a text box 1210.

A wide variety of other uses of the virtual mouse 200 may be possible. It should be understood that a wide variety of modifications and/or additions to what is described above are possible. In general, the above descriptions are meant to be taken only by way of example.

The virtual mouse may achieve several advantages over traditional touch based control techniques. Among its benefits, the virtual mouse may enable more detailed and precise control than generally possible on a touch screen display. Since the virtual mouse provides buttons whose number and functions may vary based on usage, a greater number of input types can be supported than with traditional touch input techniques. Further, the presence of the pointer may provide persistent position tracking, allowing user interface interactions such as "hover over". Still further, by utilizing an offset movement area, the user's view of the pointer is un-obstructed, allowing the user to readily discriminate between nearby items or points.

It should be understood that, depending on the implementation, some or all of these advantages may be achieved. Alternatively other advantages may instead be achieved.

What is claimed is: