Method and apparatus for supporting two-dimensional windows in a three-dimensional environment

A user interface for a computer system controls the creation and appearance of windows in a computer display. Aspects of the interface include utilizing three-dimensional rendering technology to render two-dimensional windows as texture on three-dimensional objects, automatically positioning windows in a primary viewing area so that the windows appear aligned with each other, and providing a three-dimensional start palette that contains icons for opening windows on the display.

BACKGROUND OF THE INVENTION

The present invention relates to computer interfaces. In particular, the present invention relates to three-dimensional computer interfaces.

Currently, three-dimensional computer interfaces are being developed that allow a user to navigate through a three-dimensional space that contains icons and windows representing documents and applications. However, current systems do not combine existing three-dimensional rendering technology with two-dimensional window data in a way that allows the windows to be rendered easily in the three dimensional environment while retaining the ability to identify the location of a cursor relative to the displayed window.

In addition, although a three-dimensional space provides more room for displaying two-dimensional windows, it also applies a greater burden on the user to position the windows properly in the space. In particular, current operating systems (both three-dimensional based and two-dimensional based) fail to provide an optimum method for placing two or more windows in an area so that the windows have the same general shape and size and do not overlap each other. Currently, in order to place two or more windows in such an area, the user must change the shape and size of one or both of the windows to be viewed and manually move the windows into the desired area. These manual steps reduce the efficiency of using the computer system. Thus, a system is needed that allows windows to be positioned in a three-dimensional space but that also limits the positioning burden placed on the user.

In addition, because the user can move in such three-dimensional environments, they are often some distance from the application icons they want to access. Thus, the user is often forced to navigate through the environment to reach the documents and applications they want to use. This is a burden to the user, especially when the user has to navigate through the environment for applications and documents that they access frequently.

Current interfaces also fail to provide descriptive icons to represent windows that are currently running on the system but that may not be currently visible to the user. In some two-dimensional desktop interfaces of the prior art, a taskbar is provided that includes icons for each active window on the desktop. However, these icons do not provide much information about the status of the window's contents and in some cases two or more icons can look the same on the taskbar.

SUMMARY OF THE INVENTION

The present invention provides a user interface for a computer system that includes several aspects.

Under one aspect of the invention, a three-dimensional space is provided that includes a primary viewing area and an ordered stack area. Windows in the ordered stack may have their order changed by the user, but the actual position of the windows in the stack is automatically set by the system.

Under another aspect of the invention, a system automatically adjusts the size and position of the windows in the primary viewing area so that all of the windows appear to be the same size.

Under a third aspect of the invention, a three-dimensional start palette is provided in a three-dimensional toolspace. The palette includes application and document icons that may be selected by the user to start the application or open a window containing the document. In most embodiments, the start palette travels with the virtual user as the virtual user moves through the environment.

A fourth aspect of the invention utilizes three-dimensional rendering technology to display a two-dimensional window in a three-dimensional environment. In particular, this aspect of the invention applies the window data as texture on a three-dimensional object that is defined in the three-dimensional space. The window is displayed along with a cursor that has a location defined by screen coordinates. Using the location and orientation of the three-dimensional object, the location of the cursor is calculated relative to the displayed window, and the new coordinates are passed to the window's application.

DETAILED DESCRIPTION OF ILLUSTRATIVE EMBODIMENTS

With reference toFIG. 1, an exemplary system for implementing the invention includes a general purpose computing device in the form of a conventional personal computer20, including a processing unit (CPU)21, a system memory22, and a system bus23that couples various system components including the system memory22to the processing unit21. The system bus23may be any of several types of bus structures including a memory bus or memory controller, a peripheral bus, and a local bus using any of a variety of bus architectures. The system memory22includes read only memory (ROM)24and random access memory (RAM)25. A basic input/output (BIOS)26, containing the basic routine that helps to transfer information between elements within the personal computer20, such as during start-up, is stored in ROM24. The personal computer20further includes a hard disk drive27for reading from and writing to a hard disk (not shown), a magnetic disk drive28for reading from or writing to removable magnetic disk29, and an optical disk drive30for reading from or writing to a removable optical disk31such as a CD ROM or other optical media. The hard disk drive27, magnetic disk drive28, and optical disk drive30are connected to the system bus23by a hard disk drive interface32, magnetic disk drive interface33, and an optical drive interface34, respectively. The drives and the associated computer-readable media provide nonvolatile storage of computer readable instructions, data structures, program modules and other data for the personal computer20.

Although the exemplary environment described herein employs the hard disk, the removable magnetic disk29and the removable optical disk31, it should be appreciated by those skilled in the art that other types of computer readable media which can store data that is accessible by a computer, such as magnetic cassettes, flash memory cards, digital video disks, Bernoulli cartridges, random access memories RAMs), read only memory (ROM), and the like, may also be used in the exemplary operating environment.

A number of program modules may be stored on the hard disk, magnetic disk29, optical disk31, ROM24or RAM25, including an operating system35, one or more application programs36, other program modules37, and program data38. A user may enter commands and information into the personal computer20through local input devices such as a keyboard40, pointing device42and a microphone43. Other input devices (not shown) may include a joystick, game pad, satellite dish, scanner, or the like. These and other input devices are often connected to the processing unit21through a serial port interface46that is coupled to the system bus23, but may be connected by other interfaces, such as a sound card, a parallel port, a game port or a universal serial bus (USB). A monitor47or other type of display device is also connected to the system bus23via an interface, such as a video adapter48. In addition to the monitor47, personal computers may typically include other peripheral output devices, such as a speaker45and printers (not shown).

The personal computer20may operate in a networked environment using logic connections to one or more remote computers, such as a remote computer49. The remote computer49may be another personal computer, a hand-held device, a server, a router, a network PC, a peer device or other network node, and typically includes many or all of the elements described above relative to the personal computer20, although only a memory storage device50has been illustrated in FIG.1. The logic connections depicted inFIG. 1include a local area network (LAN)51and a wide area network (WAN)52. Such networking environments are commonplace in offices, enterprise-wide computer network Intranets, and the Internet.

Under the present invention, a three-dimensional user interface is generated that allows a user to manipulate and use windows by associating the windows with separate tasks. In the description below, this three-dimensional user interface is referred to alternatively as a task gallery, a data hallway, and a data mine. Generally, the three-dimensional user interface gives the user the perception that they are within a hallway or gallery consisting of a number of aligned hallway sections that end with a stage or display area at an end wall.

Task Gallery Layout

FIG. 2provides a top back perspective view of a task gallery200of one embodiment of the present invention with the ceiling in the gallery removed to expose the remainder of the gallery. Task gallery200includes rooms202,204,206and208that each have walls forming a portion of side walls210and212, and floors that form a portion of gallery floor214. Room208also includes an end wall216and a stage217.

FIG. 3provides a perspective view from the side of task gallery200of FIG.2. InFIG. 3, ceiling202of task gallery200is shown connecting side walls210, and212. Although only four rooms,202,204,206and208are shown inFIGS. 2 and 3, many task galleries of the present invention are indefinitely extendable by the user. In one embodiment, the user interface automatically generates additional rooms as the user moves objects out of the last existing room or creates new objects that necessitate the creation of new rooms. In such embodiments, the interface also removes back-end rooms if they no longer contain objects. Thus, the task gallery may consist of as few as one room.

When the user is using task gallery200ofFIG. 3, the three-dimensional image provided to the user is based upon the combination of the location of a virtual body, representing the user's body in the task gallery and the orientation of a virtual head or camera representing the user's head in the task gallery. The user's virtual head is able to rotate independently of the direction the virtual body is facing, so that the user can glance up and down and to the sides as discussed further below.

FIG. 4provides a screen image representing the view from the virtual camera when the virtual camera is directed toward end wall216and the virtual body is positioned at a location220in FIG.3. Thus, inFIG. 4, end wall216and stage217are shown as being some distance from the user and floor214, ceiling218, and walls210and212can be seen.

In some embodiments, each segment of the hallway is decorated so as to make it distinct from other segments of the hallway. For example, the walls, floor, and ceiling of a segment may be decorated with unique texture maps to make the hallway segment look unique. This helps to enhance the user's spatial memory of locations for storing or retrieving objects. Segments of the hallway may also be decorated with three-dimensional landmarks such as a virtual chair, a chandelier, or other decoration, to make the hallway segment further visually distinct and memorable.

Container Objects

In one embodiment of the invention, the user interface program that generates the three-dimensional task gallery is programmed using an object-oriented programming language. Under such an embodiment, a container object is defined that includes a property of containing other objects. The objects that are contained within a container object are known as containables. A displayed item associated with a containable object has its appearance and movement defined in part by the container object that holds the containable object.

In one embodiment, the task gallery is represented by a container object that contains room objects. Each room object contains two side wall objects, a floor object and a ceiling object. Each of these containable objects is in turn a container object that contains further objects. This hierarchy is shown inFIG. 5where task gallery object250contains room objects251and252. Room object251contains stage object254, left side wall object255, right side wall object256, end wall object257, floor object258, and ceiling object260. Room object252contains left side wall object270, right side wall object272, floor object274, and ceiling object276. When using a task gallery, the user may add task objects to the wall, floor or ceiling objects of a room. For example, task objects262, and264ofFIG. 5have been added to left side wall object270of room object252. When a task object is added to a structural object such as a left side wall object, the image associated with the task object appears bound to the image of the structure associated with the structural object.

For example,FIG. 6shows that a task image300appears near left side wall210of room208when the task object associated with task image300is contained within the left side wall object of the room.

The appearance of task300inFIG. 6is defined in part by the fact that the task object representing task300is contained within the left side wall object. In particular, task300appears on a stand302and has a title bar304placed along its top edge. The stand helps the user determine the three-dimensional location of the particular task. In addition, task300does not lie flat against wall210, but instead extends out into the hallway of the task gallery.

InFIG. 5, task objects are shown in right side wall object252, and ceiling object260of room object251and floor object274of room252. Examples of images associated with such task objects are shown inFIG. 6as right side wall task310, ceiling task308, and floor task306, respectively.

In the embodiment ofFIG. 6, floor task306appears with the top of the task closer to the end wall than to the user. In addition, a title bar312appears on the top edge of the task and the top edge is raised slightly from floor214to provide a better view of the task to the user.

Ceiling task308has its top edge closer to the user than to end wall216. The top edge of task308is covered by a title bar314and the lower edge of task308is suspended slightly from ceiling218to provide a better view of the task image. All of these arrangements may be created or changed by the user, at will, to provide arrangements optimized for particular uses.

Right side wall task310appears on a stand318and has a title bar316. Task310does not lie flat against wall212, but instead extends out into the hallway of the task gallery.

Note that the specific appearances of tasks300,306,308, and310shown inFIG. 6are only examples of one embodiment of the present invention. The specific appearance of any one of the tasks can be changed within the scope of the invention. In particular, tasks on side walls210and212may lie flat against the wall and may not appear with a stand. Under some embodiments, the height of the stand changes dynamically to accommodate the placement of the task so that the task always appears to have a visual link with the floor area below it.

In one embodiment, structural objects such as left side wall object255, right side wall object256, floor object258, and ceiling object260may each contain multiple task objects. In addition, task images associated with each task object may be moved along the image associated with the respective wall, ceiling or floor object that contains the task object. Moreover, a task object may be moved between container objects causing the task image to change in response to its new container object.

Movement of Tasks within the Gallery

The tasks and windows ofFIG. 6can be moved by the user. Table 1 below describes the relationship between certain input key strokes and pointing device events to the movement of windows and tasks within a task gallery such as the task gallery of FIG.6. The particular effects of each input are dependent on the location of the cursor. The first two columns of Table 1 indicate the type of window underneath the cursor and the task in which that window is located. The top row of Table 1 indicates the type of user input provided by the input device. Although specific user inputs have been listed in Table 1, those skilled in the art will recognize that other input devices can be used in place of those chosen and that not all affects shown within a same column for an input instruction are necessarily required to be controlled by the same input instructions. In other words, simply because two events occur in the same column in the embodiment of Table 1 does not necessarily mean that the same events must be generated for the same input instructions used in other embodiments.

In Table 1, there are seven different types of input instructions. The first is the left click instruction in which the left button of a pointing device is clicked by depressing and releasing the button. The second instruction is a shift-left click, in which the shift key of the keyboard is depressed while the left button of the pointing device is clicked. The third input instruction is a left drag plus “alt” key, in which the left button of the pointing device and the “alt” key of the keyboard are depressed while the pointing device is moved. The last four instructions are drag up; drag down, drag left, and drag right. These instructions involve depressing the left button of the pointing device and moving the pointing device up, down, left and right, respectively.

Those skilled in the art will recognize that other input instructions are possible under the present invention. For instance, under one embodiment, a secondary pointing device such as a touch pad is used to provide input. In alternative embodiments, input instructions are indicated by using a combination of keystrokes with the arrow keys on the keyboard.

As shown in Table 1, any task that does not have focus (i.e. any task that is not on stage217) may be moved by using a traditional drag technique. Thus, by positioning a cursor over the desired non-focus task, and depressing the primary button of the pointing device, the user can move the selected task by moving the pointing device. When the task is in the desired position, the user releases the primary button to “drop” the task in its new location. As discussed further below, some windows in the focus task can also be moved using this technique.

During a drag operation, the direction in which a task moves for a given movement of the pointing device is dependent upon which container object the task is contained within.FIG. 7describes the relationship between movement of the input pointing device and corresponding movement of a task contained by objects associated with floor214, ceiling218, stage217, and walls216,210and212. InFIG. 7, the arrows indicate the directions that objects move along the respective structures and the words by the arrows indicate the directions of movement of the pointing device. For walls216,210and212, movement forward and back with the pointing device results in movement of the selected task or window upward and downward, respectively. For a task on left side wall210, movement of the input device to the left and right causes the window to move respectively away from and toward end wall216. For a task on right side wall212, movement of the input device to the left and right causes the task to move respectively toward and away from end wall216. In essence, the task currently being moved by the user will appear to stay directly under the cursor.

For a task or window on end wall216, stage217, floor214, and ceiling218, movement of the input device left and right causes the window or task to move respectively left and right on the display. For tasks on stage217, floor214or ceiling218, movement of the input device forward and back causes the displayed window to move respectively toward and away from end wall216. In one embodiment, tasks and windows are restricted from moving freely in all three dimensions of the virtual space but instead are restricted to two-dimensional movement on the surface of a wall, floor or ceiling.

FIGS. 8A and 8Bdepict the movement of a task350along right side wall212. InFIG. 8A, task350is initially shown near the virtual user. The user then selects task350by positioning the cursor over task350and depressing the primary button of the pointing device. As the user moves the pointing device to the left, task350recedes toward stage217and is eventually dropped by the user at the location shown in FIG.8B. Note that because the present invention provides a three-dimensional user interface, as task350is moved toward stage217, it progressively appears smaller.

FIGS. 9A and 9Bshow the movement of a task352along left side wall210.FIGS. 10A and 10Bshow the movement of a task354along floor214as task354is moved toward the user and away from stage216.FIGS. 11A and 11Bshow the movement of a task356along ceiling218away from stage216and toward the user.

In one embodiment of the invention, tasks may be moved between the side wall, the ceiling and the floor. Such movements are shown inFIGS. 12A through 12I. InFIG. 12A, a task370is shown on wall212. InFIG. 12B, task370has been moved to the bottom of wall212near floor214. Continued movement downward along wall212eventually causes task370to be removed from wall212and placed onto floor214. To avoid the possibility that the task will flip-flop between the floor and the wall during the transition, one embodiment of the present invention includes a hysteresis distance along the floor and the wall. Thus, the mouse must continue to move a certain distance after the task meets the intersection of the floor and the wall before the task is moved to the floor. Likewise, the window will not move from the floor back to the wall until the mouse is moved a small distance to the right of the intersection of the floor and the wall.

In an object oriented embodiment, such as the embodiment ofFIG. 5, the movement of task370from wall212to floor214involves moving the task object associated with task370from the right side wall container object to the floor container object. As the task object is transferred, it loses the appearance and movement behavior dictated by the right side wall container object and adopts the appearance and movement behavior dictated by the floor container object. Thus, stand372, which is shown inFIGS. 12A and 12B, disappears in FIG.12C and the orientation of task370is changed so that task370leans toward stage216instead of extending out into the hallway. In addition, once the task object has been moved to the floor container object, left and right movement of the pointing device no longer moves the task toward and away from stage216but instead moves the task left and right across floor214.

InFIG. 12D, task370has been moved across floor214so that it is next to left side wall210.

Continued movement in this direction causes the task object associated with task370to be transferred from the floor container object to the left side wall container object. This causes the appearance of task370to change as shown inFIG. 12Ewhere task370is now shown on a stand374and is in an upright position along wall210. InFIG. 12F, task370has been moved upward along wall210toward ceiling218. As task370is moved upward, stand374expands so that it continues to connect task370to floor214.

InFIG. 12G, task370has been moved further upward along wall210causing the task object associated with task370to be removed from the left wall container object and into the ceiling container object. Because of this, the appearance of task370has changed by removing the stand found inFIGS. 12E and 12Fand leaning the bottom of task370toward stage216. Other embodiments include further changing the appearance of each task to suggest a more realistic relationship between a task and its location in a particular room. For example, a task moved to the ceiling area might have its appearance changed so that it looks like it is hanging from the ceiling. A task placed on the floor might grow legs so that it appeared to provide some semantic consistency with the environment.

InFIG. 12H, task370has been moved to the right across ceiling218toward right side wall212. Continued movement to the right causes the task object associated with task370to be removed from the ceiling container object and placed into the right wall container object. This causes a transformation in the appearance of task370as shown in FIG.12I. In particular, task370is again vertical in FIG.12I and has a stand376that extends from task370to floor214.

Objects on Stage

Returning to the hierarchy ofFIG. 5, it can be seen that stage object254contains only one task object268. In the embodiment shown inFIG. 6, when a task object is placed in stage object254, it becomes the focus task and is associated with an image that does not have a border around the task nor a title bar over the task. (Although in some embodiments, the title of the task can be seen in the backdrop of the focus task.) In addition, instead of being a single image element, a task on the stage consists of multiple window images that can each be manipulated by the user.

The window images of the focus task have associated window objects that are grouped into container objects within task object268. Specifically, as shown inFIG. 5, task object268contains a number of other container objects including a loose stack object270, an ordered stack object272, and a primary view object274. Each of these objects further contains a collection of window objects such as window objects276and278of loose stack object270. One of the windows contained by primary view object274is a focus window object280. Focus window object280is associated with an application, which receives keyboard and appropriate pointer device input values as long as its associated window object is designated as focus window object280.

Although multiple window objects are shown in loose stack270, ordered stack272and primary view274, these containers are not required to always contain a window object. At different times during the practice of the invention, each of these containers may be devoid of window objects.

Examples of window images associated with window objects found in a focus task, such as task268ofFIG. 5, are shown in FIG.6. InFIG. 6, window320is an image associated with a focus window object contained by a primary view object, windows322and324are associated with window objects contained by a loose stack object, and windows326and328are associated with window objects contained by an ordered stack object.

InFIG. 6, window320appears closer to the user than loose stack windows322and324and ordered stack windows326and328. Loose stack windows322and324each appear on stands, and ordered stack windows326and328each appear on a podium330.

Under some embodiments of the invention, various visual cues are added to each window in order to further indicate its state. For example, windows that are not selected, and thus do not allow application interaction, can be shown with a semi-transparent pane over the extent of the window. Additionally an icon in the form of a padlock can be superimposed over the window to indicate its state.

Under one embodiment of the present invention, the user may only interact directly with an application associated with a window if the window is placed in the primary view associated with the stage and the window is given focus. Thus, in order to interact with a window within a task, the user must first place the task at the stage. Under the embodiment of Table 1, this is easily achieved by clicking on the non-focus task that the user wishes to move to the stage. Based on this clicking, the user interface of the present invention provides an animated display showing the removal of the current task from the stage and its replacement by the selected task. Selected frames from such an animation are shown inFIGS. 13A through 13E.

FIG. 13Ashows an initial state of the user interface display showing a current task400having a primary viewing window402and two loose stack windows404and406. The initial display ofFIG. 13Aalso includes a selected task408, which is the task the user has “clicked” on to move to the stage.

After the user selects task408, the user interface generates a “snapshot” of current task400. The snapshot of current task400is an image showing the appearance of task400from the home viewing area before task408was selected.

To produce this snap shot while maintaining the image of the gallery provided to the user, some embodiments of the invention utilize two image buffers. Most often, these embodiments change the typical operation of two image buffers that are already present in most three-dimensional rendering systems. During normal operation, one of these buffers, known as the back buffer, is being filled with image data while the other buffer is being accessed by the display driver to generate the display. The data filling the back buffer represents the appearance of the gallery from the user's next position in the gallery. When the back buffer is full, the two buffers are swapped such that the current display buffer becomes the new back buffer and the current back buffer becomes the new display buffer. The new back buffer is then cleared and filled with new image data representing the user's next position in the gallery.

This normal operation is changed to create the snap shot. When the user selects a new task, the camera's next position is set to the home viewing area. The image of the task gallery is then rendered from that position and the rendered image data is stored in the back buffer. Without swapping the two buffers, the data in the back buffer is read out into a separate memory location that holds the snap shot. The back buffer is then cleared and the position of the camera is reset to its previous position. Normal operation of the buffers is then restored. During this operation, the display buffer is accessed to produce the display, so the user is unaware of the temporary change in the camera position.

Once generated, the snapshot is displayed on a stand as shown inFIG. 13Bwhere a task image410has been generated over the stage. After task image410has been generated, task image410begins to move away from the stage. In one embodiment, task image410moves toward its last location in the task gallery before it was selected to move to stage217. In some embodiments, this last location is marked by a stand, such as stand412, that supports a “dimmed” or “faded” image of the task as it appeared before it was moved to the stage. In other embodiments, the location is not visibly marked on the display.

At the same time, task image409of selected task408begins to move toward stage217while stand411of selected task408and a faded version of task image409remain in place along the right side wall.FIG. 13Cshows one frame of the display during the animated movement of both task image410and selected task408.

In some embodiments, various visual cues are placed around the border of the selected task to indicate that it is selected. These can include a border, brighter background image, or additional textual cues.

As task image410moves from the stage, its associated task object is removed from the stage container object and is placed in the left side wall container object. In one embodiment, this occurs as soon as task image410moves far enough left in the animation to be considered moving along the left side wall.

InFIG. 13D, task image410has returned to its previous position in the task gallery and selected task image409is positioned over stage217. When task image409reaches stage217, the task object associated with task image409is removed from the side wall container it had been in and is placed in the stage container. When task image409is placed in the stage container, under one embodiment, a background image that is shown behind the windows in task image409is expanded to fill all of end wall216. The windows within task image409are then redrawn using current data from the windows' associated applications. InFIG. 13E, this means that windows414,416and418of selected task408are redrawn with the size and location of the windows determined by values stored for those windows when selected task408was last moved from stage217to the task gallery.

Switching Tasks Using a Menu

In many embodiments of the invention, users may also switch between tasks using a pop-up menu. Such a technique is shown inFIGS. 14A through 14F. InFIG. 14A, the user has invoked a pop-up window420that provides a “switch task” command. Although only the “switch task” command is shown inFIG. 14A, those skilled in the art will recognize that other commands can also be present above and/or below the “switch task” command. A secondary pop-up window422that provides a list of tasks available in the task gallery is shown displayed to the right of pop-up window420. The user may select one of the available tasks by manipulating an input device such as the keyboard or mouse. Note that inFIG. 14A, the virtual user is in the home viewing area, which is centered in front of stage217and end wall216.

After the user has selected a task from secondary pop-up window422, the user interface generates an animation that gives the appearance that the user is moving backward through the task gallery. This movement continues until the user is far enough back that the selected task and the dimmed version of the former current task are fully in view. InFIG. 14B, the task selected by the user is shown as selected task424. Although not necessary to the practice of the present invention, this automatic movement allows the user to see an animated switch of the tasks so that the user has a better understanding of which task has actually been selected. In one embodiment, the automatic movement of the user can be over-ridden by the user through a user preference.

InFIG. 14C, the user interface generates a “snapshot” of the current task and produces task image426from that “snapshot”. Task image426then begins to move toward a stand427at its previous location in the task gallery. At the same time, task image425of selected task424begins to move toward stage217.FIG. 14Dshows one frame during the middle of this animated motion.

As task image426moves, its associated object is removed from the stage container object and is placed in the left side wall container object.

When task image426has returned to its original location and selected task424has moved to stage217, as shown inFIG. 14D, the object associated with selected task424is removed from the right side wall container object and is placed into the stage container object. The display then regenerates each window in selected task424above stage217. In some embodiments, the virtual user is then returned to the home viewing area.

Virtual User Movement

In the embodiment of the present invention associated with the input controls of Table 1, the user may move through the task gallery using a pointing device to indicate the direction and duration of each movement. Alternatively or in addition to the direct movement, the user may initiate movements to fixed positions within the task gallery. To facilitate such movement, the task gallery is divided into rooms with one or more user positions within each room. By using a single key stroke, the user may advance forward one room or backward one room. In addition, by using a dedicated key or dedicated combination of keys, the user may move directly from any location within the task gallery to the home viewing area in front of stage217.

These embodiments of the invention provide a high level of control where a single click on an appropriate navigational control (button), causes the virtual user to move swiftly but smoothly from their current location to a new desired location. In other words, a discrete action results in transportation of the virtual user to commonly used and useful locations. This avoids problems of hand-eye coordination and the need for well-developed spatialization skills.

FIGS. 15A through 15Dshow an animated motion from a remote location in the task gallery to the home viewing area. Specifically, inFIG. 15A, the user is located in the second room of the task gallery. The user then initiates the command to move to the home viewing area.FIGS. 15B and 15Cshow selected frames in the animated movement towards stage217andFIG. 15Dshows the view from the home viewing area.

FIG. 16shows another embodiment of the present invention in which a set of movement controls428are displayed in the lower left corner of the three-dimensional environment. The movement controls include a forward arrow control429, a backward arrow control431, a home viewing area control433, an overview control435, an up glance control437, a down glance control439, a left glance control441, a right glance control443and a human FIG.445. Although the appearance of the buttons and icons inFIG. 16are found in several embodiments of the invention, different designs for the appearance of the buttons and icons can be used depending on the intended experience level of the user.

By placing the cursor over a control and depressing a button on the mouse or keyboard, a user can select the control and cause the user to move through the environment or change the direction of their view of the environment. For instance, selecting forward arrow control429causes the user to move forward one room in the environment and selecting backward arrow control431causes the user to move backward one room. Selecting home viewing area control433causes the user to move to the home viewing area. Selecting overview control435causes the user to move to the back of the task gallery so that the entire task gallery is visible. Selecting glancing controls437,439,441, and443is discussed below in connection with glances.

Under one embodiment of the present invention, movement controls428are always present on the screen. In other embodiments, movement controls428are only displayed when the user requests that they be displayed. For example, a touch-sensitive input device can be used to fade in or fade out the human figure. When the user touches the input device, the figure appears, and when the user lets go it vanishes. In still other embodiments, the human figure is always present on the screen but the movement controls only appear when the user places the cursor over the figure. In further embodiments of the invention, pausing the cursor over one of the controls or the human figure generates a tool-tip that describes the function of the control.

Further embodiments of the invention rely on input devices that are optimized for the task of navigation. These include dedicated keys on the keyboard, touch-sensitive pads for direction control, and/or small spring-loaded levers with sensors to control the primary locomotion interactions.

The Focus Task

FIG. 17shows a screen display produced when the user is in the home viewing area in front of stage217. InFIG. 17, a task430is shown that contains a focus window432in the primary viewing area, windows434and436in a loose stack area and windows438and440in an ordered stack area. Although the screen display ofFIG. 17is described in connection with a virtual user placed in a three-dimensional task gallery, the inventive aspects of the screen display discussed below are not limited to such an environment. As such, the inventive aspects of the screen display ofFIG. 17discussed further below may be practiced in an environment that does not include a three-dimensional task gallery such as a simple three-dimensional desktop.

Moving Windows from the Primary View to the Loose Stack

Within the current or focus task, the user may move windows between the primary viewing area, the loose stack, and the ordered stack.FIGS. 18A through 18Dshow selected frames representing the movement of a window from the primary viewing area to the loose stack. InFIG. 18A, the user has placed the cursor over window442, which is located in the primary viewing area. Note that window442has focus inFIG. 18A, and as such, most keyboard and pointing device inputs are provided directly to the application corresponding to the focus window. In order to overcome this default, a combination of keystrokes may be used as the command to move the window from the primary viewing area to the loose stack. For example, in the embodiment associated with Table 1, the user performs a drag up on the window in the primary viewing area while depressing the “alt” key in order to move it to the loose stack. Alternatively, the command for moving a window to the loose stack from the primary viewing area can require that the cursor be positioned in a non-client area (also known as a window decoration area) in order for the command input to be directed away from the application and to the user interface.

Upon receiving the input corresponding to the user's desire to move window442to the loose stack, the user interface begins to push window442back toward a loose stack area450as shown in FIG.18B. When window442reaches loose stack area450, as shown inFIG. 18C, the window object associated with window442is removed from the primary viewing container and placed into the loose stack container. Since windows in the loose stack have stands that connect the windows to the floor, a stand is then drawn below window442as shown in FIG.18D.

Moving Windows from the Ordered Stack to the Loose Stack

FIGS. 19A through 19Cshow selected frames of an animation produced by an embodiment of the present invention to show the movement of a window454from an ordered stack456to a loose stack458. InFIG. 19A, the user has positioned a cursor460over window454. With the cursor positioned over window454, the user provides input corresponding to a desire to move window454to loose stack458. In the embodiment of Table 1 this input is a drag to the right. In other embodiments, any dragging operation from the ordered stack toward the loose stack will be interpreted as a command to move the selected window from the ordered stack to the loose stack.

When the user interface receives the drag right input, it generates an animated movement of the selected window454that shows window454moving up from the ordered stack456toward loose stack458. In addition, the animation shows the rotation of window454so that the window's orientation matches the orientation of the loose stack windows.FIG. 19Bshows a frame of this animated movement.

InFIG. 19C, window454is positioned within loose stack458. At this point, the object associated with window454has been removed from the ordered stack container and has been placed in the loose stack container. As such, window454is drawn in the display with a stand460extending from the bottom of window454to the floor. In addition, if the window removed from the ordered stack was not the front window, an animation is invoked to re-position the windows in the ordered stack so that they are a fixed distance apart from each other.

Movement of a Window from the Ordered Stack to the Primary Viewing Area

FIGS. 20A through 20Cshow separate frames of an animation created by the present user interface when the user wishes to replace the window in the primary viewing area with a window on the ordered stack. InFIG. 20A, the user has positioned a cursor462over a window464in an ordered stack466. With the cursor in this position, the user indicates their desire to replace window468of the primary viewing area with window464. In the embodiment of Table 1, the user indicates their desire for this change by clicking a primary button of a pointing device such as a mouse or a track ball.

Upon receiving the “click” input, the user interface simultaneously moves window464up toward the primary viewing area and pushes window468back toward either loose stack470or ordered stack466. In one embodiment, window468is pushed back toward the stack that the window was in before it was moved to the primary viewing area. When window464reaches the primary viewing area and window468reaches loose stack470, the object's associated with these windows are moved into the appropriate container objects. For example, window464is moved from the ordered stack container object into the primary viewing area container object. In addition, window464is identified as the focus window.

Lastly, if the window removed from the ordered stack was not the front window, an animation is invoked to re-position the windows in the ordered stack so that they are a fixed distance apart from each other.

Moving a Window from the Loose Stack to the Ordered Stack

FIGS. 21A through 21Cshow frames from an animation generated when the user indicates that they want to move a window472from a loose stack474to an ordered stack476. In one embodiment, the user indicates that they wish to move a window from the loose stack to the ordered stack by placing a cursor over the window and performing a drag left. In other embodiments, any dragging operation from the loose stack to the vicinity of the ordered stack will be interpreted as a command to move the selected window from the loose stack to the ordered stack.

After receiving the drag left input, the user interface generates an animation in which window472is brought forward toward ordered stack476and is rotated so that it is aligned with the other windows in ordered stack476.FIG. 21Bshows one frame of that animated movement. Before moving window472, stand478ofFIG. 21Ais removed from the bottom of window472. When window472reaches ordered stack476, the object associated with window472is removed from the loose stack container object and is placed in the ordered stack container object.

Moving a Window from the Loose Stack to the Primary Viewing Area

FIGS. 22A through 22Cshow selected frames from an animation generated by the present interface when the user wishes to replace a window484in the primary viewing area with a window480from a loose stack482. In the embodiment of Table 1, the user initiates this movement by clicking on window480. Based on this input, the user interface generates an animation in which window480is brought forward from loose stack482to the primary viewing area and window484, which is in the primary viewing area, is moved back to either the loose stack or the ordered stack depending on where it was before being placed in the primary viewing area. For the purposes ofFIGS. 22A through 22C, window484was in loose stack482before being moved to the primary viewing area.

During the animation, the object associated with window480is removed from the loose stack container object. This causes stand486to disappear so that window480appears unsupported. At the same time, the object associated with window484is removed from the primary viewing container and placed into the loose stack container. When the object associated with window484is placed in the loose stack container object, a stand appears below window484.

Moving Windows from the Primary Viewing Area to the Ordered Stack

FIGS. 23A through 23Cshow selected frames from an animation created by an embodiment of the present user interface when the user indicates that they wish to move a window490from the primary viewing area to ordered stack492. In one embodiment, the user indicates that they want to move window490to ordered stack492by performing a drag left while the “alt” key is depressed and the cursor is positioned over window490.

Under this embodiment, when the user interface receives a drag left and “alt” key input while the cursor is positioned over window490, the user interface initiates an animation in which window490is pushed backward and rotated slightly to align itself with ordered stack492as shown in FIG.23B. When window490reaches ordered stack492, the object associated with window490is placed in the ordered stack container object and is removed from the primary viewing area object. The end result of this animation is shown in the frame of FIG.23C.

Moving Objects within the Loose Stack

Windows within the loose stack inherit movement properties from the loose stack container object that allow the user to reposition the windows freely within the loose stack. In one embodiment, there are two types of possible movement for a window within the loose stack. First, the window may be moved laterally or vertically within the loose stack as shown inFIGS. 24A through 24Cwhere window500in loose stack502is moved by the user from an initial position shown inFIG. 24Ato a second position shown in FIG.24B and finally to a third position as shown in FIG.24C. In the movement from the initial position ofFIG. 24Ato the second position ofFIG. 24B, the user mostly moves the window laterally to the right. In the second motion, from the second position ofFIG. 24Bto the third position of24C, the user moves window500downward and to the left. Note that as window500is moved, a stand504located below window500is adjusted so that it remains below window500and has the appropriate size to connect window500to the floor.

In the embodiment of Table 1, the movement shown inFIGS. 24A through 24Cis accomplished by the user by placing the cursor over window500and performing a drag operation with the “alt” key depressed.

Windows within the loose stack may also be moved forward and backward within the loose stack.FIGS. 25A through 25Cshow the movement of a loose stack window506first to the front of the loose stack and then to the back of the loose stack. Thus, inFIG. 25A, window506is shown initially positioned between windows508and510of loose stack512. InFIG. 25B, window506has been brought to the front of loose stack512and is now in front of window508. InFIG. 25C, window506has been placed at the back of the loose stack behind both window510and window508.

In the embodiment of Table 1, the user indicates that they wish to pull a loose stack window to the front of the loose stack by performing a drag down. To push a window back in the loose stack, the user performs a drag up operation.

Movement within the Ordered Stack

Under the present invention, a user can also reorganize the order of windows in an ordered stack. Although the user can change the order of the windows, the precise locations of the windows are determined by the user interface.

For example, inFIGS. 26A through 26F, the user reorders an ordered stack514that contains windows516,518and520. In the initial display shown inFIG. 26A, window518is shown between windows516and520in ordered stack514. By selecting window516, the user is able to drag window516upward as shown in FIG.26B and forward of window520as shown in FIG.26C.

Since the user interface automatically repositions windows in the ordered stack, the user may release window518outside of the ordered stack as shown inFIG. 26D, where cursor522has been moved from window518after the user has released the primary button of the pointing device.

When the user releases window518, windows518and520begin to move. Specifically, window520moves backward in ordered stack514to assume the position that window518originally had in ordered stack514. At the same time, window518moves downward and back toward ordered stack514. When the movement is complete, window518occupies the space that window520occupied initially in FIG.26A. Its final resting position is shown in FIG.26F. Thus, the user is able to reorganize ordered stack514without having to expend unnecessary energy in realigning the windows within ordered stack514.

Movement Using Icon Control

Under an alternative embodiment, windows in the primary task may also be moved by using a set of selectable button icons such as buttons524of FIG.27. In one embodiment, buttons524appear on top of a window when a cursor crosses into the window. The buttons persist above the window so that the user may reposition the cursor over one of the buttons. By clicking on one of the buttons, or by dragging one of the buttons, the user is then able to move the selected window in any of the manners described above.

For example, a user can move a window in the primary viewing area to the loose stack by clicking loose stack button526of buttons524.FIGS. 28A through 28Dshow selected frames of an animation created by an embodiment of the present invention showing the movement of a Window550from a primary viewing area to a loose stack552using a set of buttons554. InFIG. 28A, button icons554have been generated by the user interface above window550based on the location of a cursor556within the window550. The user has moved the cursor556over to “loose-stack” button554and has clicked on that button. InFIG. 28B, window550has been pushed backward toward loose stack552. InFIG. 28C, window550has reached loose stack552and inFIG. 28Da stand has appeared below window550.

Loose stack button526may also be used to move a window from an ordered stack to the loose stack as shown inFIGS. 29A through 29C. InFIG. 29A, the user has caused button icons560to appear above window562in ordered stack564by placing the cursor in window562. The user has then positioned the cursor over loose stack button566of button icons560. By clicking on loose button566, the user initiates an animation in which window562moves to loose stack568.FIG. 29Bshows one frame during that animated motion andFIG. 29Cshows window562in its final position in loose stack568.

Button icons524ofFIG. 27also include a primary view button528, which is used to replace the current window in the primary view with a selected window.FIGS. 30A through 30Cshow the use of a primary view button570to replace a window572in the primary view with a window574from an ordered stack576. InFIG. 30A, button icons578have been generated when the user moved the cursor over window574. The user has then moved the cursor over the primary view button570. When the user clicks on primary view button570, window572in the primary viewing area begins to move back toward loose stack580while window574moves forward. At the end of the movement, window572is located in loose stack580and window574is located in the primary viewing area.

Primary view button528ofFIG. 27can also be used to move a window from a loose stack to the primary view.FIGS. 31A through 31Cshow selected frames of an animation depicting such an event. In particular,FIG. 31Ashows a cursor590placed over a primary view button592of button icons594. Button icons594were generated by the user interface in response to cursor590being positioned over loose stack window596.

When the user clicks on primary view button592, window596moves forward and current window598moves back toward the loose stack.FIG. 31Bshows a frame during a portion of this movement.FIG. 31Cshows the final orientation of windows596and598.

A user can add additional windows to the primary viewing area without removing existing windows from the primary viewing area by using add-to-selection button536of FIG.27. When the user selects this button for a window in the loose stack or the ordered stack, the window moves to the primary viewing area and the existing windows in the primary viewing area are moved to accommodate the new window. In one embodiment, the windows in the primary viewing area are positioned so that they appear to be the same size as discussed further below.

Button icons524ofFIG. 27also include an ordered stack button530that can be used to move windows from the primary viewing area to the ordered stack and from the loose stack to the ordered stack.FIGS. 32A through 32Bshow selected frames of movement of a window600from the loose stack to the ordered stack. The movement of window600is initiated by the user clicking on ordered stack button602of button icons604.FIGS. 33A through 33Cshow the movement of a window606from the primary viewing area to ordered stack608when the user clicks on ordered stack button610of button icons612.

Button icons524ofFIG. 27also include a push back/pull forward button532. As shown in FIGS.34A through34C, the user can use button532to push a window in a loose stack back or pull the window forward in the loose stack. InFIG. 34A, the user has selected push back/pull forward button616of button icons618, which was displayed when the user placed the cursor over loose stack window620. While depressing the primary button on a pointing device, the user can pull loose stack window620forward in the loose stack by moving the pointing device backward. The result of such an operation is shown inFIG. 34B, where loose stack window620is shown at the front of the loose stack. The user may also push loose stack window620to the back of the loose stack by moving the pointing device forward. The result of this operation is shown in FIG.34C.

In an alternative embodiment, push back/pull forward button532ofFIG. 27is divided into an upper selectable arrow531and a lower selectable arrow533. As shown inFIG. 35A, when a window621is located in the middle of a loose stack both the upper selectable arrow and the lower selectable arrow are shown in push back/pull forward button617of button icons619. By positioning the cursor, the user can select either the upper arrow or the lower arrow. If the user selects the upper arrow, window621is pushed to the back of the loose stack as shown in FIG.35C. If the user selects the lower arrow, window621is pulled to the front of the stack as shown in FIG.35B. In one embodiment, the upper arrow and the lower arrow are rendered in three-dimensional perspective such that the upper arrow appears smaller than the lower arrow. This helps to indicate to the user that the upper arrow will push windows to the back and that the lower arrow will pull windows to the front.

When window621is at the front of the stack, the lower arrow is removed from button617as shown in FIG.35B. Similarly, when window621is at the back of the loose stack, the upper arrow is removed from button617as shown in FIG.35C.

Button icons524ofFIG. 27also include a move button534, which the user may use to relocate a window within the loose stack or the ordered stack.FIGS. 36A through 36Cshow movement of a loose stack window624using a location button626of button icons628. InFIG. 36A, the user has selected location button626from button icons628. While depressing a primary button on a pointing device, the user is able to move window624vertically and laterally within the loose stack. As shown inFIG. 36B, the user has moved window624laterally within the loose stack. As shown inFIG. 36C, the user has moved window624down and to the left within the loose stack.

The move button may also be used to provide arbitrary movement in depth while dragging the button. In one specific embodiment, holding the shift key while dragging causes the window to move away from the user and holding the control key while dragging causes the window to move toward the user.

A move button may also be used to reorder windows within an ordered stack as shown inFIGS. 37A through 37F. InFIG. 37A, the user has selected move button630of button icons632. While depressing a primary button on a pointing device, the user can move window634as shown inFIGS. 37B and 37Cby moving the pointing device. InFIG. 37D, the user has released the primary button of the pointing device and moved the cursor away from button630. This in turn has caused button icons632to disappear in FIG.37D.

InFIG. 37E, the user interface automatically moves windows636and634within the ordered stack. As shown inFIG. 37E, this involves moving window636back in the ordered stack and moving window634down toward the ordered stack.FIG. 37Fshows the result of the reordering done by the user and the automatic positioning done by the user interface.

A user may also close a window using a close button537of icons524. When a user clicks on close button537, the window associated with the button icons disappears from the screen along with the button icons.

The order of the button icons shown inFIG. 27represents only a single possible embodiment. Other orders for these buttons are within the scope of the invention. In addition, the buttons may be arranged in other possible layouts within the scope of the present invention. For example, the buttons may be arranged in an arc around one of the corners of the window. This aids the user in consistently and quickly acquiring the buttons for purposes of interaction.

Various embodiments of the present invention also use a variety of strategies for attaching the button icons to a window. In one embodiment, the button row moves in all three dimensions with the window such that when the window moves away from the user, the button row appears to get smaller. In some embodiments, the row of buttons tilts with the window as the window tilts. In further embodiments, the button row tilts as the window tilts but during the tilt operation the buttons are simultaneously resized and rearranged such that each button remains a constant size (in pixels) on the screen and the spacing between the buttons remains constant in pixels.

When an embodiment is used where the row of buttons does not tilt or move forward and back with the window, various visual cues can be used to suggest the association between the row of buttons and the selected window. For example, semi-transparent geometric objects can stretch between the boundary of the row of buttons and the top edge of the selected window. Alternatively, lines may be drawn between each button and an associated location on the selected window. In further embodiments, various combinations of lines and planar objects are used together to further the visual correspondence.

Multiple Windows in the Primary Viewing Area

Under an embodiment of the present invention, multiple windows can be placed in the primary viewing area.FIGS. 38A through 38Jdepict selected frames showing the placement of multiple windows in the primary viewing area. InFIG. 38A, the user has positioned a cursor650over a loose stack window652. The user then indicates that they wish to add window652to the primary viewing area. In the embodiment of Table 1, this is accomplished by depressing the shift key on the keyboard while clicking the primary button of the pointing device. In the pop-up menu embodiment ofFIG. 27, this is accomplished by selecting add window button536.

In response to this input, the user interface of the present invention pushes current focus window654back in the display while bringing loose stack window652forward in the display. A frame from this motion is shown in FIG.38B. As loose stack window652is moved into the primary viewing area, the object associated with window652is removed from the loose stack container object and is placed into the primary view container object. In addition, window652is designated as the focus window in the primary viewing area.

When window652reaches the primary viewing area, it is the same distance from the user as window654with which it shares the primary viewing area. Thus, the user does not have to manipulate the shape or location of either window in order to view both windows in the primary viewing area. The result of moving window652into the primary viewing area is shown in FIG.38C. In other embodiments, the windows are placed at different distances from the user so that the windows appear the same size to the user and so that the windows do not obscure each other. In still, other embodiments, the windows are scaled so that they appear the same size in the primary viewing area. In the context of this application, such scaling can be considered a way of positioning the windows.

More than two windows may be added to the primary view. InFIG. 38Dthe user positions cursor650over an ordered stack window656and indicates that they wish to add that window to the preferred viewing area. Using the embodiment of Table 1, this involves pressing the shift key while clicking the primary button of the pointing device. In the embodiment ofFIG. 27, this involves selecting the add-to-selection button536of button icons524. In response to the user input, the user interface pushes windows652and654back in the display while bringing windows656forward and to the right. A frame from this motion is shown in FIG.37E. InFIG. 38F, it can be seen that each of the windows652,654, and656in the primary viewing area are of generally the same size and shape. The repositioning of the windows is done automatically by the user interface of the present invention so that the user does not have to manipulate these features of the windows in order to view all of the windows in the primary viewing area. In one embodiment, window656is given focus as it is moved into the primary viewing area.

A fourth window may be added to the primary viewing area by selecting an additional window to add to the primary viewing area as shown in FIG.38G. InFIG. 38G, the user has selected a window660to add to the primary viewing area. InFIGS. 38H and 38I, window660is moved forward toward a preferred viewing area defined by windows652,654and656. InFIG. 38Jwindow660reaches its final position within the preferred viewing area and is designated as the focus window.

The present invention is not limited to any particular number of windows that may be added to the primary viewing area. For example, in one embodiment ten windows may be placed in the primary viewing area.

Movement of the Loose Stack and Ordered Stack

In some embodiments, the locations of the ordered stack and/or the loose stack are changed dynamically as windows are moved into and out of the primary viewing area. This movement is designed to keep at least a part of both the loose stack and the ordered stack in view when windows are placed in the primary viewing area.

Embodiments of the present invention utilize a glancing technique to allow the user to look ephemerally to their left and right and up and down. For example, under one embodiment, if the user clicks on left glance control441ofFIG. 16, an animation is started that rotates the camera to the left. The user is then able to see the area to the left of the virtual user. When the camera has been rotated ninety-degrees, the image is held for one second and then a second animation is generated to simulate the rotation of the camera back to the forward position. Similar glancing animations can be invoked to view the spaces to the right, above and below the virtual user by clicking on glancing controls443,437and439respectively. Any one of these glances can be held by clicking and holding on the respective control. When the control is released, the rotation animation toward the forward view is invoked.

In some embodiments, glancing can be used to expose tool spaces that travel with the virtual user in the task gallery. The techniques for generating such tool spaces and for implementing glances to the tool spaces are discussed in detail in a U.S. patent application entitled “A METHOD AND APPARATUS FOR PROVIDING AND ACCESSING HIDDEN TOOL SPACES” filed on even date herewith, assigned to a common assignee and identified.

In summary, a tool space is a container object that contains and displays images of other objects. The tool space container object is different from other container objects described above in that the tool space container object travels with the virtual user and can be seen by using a glancing technique or by activating a tool space control. In a glancing technique, the camera associated with the virtual user is rotated while the virtual user's body remains in a fixed position. If the virtual user's body is rotated toward the tool space, the tool space rotates with the user such that the user does not see the tool space. To invoke a glance, the user utilizes a glancing gesture, which can involve a combination of keystrokes, a combination of keystrokes and pointing device inputs, just primary pointing device inputs, or the use of a secondary pointing device such as a touch pad. In some embodiments, glancing is invoked using movement controls428of FIG.16. Specifically, glancing controls437,439,441, and443are used to invoke glances up, down, left, and right, respectively.

In other embodiments, the user displays a tool space without performing a glancing gesture. For example, in one embodiment, the user can display a tool space by selecting the hands of the displayedFigure 445in FIG.16. In one such embodiment, the system displays an animation in which the tool space rotates into the user's current view. In such cases, when the user invokes a glance to the left or right they see the left and right side walls but do not see a tool space. The tool space can be dismissed by clicking on the tool space control again or by selecting an object in the tool space. When the tool space is dismissed, an animation is displayed in which the tool space appears to return to the place it originally came from.

Glances to the Three-Dimensional Start Palette

FIGS. 39A through 39Cshow selected frames from an animated glance toward a left tool space. InFIG. 39A, the virtual user is positioned in front of stage217at the home viewing location. Upon receiving the glance gesture, the user interface rotates the view to the left such that windows680and682rotate to the right in the display. As the view rotates left, the left tool space comes into view. In the embodiment ofFIGS. 39A,39B, and39C the left tool space is depicted as a palette684. InFIG. 39C, the rotation is complete so that all of palette684can be seen. In the embodiment ofFIG. 39C, the user's hand is shown holding palette684to give the user a sense of depth perception as to the location of palette684, and to indicate the size of palette684.

Palette684ofFIG. 39Ccontains a number of three-dimensional objects such as objects688and670. Objects670and688may be moved by placing a cursor over the object and using a dragging technique.

In one embodiment, palette684is a data mountain as described in a co-pending U.S. Patent application having Ser. No. 09/152,491, filed on Sep. 14, 1998, and entitled METHODS, APPARATUS AND DATA STRUCTURES FOR PROVIDING A USER INTERFACE, WHICH EXPLOITS SPATIAL MEMORY IN THREE-DIMENSIONS, TO OBJECTS.” In such an embodiment, objects, such as objects670and688are prevented from being moved such that one object obscures another object. In particular, if an object begins to substantially cover another object, the other object moves to the side so that it remains in view.

Selecting an Application from the Three-Dimensional Start Palette

In one embodiment, the objects on a start palette such as palette684represent applications that can run on the same computer that is generating the three-dimensional computer interface of the present invention. By clicking on an object such as object690inFIG. 40A, a user of the present invention can cause the application to begin executing. If the application then opens a window, the present invention will redirect the window that is drawn by the application so that the window appears in the primary viewing area of the current task. The user interface of the present invention then dismisses the tool space either by rotating the tool space out of the user's forward view (non-glancing tool space embodiments) or by rotating the user's view from the side glance (glancing tool space embodiments) back to the primary task so that the user may see the newly opened window.

FIG. 40Bshows the beginning of a rotation back to the primary task from a side glance and FIG.40C shows a return to the full view of the primary task showing newly opened window692which is associated with application690of FIG.40A. Because palette684can include a number of objects representing applications, it serves the function of current two-dimensional Start Menus and favorites. Thus, palette684can be viewed as a three-dimensional Start Menu.

In some embodiments, the user can launch multiple applications during a single viewing of the start palette. In one specific embodiment, the user holds the shift key while selecting individual items. Instead of launching the selected items, the system changes the appearance of the icons to mark the icons as having been selected. When a user clicks on an already marked item, the tool space is dismissed and all of the selected applications are launched.

Although the left tool space has been described in connection with palette684, those skilled in the art will recognize that the tool space can take any shape.

Glancing to the Right Tool Space

In one embodiment, the task gallery also includes a right tool space, which the user can rotate to using a glancing gesture to the right. This causes the rotation of the display as shown inFIGS. 41A,41B and41C.FIG. 41Ashows an initial view of the current task on stage216.FIG. 41Bshows a rotation to the right exposing a portion of a right tool space700.FIG. 41Cshows the complete rotation to the right tool space700.

In the embodiment ofFIG. 41C, right tool space700is a single window, which is generated by a file manager program such as Windows Explorer from Microsoft Corporation. InFIG. 41C, a hand702shown holding a window of tool space700. Hand702gives the user some perspective on the size and position of tool space700relative to their viewpoint. As those skilled in the art will recognize, tool space700can take on many different appearances and the appearance shown inFIG. 41Cis only one example.

In an embodiment in which the right tool space contains a file manager such as the menu provided by Microsoft Windows Explorer, the user may invoke an application or open a document simply by selecting the application or document's entry in the file list.

As shown inFIGS. 42A through 42C, if the user selects an application or document in the file list, the application will be started and if the application has an associated window, the window will be put in the primary viewing area of the current task. For example, inFIG. 42Awhere the user selects an entry704from file manager706, the application associated with that entry is started. The user interface then rotates the view back to the current task as shown inFIGS. 42B and 42Cto expose a window708, which was created by the selected application and redirected to the primary viewing area by the user interface.

Glancing at the Up Tool Space

Embodiments of the present invention can also include an up tool space, which may be accessed by performing an upward glancing gesture.FIGS. 43A through 43Cdepict frames from an animation that is generated when a user performs an upward glancing gesture. Specifically,FIG. 43Ashows an initial view of a current task on stage216. Upon receiving the upward glancing gesture, the user interface rotates the view upward causing the windows of the current task to move downward. As shown inFIG. 43B, this gradually exposes the up tool space until the entire up tool space712becomes visible as shown in FIG.43C.

Glancing at the Down Tool Space

Some embodiments of the invention also include a down tool space, which may be accessed using a downward glancing gesture.FIGS. 44A through 44Cshow frames of an animated rotation downward to expose the down tool space. In particular,FIG. 44Ashows an initial view of a current task on stage216.FIG. 44Bshows a frame from the middle of the downward rotation to the down tool space showing a portion of down tool space714.FIG. 44Cshows the result of the full rotation to the down tool space714.

Down tool space714ofFIG. 44Cincludes an image of shoes716and718meant to depict the virtual shoes of the user in the task gallery. In addition, down tool space714includes two past dialog boxes720and722. Although shoes716and718and dialog boxes720and722are shown in down tool space714, those skilled in the art will recognize that none of these items necessarily need to appear in down tool space714and that other items may be added to down tool space714in place of or in addition to the items shown in FIG.44C.

Movement of Past Dialog Boxes to the Down Tool Space

The present inventors have recognized that in current operating systems, users may dismiss dialog boxes that contain valuable information before they really know what the boxes contain. Unfortunately, once the dialog box is dismissed, the user is not able to recover the text of the box.

To overcome this problem, an embodiment of the present invention stores past dialog boxes in the down tool space. Thus, past dialog boxes720and722inFIG. 44Care examples of dialog boxes that have been dismissed by the user.

In further embodiments of the invention, the user interface generates an animated motion of the dismissed dialog box toward the down tool space to indicate to the user that the dialog box has been moved to this tool space.FIGS. 45A through 45Eprovide selected frames of this animated motion.

InFIG. 45A, a dialog box730is shown in the display. After the user dismisses the dialog box either by hitting enter or by selecting a display button within the dialog box, the user interface creates an animation in which dialog box730slowly drifts to the bottom of the screen as shown inFIGS. 45B,45C, and45D. Eventually, the dialog box drifts completely out of view as shown in FIG.45E. If the user wishes to view the dialog box again, they execute a downward glancing gesture to access the down tool space as described above forFIGS. 44A through 44C.

Under some embodiments, the number or age of the dismissed dialog boxes displayed in the down tool space is controlled by the system. Thus, under one embodiment, dialogue boxes are removed from the down tool space after some period of time. In other embodiments, the oldest dialogue box is removed when a new dialogue box enters the down tool space.

Although the dismissed dialogue boxes are shown drifting to a down tool space, in other embodiments, the dismissed dialogue boxes move to other off-screen tool spaces. In addition, although the placement of dismissed dialogue boxes in a tool space is described in the context of a three-dimensional task gallery, this aspect of the invention may be practiced outside of the task gallery environment.

Movement of a Window from One Task to Another

Under an embodiment of the invention, the user may move a window from one task to another. In one embodiment, the user initiates such a move by invoking a menu using a secondary button on a pointing device. This menu, such as menu732inFIG. 46Aincludes an instruction to move the window. It also provides a secondary menu734that lists the task currently available in the task gallery. By moving the cursor over one of the tasks, and releasing the secondary button of the pointing device, the user can select the destination task for the window.

After the user makes their selection, the menus disappear as shown in FIG.46B and the virtual user is moved back in the task gallery to expose the destination task. InFIG. 46B, the user has selected task736as the destination task. The user interface of this embodiment then removes the stand associated with window738as shown in FIG.46C and moves window738to task736as shown in FIG.46D. Window738is then added to the snapshot of task736as shown in FIG.46E.

In further embodiments of the invention, the current task is replaced by the task that received the moved window. In such embodiments, the user interface provides an animated exchange of the two tasks as described above in connection with switching the current task.

Resizing Windows in the Primary Task

Under embodiments of the present invention, users may resize a window in the primary viewing area of the current task by positioning the cursor on the edge of the window until two resizing arrows, such as resizing arrows740and742ofFIG. 47A, appear. Once resizing arrows740and742appear, the user depresses the primary button on the pointing device and moves the pointing device to establish the new location for the window border. Such border movement is shown inFIG. 47Bwhere border744has been moved to the left with resizing arrows740and742.

The resizing performed under the present invention differs from resizing performed in most two-dimensional window based operating systems. In particular, in most two-dimensional operating systems, window resizing is performed by the application itself. However, under many embodiments of the present invention, window resizing is performed by a three-dimensional shell, which creates the three-dimensional user interface. In particular, the three-dimensional shell defines a three-dimensional polygon on which the image of a window is applied as texture. Thus, upon receiving a resizing instruction, the three-dimensional shell changes the size of the polygon and reapplies the window texturing without conveying to the application that the application's window has been resized. Thus, both the window and the contents of the window are resized together under this technique of the present invention.

Code Block Diagram

The operation of the three-dimensional shell discussed above is more fully described in connection with the block diagram ofFIG. 48which shows the hardware and code modules that are used in the present invention. InFIG. 48, an operating system750such as Windows® 2000 from Microsoft Corporation interacts with a set of applications752and a three-dimensional shell754. Applications752are ignorant of the existence of three-dimensional shell754and are not aware that their associated windows are being displayed in a three-dimensional environment. To accomplish this, operating system750and three-dimensional shell754cooperate to redirect window display data from applications752into the three-dimensional environment. The operating system and three-dimensional shell also cooperate to modify pointing device messages before they are delivered to applications752unless the appropriate circumstances exist in the three-dimensional environment.

The method of generating a three-dimensional interface of the present invention by redirecting the window data generated by applications752is discussed below with reference to the flow diagrams ofFIGS. 49 and 50and the block diagram of FIG.48. The process ofFIG. 49begins with step800in which one of the applications752or the operating system750determines that a window should be repainted on the display. In this context, repainting the window means regenerating the image data corresponding to the appearance of the window on the display.

After it is determined that a window needs to be repainted, the associated application regenerates the display data at a step802. This display data is then sent to operating system750. In operating systems from Microsoft Corporation, the display data is routed to a graphics device interface756(GDI.DLL) within operating system750. Graphics device interface756provides a standardized interface to applications and a specific interface to each of a collection of different types of displays. Graphics device interface756includes a set of drawing contexts758for each window generated by each of the applications752. The drawing contexts758describe the location in memory where the display data is to be stored so that it can be accessed by a display driver.

Under the present invention, instead of directing the display data to a portion of the display memory, graphics device interface756redirects the data to a location in memory denoted as redirect memory760of FIG.48. The redirection of the window data is shown as step804inFIG. 49. Afurther discussion of window redirection can be found in U.S. patent application Ser. No. 09/282,872, filed Mar. 31, 1999 and entitled DYNAMIC EFFECTS FOR COMPUTER DISPLAY WINDOWS.

After graphics device interface756has redirected the window display data, it notifies three-dimensional shell754that certain window data has been updated and provides a pointer to the redirected window display data in redirect memory760. This occurs at step806of FIG.49. At step808, three-dimensional shell754marks the texture map associated with the update window as being “dirty”.

At step810, three-dimensional shell754stores a new polygon for any window that has had its shape changed. The polygon associated with a window determines the location and shape of the window in the three-dimensional display environment. For instance, in most of the screen examples described above, each window is a texture map on a rectangular polygon. By rotating and moving this polygon within the three-dimensional environment, and then applying the associated texture map containing the window data, the present invention can give the appearance of a three-dimensional window moving in the three-dimensional environment.

The images of the task gallery and the windows in the gallery are rendered using a three-dimensional rendering toolkit764such as Direct3D from Microsoft Corporation. Three-dimensional rendering toolkit764is used during an animation loop shown in FIG.50. At step801of this loop, the location of the virtual user and the virtual user's orientation in the task gallery is determined. The task gallery and the non-focus tasks are then rendered at step803based on this user viewpoint. At step805, three-dimensional shell754determines which windows in the focus task are in the current view. At step810three-dimensional shell754determines if any of the visible windows have had their texture map marked as dirty. If one of the visible windows has a “dirty” texture map, the redirected paint data is copied into the window's texture map at step811. The windows are then rendered at step812by applying each windows texture map to its associated polygon.

The rendering produces display data that is stored in a back buffer765of a display memory766. Back buffer765is then swapped with a front buffer767of display memory766so that back buffer765becomes the new front or display buffer765. A display driver768then accesses new display buffer765to generate an image on a display770.

Three-dimensional shell754also receives event notification when an application opens a new window. Such windows include new document windows, dialogue boxes and drop-down menus. Three-dimensional shell754selects a position for the new window based on the position of the window's parent window and the two-dimensional location indicated for the new window. Thus, a pull-down menu is positioned relative to its parent window in the three-dimensional environment so that it is in the same relative location within the parent window as it would be if both windows were in a two-dimensional environment. Likewise, a dialogue box that is designated by the application to appear in the center of the screen is positioned relative to its parent window in the three-dimensional environment.

Redirection of Pointer Device Inputs

In addition to redirecting the window display data created by an application, the present invention also modifies event data generated by a pointing device so that the event data reflects the position of the cursor in the three-dimensional environment relative to redirected windows that are displayed in the environment. These modifications are described with reference to the flow diagram of FIG.51and the block diagram of FIG.48.

In step820ofFIG. 51, a pointing device driver772ofFIG. 48generates a pointer event message based on the movement of a pointing device774. Examples of pointing device774include a touch pad, a mouse, and a track ball. Operating system750receives the pointer event message and in step822determines screen coordinates fox a cursor based on the pointer event message. In operating systems from Microsoft Corporation, the screen coordinates are determined by a dynamic linked library (DLL) shown as USER.DLL776in FIG.51.

In step824, operating system750notifies three-dimensional shell754that a pointing device event has occurred. In most embodiments, this notification is based on an event inspection mechanism (known generally as a low-level hit test hook) that three-dimensional shell754requests. With the hit test hook notification, operating system750includes the screen coordinates of the cursor.

At step832, three-dimensional shell754determines if the cursor is over a redirected window in the focus task that is displayed on the stage. If the cursor is not over a window in the focus task, three-dimensional shell754does not change the event message at step833but instead returns the message to the operating system. The operating system then posts the unchanged message in the event queue for three-dimensional shell, which uses the posted event message as input for changing the three-dimensional environment at step834. For example, if the cursor is over a task located along a side wall, the floor, or the ceiling of the task gallery, three-dimensional shell754may use the pointer event message as an input command for moving the task within the task gallery. Thus, if the user clicks on the task using the pointer device, three-dimensional shell754uses the clicking input as an instruction to make the selected task the focus task.

If the cursor is over a redirected window in the current task at step832, three-dimensional shell754determines the two-dimensional position within the window at a step836. Since windows within the current task can be rotated away from the user, the determination of the two-dimensional coordinates involves translating the coordinates of the cursor on the display first to a three-dimensional position in the virtual three-dimensional environment and then to a two-dimensional point on the surface of the polygon associated with the displayed window.

After calculating the two-dimensional position of cursor on the window, three-dimensional shell754determines if the window under the cursor is in the primary viewing area at step838. If the window under the cursor is not in the primary viewing area, three-dimensional shell754changes the event message by replacing the cursor's screen coordinates with the two-dimensional coordinates of the cursor within the window at step840. Three-dimensional shell754also changes the window handle in the event message so that it points at the window under the cursor and changes the message type to a cursor over message. In other words, if the pointer event message indicates a left button down on the pointer device, three-dimensional shell754would change this information into a cursor over message at step840.

The reason for converting all pointer event messages into cursor over messages at step840is that applications that are not in the primary viewing area cannot receive pointer device input under some embodiments of the present invention. Even so, in many embodiments of the invention, it is considered advantageous to give each application the ability to change the shape of the cursor as the cursor moves over the application window. Thus, although an application does not receive button information when the application's window is not in the primary viewing area, it does receive cursor over information so that it may adjust the shape of the cursor.

If the window is in the primary viewing area at step828, three-dimensional shell754determines if the cursor is in the client area of the window at step842. If the cursor is not in the client area at step842, the process continues at step840where the two-dimensional window coordinates of the cursor are placed in the event message and a window identifier that identifies the window below the cursor is placed in the event message.

After changing the event message at step840, three-dimensional shell754uses the original pointer event message information as input for changing the three-dimensional environment at step834. Thus, if the window is not in the primary viewing area, three-dimensional shell754can use the pointer device message to move a window within the loose stack or ordered stack, or move a window between the loose stack, the ordered stack and the primary view.

If the cursor is in the client area at step842, the pointer event message is changed by changing the cursor coordinates to the two-dimensional coordinates of the cursor over the window in the three-dimensional environment and changing a window identifier so that it identifies the particular window that the cursor is over. Thus, if the original pointer event message indicated that the left button of the pointing device had been clicked and gave the screen coordinates of the cursor during that click, three-dimensional shell754would replace the screen coordinates with the two-dimensional coordinates identified by three-dimensional shell754. This pointer event message is then routed by operating system750to the application associated with the identified window. Under this embodiment of the invention, the pointer event message returned by three-dimensional shell754appears to the application to have come from pointing device driver772. Thus, applications752are ignorant of the fact that three-dimensional shell754exists or that their window is being displayed in a three-dimensional shell.

Although the present invention has been described with reference to particular embodiments, workers skilled in the art will recognize that changes may be made in form and detail without departing from the spirit and scope of the invention. In particular, although the present invention has been described with reference to operating systems from Microsoft Corporation, the components needed will be similar on other operating systems. For example, a computer system that uses the X Window System could be used to implement the present invention. It is noted that for such other systems the X server should run on the same machine as the client applications and the window manager so that bitmap sharing is efficient.