Application sharing user interface improvements

[0001] This application is a divisional of U.S. patent application Ser. No. 10/116,817 entitled “APPLICATION SHARING USER INTERFACE IMPROVEMENTS,” filed on Apr. 5, 2002, which application is hereby incorporated by reference in its entirety.

[0002] This invention relates generally to the technology of application sharing and, more particularly, relates to a system and method for improving a viewer's experience during application sharing.

[0003] As computers and computer networks become more pervasive in the home and workplace, many old methods for performing everyday tasks are being replaced or streamlined through the use of computer networking technology. For example, many employees are now able to have a virtual presence in their workplace by logging into a computer network maintained by their employer. One of the most striking developments in computer networking technology has been the advent of remote collaboration.

[0004] One of the oldest forms of processing data is the meeting or conference, whereby multiple individuals focus their attention on common subject matter to arrive at a joint decision, consensus, or product. Increasingly, such meetings are now taking place virtually over computer networks through the use of application sharing technologies. Such technologies enable a sharing user to share an application with various viewing users. The display produced by the application running on the sharer's computer is made available via a computer network to the viewers' computers. In some cases, the sharer may pass control of the application to a viewer, whereby the viewer's control inputs are then communicated back to the sharer's computer, where the actions associated with the inputs are executed, and the resulting changed display is shared back out to the viewers.

[0005] Although application sharing can play a critical role in maintaining or increasing productivity and cooperation, certain problems with current application sharing systems sometimes create a confusing user experience. For example, a sharing user may simultaneously have on their screen a shared window and an unshared window. In an ideal case, a viewing party, or viewer, sees on their computer display and image of the shared window in whole, and does not see the unshared window or any artifacts caused thereby. However, if the sharing user moves the unshared window in such a way as to partially or wholly occlude the shared window, then the viewing user can no longer see the occluded portion. Furthermore, since the unshared window cannot be shown, the occluded region is often filled in with hash marks or other placeholder imagery. The same situation may occur when an unshared window is generated automatically, such as when a message notification or system window is generated.

[0006] The screen presentation at the viewer's machine in such a situation is often unpleasant to the viewer, and indeed may be quite confusing and discomfiting to the novice user. A system and method are needed whereby the viewer experience of application sharing during periods of whole or partial occlusion is improved over prior systems.

[0007] A novel system and method are described for providing a simple and pleasing viewer experience during application sharing when a shared window is occluded in whole or in part by an unshared window. When an unshared window becomes situated in such a manner as to occlude some or all of a shared window during application sharing, the occluded portion is generated from a prior view taken at a time when the portion in question was not obscured. If the percentage of the shared window that is obscured rises above a threshold value, then the entire shared window view is generated from a prior view, and the viewer is informed in an embodiment of the invention that the sharer has paused the sharing session. In an embodiment, a predetermined amount of time is allowed to transpire in such a situation before the viewer is informed that the sharer has paused the sharing session. In this way, large but temporary occlusions are not conveyed to the viewer, and the predetermined delay is short enough that a noticeable delay in sharing is not created in the viewer's perception.

[0019] Turning to the drawings, wherein like reference numerals refer to like elements, the invention is illustrated as being implemented in a suitable computing environment. Although not required, the invention will be described in the general context of computer-executable instructions, such as program modules, being executed by a personal computer. Generally, program modules include routines, programs, objects, components, data structures, etc. that perform particular tasks or implement particular abstract data types. Moreover, those skilled in the art will appreciate that the invention may be practiced with other computer system configurations, including hand-held devices, multi-processor systems, microprocessor based or programmable consumer electronics, network PCs, minicomputers, mainframe computers, and the like. The invention is primarily for use in a networked environment and may further be practiced in distributed computing environments where tasks are performed by remote processing devices that are linked through a communications network. In a distributed computing environment, program modules may be located in both local and remote memory storage devices.

[0020] FIG. 1 illustrates an example of a suitable computing system environment 100 usable in an implementation of the invention. The computing system environment 100 is only one example of a suitable computing environment and is not intended to suggest any limitation as to the scope of use or functionality of the invention. Neither should the computing environment 100 be interpreted as having any dependency or requirement relating to any one or combination of components illustrated in the exemplary operating environment 100.

[0021] The invention is operational with numerous other general purpose or special purpose computing system environments or configurations. Examples of well known computing systems, environments, and/or configurations that are suitable for use with the invention include, but are not limited to, personal computers, server computers, hand-held or laptop devices, multiprocessor systems, microprocessor-based systems, set top boxes, programmable consumer electronics, network PCs, minicomputers, mainframe computers, distributed computing environments that include any of the above systems or devices, and the like.

[0022] An exemplary system for implementing the invention includes a general-purpose computing device in the form of a computer 110. Components of the computer 110 generally include, but are not limited to, a processing unit 120, a system memory 130, and a system bus 121 that couples various system components including the system memory to the processing unit 120. The system bus 121 may 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. By way of example only, and not limitation, such architectures include Industry Standard Architecture (ISA) bus, Micro Channel Architecture (MCA) bus, Enhanced ISA (EISA) bus, Video Electronics Standards Associate (VESA) local bus, and Peripheral Component Interconnect (PCI) bus also known as Mezzanine bus.

[0023] Computer 110 typically includes a variety of computer readable media. Computer readable media can be any available media that can be accessed by computer 110 and includes both volatile and nonvolatile media, removable and non-removable media. By way of example only, and not limitation, computer readable media may comprise computer storage media and communication media.

[0024] Computer storage media includes volatile and nonvolatile, removable and non-removable media implemented in any method or technology for storage of information such as computer readable instructions, data structures, program modules or other data. Computer storage media includes, but is not limited to, RAM, ROM, EEPROM, flash memory or other memory technology, CD-ROM, digital versatile disks (DVD) or other optical disk storage, magnetic cassettes, magnetic tape, magnetic disk storage or other magnetic storage devices, or any other medium which can be used to store the desired information and which can be accessed by computer 110.

[0025] Communication media typically embodies computer readable instructions, data structures, program modules or other data in a modulated data signal such as a carrier wave or other transport mechanism and includes any information delivery media. The term “modulated data signal” means a signal that has one or more of its characteristics (such as, for example, voltage or current level, voltage or current pulse existence or nonexistence, voltage or current pulse width, voltage or current pulse spacing, etc.) set or changed in such a manner as to encode information in the signal. By way of example, and not limitation, communication media includes wired media such as a wired network or direct-wired connection, and wireless media such as acoustic, RF, infrared and other wireless media. Combinations of any of the above are also included within the scope of computer readable media.

[0026] The system memory 130 includes computer storage media in the form of volatile and/or nonvolatile memory such as read only memory (ROM) 131 and random access memory (RAM) 132. A basic input/output system 133 (BIOS), containing the basic routines that help to transfer information between elements within computer 110, such as during start-up, is typically stored in ROM 131. RAM 132 typically contains data and/or program modules that are immediately accessible to and/or presently being operated on by processing unit 120. By way of example, and not limitation, FIG. 1 illustrates RAM 132 as containing operating system 134, application programs 135, other program modules 136, and program data 137.

[0027] The computer 110 may also include other removable/non-removable, volatile/nonvolatile computer storage media. By way of example only, FIG. 1 illustrates a hard disk drive 141 that reads from or writes to non-removable, nonvolatile magnetic media, a magnetic disk drive 151 that reads from or writes to a removable, nonvolatile magnetic disk 152, and an optical disk drive 155 that reads from or writes to a removable, nonvolatile optical disk 156 such as a CD-ROM or other optical media. Other removable/non-removable, volatile/nonvolatile computer storage media that can be used in the exemplary operating environment include, but are not limited to, magnetic tape cassettes, flash memory cards, digital versatile disks, digital video tape, solid state RAM, solid state ROM, and the like. The hard disk drive 141 is typically connected to the system bus 121 through a non-removable memory interface such as interface 140, and magnetic disk drive 151 and optical disk drive 155 are typically connected to the system bus 121 by a removable memory interface, such as interface 150.

[0028] The drives and their associated computer storage media, discussed above and illustrated in FIG. 1, provide storage of computer readable instructions, data structures, program modules and other data for the computer 110. In FIG. 1, for example, hard disk drive 141 is illustrated as storing operating system 144, application programs 145, other program modules 146, and program data 147. Note that these components can either be the same as or different from operating system 134, application programs 135, other program modules 136, and program data 137. Operating system 144, application programs 145, other program modules 146, and program data 147 are given different numbers herein to illustrate that, at a minimum, they are different copies. A user may enter commands and information into the computer 110 through input devices such as a keyboard 162, pointing device 161 (commonly referred to as a mouse), and trackball or touch pad. Other input devices (not shown) may include a microphone, joystick, game pad, satellite dish, scanner, or the like. These and other input devices are often connected to the processing unit 120 through a user input interface 160 that is coupled to the system bus, but may be connected by other interface and bus structures, such as a parallel port, game port or a universal serial bus (USB). A monitor 191 or other type of display device is also connected to the system bus 121 via an interface, such as a video interface 190. In addition to the monitor, computers may also include other peripheral output devices such as speakers 197 and printer 196, which may be connected through an output peripheral interface 195.

[0029] In the implementation of an embodiment of the invention, the computer 110 operates in a networked environment using logical connections to one or more remote computers, such as a remote computer 180. The remote computer 180 may be a personal computer, a router, a network PC, a peer device or other common network node, and in any case the remote computer or computers typically include many or all of the elements described above relative to the personal computer 110, although only a memory storage device 181 has been illustrated in FIG. 1. The logical connections depicted in FIG. 1 include a local area network (LAN) 171 and a wide area network (WAN) 173, but the computer 110 may additionally or alternatively use one or more other networking environments. Networking environments of all types are commonplace in offices, enterprise-wide computer networks, intranets and the Internet.

[0030] The computer 110 should include facilities for accessing the networks to which it is attachable. For example, when used in a LAN networking environment, the personal computer 110 is connected to the LAN 171 through a network interface or adapter 170. Another node on the LAN, such as a proxy server, may be further connected to a WAN such as the Internet. When used in a WAN networking environment, the computer 110 typically includes a modem 172 or other means for establishing communications directly or indirectly over the WAN 173, such as the Internet. The modem 172, which may be internal or external, may be connected to the system bus 121 via the user input interface 160, or other appropriate mechanism. In a networked environment, program modules depicted relative to the personal computer 110, or portions thereof, may be stored in the remote memory storage device. By way of example, and not limitation, FIG. 1 illustrates remote application programs 185 as residing on memory device 181. It will be appreciated that the network connections shown are exemplary and other means of establishing a communications link between the computers may be used. It is not intended to limit the invention to use in a hard-wired network environment, since it may also be used in transiently connected environments, such as for example a wholly or partially wireless network environment interconnected wholly or partially via optical, infrared, and/or radio frequency wireless connections.

[0031] Herein, the invention is described with reference to acts and symbolic representations of operations that are performed by one or more computers, unless indicated otherwise. As such, it will be understood that such acts and operations, which are at times referred to as being computer-executed, include the manipulation by the processing unit of the computer of electrical signals representing data in a structured form. This manipulation transforms the data or maintains it at locations in the memory system of the computer, which reconfigures or otherwise alters the operation of the computer in a manner well understood by those skilled in the art. The data structures where data is maintained are physical locations of the memory that have particular properties defined by the format of the data. However, while the invention is being described in the foregoing context, it is not meant to be limiting as those of skill in the art will appreciate that various of the acts and operation described hereinafter may also be implemented in hardware.

[0032] FIG. 2 illustrates schematically a networking environment in which the present invention in preferably implemented. The architecture of such a system comprises one or more viewer computers illustrated as computers 201, 203, and 205, connected to a sharer computer 207 via a network 209. Each computer 201, 203, 205, 207 is connected or connectable to the network 209 and hence to the others of computers 201, 203, 205, 207 via network connections 211, 213, 215, and 217. The network connections 211, 213, 215, 217 and computers 201, 203, 205, 207 are as discussed above more generally with respect to FIG. 1. The network may be of any type, including, for example, a LAN, such as found in an office, university or other setting, a WAN such as the Internet, a MAN, or any other tangible or intangible, fixed or transient mechanism for computer interconnectivity. While higher data transfer rates are generally preferable to lower data transfer rates, there is no limit or requirement as to the speed of the network 209. In addition, the network 209 may be a single network, or alternatively may be comprised of multiple networks of the same or different types and/or speeds. It will be understood that in many but not all cases, the network will further comprise routers, servers, and/or other computing devices in addition to the endpoint devices 201, 203, 205, 207 involved in the collaborative effort.

[0033] Specific exemplary architectures of the sharer computer 207 and a viewer computer 201 are illustrated in greater detail schematically in FIG. 3. It will be understood that although only one viewer computer is illustrated in FIG. 3, there can be more than one such computer in an implementation of the invention, as illustrated by way of FIG. 2. Sharer computer 307 is illustrated as being connected via networking connection 319 to viewer computer 301. As will be appreciated by those of skill in the art, network connection 319 can include some or all of the network types and network connections discussed above, as well as other network types and connections alternatively or additionally.

[0034] One or more user mode processes of interest 321 are running on sharer computer 307. Such processes include processes, such as a programs, from which information is being shared to one or more viewers such as viewer 307. The processes of interest 321 will be referred to hereinafter as shared processes, with the understanding that the information generated by the processes 321 need not be shared completely. That is, the information shared may consist of a subset of the information generated by such a process 321. Many shared process can also be used in a non-shared manner. For example, a word processing program may be used by the sharer for non-collaborative document production, and may then be used in a shared manner for group editing of the same or another document. In either mode, the processes 321 and the operating system of the sharer computer 307 perform certain steps. For example, whether or not the process 321 is shared, the output of the process 321 will still generally be output to the graphics display driver of the sharer computer 307.

[0035] If the application sharing program 323 is active, such as during a sharing session, then other processes unique to the collaborative setting also take place. In particular, the application sharing program 323, which is communicably linked to the process 321, receives information from the process 321 and transfers information to the process 321. Although the bi-directional flow of information between the process 321 and application sharing program is illustrated by a double arrow, note that the mechanisms for transfer may vary depending upon direction. For example, the process 321 need not even be aware of the presence or operation of the application sharing program 323 for the application sharing program 323 to receive information from the process 321.

[0036] Typically, the application sharing program 323 is communicably linked to an interceptor filter placed in the display path for the process 321. Such a filter may be placed just before the graphics device interface (GDI) or similar interface in such a manner as to read, in a non-intrusive manner, all information sent to the screen of computer 307 by a shared process. In the WINDOWS operating system produced by MICROSOFT of Redmond, Wash., when an application wants to display an object, it calls a GDI function and sends the various parameters for the object. In turn, the GDI sends commands to the screen to cause it to actually paint the object. In contrast, the mechanism for transferring information from the application sharing program 323 to the process 321 need not involve the display path at all, and may instead involve a direct transfer of information.

[0037] Regardless, the application sharing program 323 is also communicably linked to the networking facilities 325 of the sharer computer 307. Such facilities 325 may include any networking communications stack or other protocol arrangement as well as the hardware required for accessing the network connection 319, as discussed above with respect to FIG. 1. Across the network connection 319, a counterpart application sharing program 327 running on the viewer computer 307 is communicably linked to the sharer computer 307 via the network connection 319 and the networking facilities 329 of the viewer computer. The networking facilities 329 may be similar to the networking facilities 325 of the sharer computer. The counterpart application sharing program 327 receives input from shared process 321 via the network connection 319 and also potentially from a user of the viewer computer 301, via one or more input channels 331, such as a keyboard, mouse, etc. as discussed above with respect to FIG. 1. Additionally, the counterpart application sharing program 327 outputs material for display to a display process 333 such as a GDI or similar interface, or other display process. Note that the sharing computer also preferably includes input channels 335 such as those described above for receiving user input, some of which may be directed to and received by the process of interest 321.

[0038] The general operation of the architecture and components illustrated in FIG. 3 will be described briefly in overview before giving a detailed exposition of the processes involved in embodiments of the invention. Initially the shared process 321 is running on sharer machine 307, and is processing one or more documents or files. The user of the sharer machine 307 can begin execution of the application sharing program 323 by selecting an icon on the display screen of machine 307 or otherwise. Preferably, upon prompting by the user either via start-up of the application sharing program 321 or by selection of an option during execution of the application sharing program 321, the user of sharer machine 307 is presented with a list of all sharable documents currently open on machine 307, including those being processed by process 321. The user may select documents to be shared as well as a viewer with whom the documents will be shared.

[0039] The application sharing program 327 resident on the viewer machine 329 should be running before sharing of documents occurs, and may be run in the same manner as described above. At this point, document sharing may occur. That is, of all the documents selected as shared by the user of sharer machine 307, data corresponding to all or some shared windows is transmitted to the viewer computer 301 for display on the screen or display device of that computer 301 in an embodiment of the invention.

[0040] FIG. 4 illustrates two separate views 402, 404 of a sharer display 401 taken at different points in time. In the first view 402, two separate windows 403, 405 appear in their entireties on the sharer display. In this example, one window 405 is shared while the other 403 is unshared. That is, a viewer machine communicably connected to the sharer machine and participating in a sharing session will not display the unshared window 403.

[0041] In the second view 404, the unshared window 403 has been moved so that it is positioned in such a way as to partially occlude shared window 405. It will be appreciated that content in a shared window may be obscured in any number of other ways. For example, using the WINDOWS brand operating system produced by MICROSOFT of Redmond, Wash., a user may strike a key combination to display a system window. For instance, when a user enters the key combination <alt><tab> simultaneously, a system window is generated and sent to the display, showing open windows that the user may wish to shift to. Such a window typically appears at the center of the display. Similarly, other windows may be created in a position that obscures the shared window, rather than being moved into position. For example, many notification windows notifying a user that he or she has mail, that a print job has completed, and so forth, are created in a prominent position on the display in front of whatever material was previously displayed there. Many such windows are short-lived, since they are typically not windows in which a user may stay and work or otherwise manipulate data.

[0042] When a shared window is obscured, as is the case with window 405 in FIG. 4B, a section such as section 407 of the shared window becomes hidden on the sharer's display. Since the hidden portion is no longer painted on the display by the display processing system, there are no longer any paint commands regarding that region to be intercepted and shared with the viewer, even though the viewer is authorized to see such a region since it is part of a shared document. In particular, many operating systems never paint obscured information. For example, The Win32 painting model is that an obscured screen portion simply does not paint, and thus does not produce any GDI painting commands. Thus, for application sharing systems such as NETMEETING by MICROSOFT that intercept GDI paint commands, or similar commands or instructions, to recreate a display for an application sharing viewer, there is no longer any convenient way to know what lies in an obscured region.

[0043] FIG. 5 shows the viewer experience in prior application sharing systems in the situation where a shared window is obscured. In particular, the first display view 502 shows the viewer display at a time when the shared window 505, corresponding to window 405, is not obscured on the sharer's display. This corresponds to the case illustrated in view 402 of FIG. 4A. As can be seen, the shared window 405 is in full view as window 505, while the unshared window 403 does not appear at all, since it is by definition not to be shared.

[0044] Display view 504 of FIG. 5B illustrates the prior viewer experience when an unshared window such as window 403 is positioned in front of the shared window 405 on the sharer's display. In particular, the viewer display shows the unobscured portions of the shared window 505, while filling the area 507 corresponding to the obscured portion with a place-keeper such as hash marks 509. This type of solution may disorient and confuse novice or infrequent users of the application sharing technology.

[0045] FIGS. 6 and 7 illustrate techniques for constructing viewer display representations for presenting a region of a shared window corresponding to a region that has been obscured on the sharer display, according to embodiments of the invention. These figures will be discussed below to give an overview according to embodiments of the invention after which the process of display construction will be discussed in greater detail with respect to FIG. 8.

[0046] FIG. 6 illustrates a technique for reconstructing a viewer display when a small portion of a shared window, such as less than about 30% of the window's original area, has become obscured. The shared window representation 604 on viewer display 602 does not contain any apparently obscured regions although the shared window has been partially obscured to a small degree in the sharer region corresponding to reconstructed viewer region 603. An obscuring event may be as illustrated in display 404 of FIG. 4B or otherwise. As can be seen from FIG. 6, the viewer display 602 of the shared window contains shared data in all regions of the window regardless of the obscuring event at the sharer display.

[0047] Memory maps 605 and 607 illustrate the manner in which the viewer display is constructed after a small partial obscuring of a shared window. Maps 605 and 607 may be bitmaps stored in the memory of the viewer computer hosting the viewer display. Map 605 corresponds to the current shared data corresponding to the current sharer view of the shared window. It can be seen that map 605 is not a complete picture of the shared window, but rather contains an obscured region 609 for which no shared data is sent to the viewer computer, due to the obscuring event. In contrast, map 607 corresponds to a partial prior set of shared data associated with the shared window before the obscuring event, and gives a complete picture of the obscured region or any newly obscured region at that prior point in time. Thus, map 605 provides an incomplete but current view of the shared window, while map 607 provides outdated information to complete the viewer display of the shared window.

[0048] To construct the viewer display of the shared window after the obscuring event, different parts of each map 605,607 are combined to yield a seemingly complete view. In particular, since the portion of current map 605 outside of obscured region 609 is current, this portion is used to construct the unobscured region of the viewer display, i.e. region 601. However, since the current map 605 does not contain data corresponding to the obscured region 609, it cannot supply any such data for reconstructing the corresponding region 603 of the viewer display. Therefore, data for this region 603 is gleaned from the corresponding region 611 of the prior map 607.

[0049] Although potential complexities arise by virtue of this approach, they are unlikely, and are somewhat mitigated by the bifurcated nature of the system as will be explained by reference to FIG. 7 below. For example, since the reconstructed region 603 of the view display is not current data, there is a possibility that the current data in the regions outside of region 603, such as region 601, will become noticeably inconsistent with the data in the reconstructed region 603. This could happen when the sharer scrolls the contents of a partially obscured window where the obscured area is relatively small. In such a case, the viewer will see region 603 remaining static while all other portions of the shared window view scroll.

[0050] It has been empirically observed that the possibility of viewer disruption presented by the technique described above with respect to FIG. 6 is relatively minor. This is because, in general, obscuring events that affect less than 30% of the shared window's original area are caused by the presentation on the sharer display of short-lived windows such as system windows or notification windows. Therefore, the obscured condition will often not persist long enough for bothersome inconsistencies to develop in the viewer display.

[0051] It has been observed that larger obscuring events, such as those that affect more than about 30% of the shared window's original area, are often associated with more long-lived windows, and as such the technique illustrated via FIG. 6 is not optimally suited for reconstructing the viewer display in such cases. In particular, the larger the portion of the viewer display of the shared window that is reconstructed from outdated information, the more noticeable it will become to the viewer that they are not seeing a current view of the shared window. Furthermore, the longer the obscuring condition remains in effect, the more likely it will become that the viewer will notice and be disturbed or distracted by inconsistencies in the viewer display of the shared window. However, note that in a preferred embodiment of the invention, the duration of a small obscuring event is not a factor in deciding how to treat that event. That is, long-lived small obscuring events and short-lived small obscuring events are both treated the same in a preferred embodiment, although such is not required.

[0052] For the above reasons, a different technique for constructing the viewer display of the shared window is used when the obscured portion of the shared window exceeds 30% of the window's original unobscured area, in accordance with an embodiment of the invention. The threshold value of 30% for switching reconstruction modes has been determined to work well, although other thresholds less than or greater than 30% are also within the scope of the invention. For example, a threshold of 10%, 20%, 40%, 50%, 60%, 70%, 80%, or 90% may be used, or any other value that allows a distinction to be made between at least two classes of obscuring events so that such classes may be treated using different techniques. Note that it is also not critical that the same threshold value be used for every type of shared window, but rather the invention also includes the use of a variable threshold adapted to account for application type, sharer display size, or any other consideration.

[0053] With reference to FIG. 7, a reconstruction technique usable in the event of a relatively large obscuring phenomenon according to this embodiment is illustrated. The viewer display 704 presents a representation of a shared window to the viewing user. This discussion assumes that the shared window has been obscured on the sharer display in the region corresponding to region 703 on the viewer display, and the extent of obscuring is substantial, such as, for example, greater than 30% or other threshold value as discussed above.

[0054] In this case, using outdated information from prior displays to fill in the obscured region may result in discomfort or confusion for the viewer due to the extent to which the shared window is obscured and hence outdated. Rather, in this embodiment, the entire shared window representation on the viewer machine is reconstructed using prior display data 705 taken before the occlusion occurred. Thus, all of the shared window representation 702 corresponds to outdated information. To prevent a viewer from coming to the conclusion that the displayed representation of the shared window corresponds to the actual current contents of the shared window, it is desirable in an embodiment of the invention to present a message on the viewer display 704, informing the viewer that the sharing session has been paused by the sharer. In addition, the content of the viewer representation of the shared window may be “washed out” or otherwise modified to indicate a disabled or invalid condition.

[0055] Although the aforementioned technique is based on the observation that phenomena that obscure large portions of a shared window tend to be long-lived, there are situations where a large obscuration occurs for a brief period of time. For example, a sharing user may briefly activate an unshared window in order to copy data, and then switch back to the shared window to paste the data therein. In such situations, it has been observed that it is preferable to freeze the viewer representation of a shared window without presenting a message that the sharing session has been paused, since the obscuring condition soon passes.

[0056] Since there may be no technique for determining in every case beforehand how long a particular obscuring event may last, it is desirable to wait a predetermined amount of time once a large obscuring occurs before presenting the viewer with the message that the viewing session has been paused, and/or washing out the viewer display of the shared window. One reason to use this technique is that since the viewing user cannot see the sharing user, the viewing user cannot tell the difference between an image that is slightly out-of-date and an updated image wherein the sharing user has not made any changes to the shared material. It has been determined that an interval of 5 seconds provides good results in this capacity, however any other amount of delay may be used without departing from the scope of the invention.

[0057] The flow chart of FIG. 8 illustrates a process used in an embodiment of the invention to reconstruct the viewer display of a shared window during application sharing. Initially at node 801, the application sharing process running on the viewer machine awaits new window information from the application sharing process running on the sharer machine. That is, it awaits the arrival of a window list and order packet. When new window data is received, the process transitions to decision 803, where it analyzes the received window data to determine whether a top level shared application window is obscured to any degree by an unshared application window. If it is determined at step 803 that no unshared application window obscures a top level shared application window, then the process flows to step 805. At step 805, the process constructs the viewer display of the shared window using the new window information and returns to step 801 to await further window information.

[0058] If at step 803 it is instead determined that a top level shared application window is obscured to some degree by an unshared application window, then the process continues to step 807, where it is determined whether the amount of the shared application window that is obscured is less than 30% of the original area of the shared application window. Preferably, the degree to which the area of the shared application window is obscured is evaluated in view of the cumulative affects of all obscuring phenomena. That is, an obscuring of 30% or more may occur as a result of separate obscuring events each of which obscures less than 30% of the original area of the shared application window.

[0059] If it is determined at step 807 that the amount of the shared application window that is obscured is less than 30% of the original area of the shared application window, the process flows to step 809, whereat the new display information for the viewer display of the unobscured portion of the shared window is taken from the newly received window information while for the obscured portion of the shared window, the data for painting the corresponding window region on the viewer display is taken from the last prior display data set for painting the shared window on the viewer display wherein that portion of the shared window was not obscured. Once the new display information for the viewer display is created, the process returns to step 801 to await further new window information.

[0060] If at step 807 it is determined that the amount of the shared application window that is obscured is greater than 30% of the original area of the shared application window, the process flows to step 811. At step 811, the process sets a five-second timer and awaits the receipt of new window information showing the shared window to no longer be obscured by greater than 30%. During the five-second delay, the viewer display is constructed according to the most recent viewer display corresponding to an obscured condition of less than 30% rather than the new window data. If the five-second timer expires without the receipt of such window information, then the process flows to step 813, whereat the process washes out the current apparently unobscured viewer display, so that the information therein appears as readable but not currently active. The process also preferably places a notification on the screen, such as in a pop-up window, to inform the viewer that the sharing session has been paused. Washing out may be accomplished by using AlphaBlending functionality as in the WINDOWS operating system produced by MICROSOFT of Redmond, Wash. From step 813, the process returns to step 801 to await new window information. Note that on subsequent re-execution of the logically following steps while the occlusion still exceeds 30%, certain steps are treated differently as appropriate. In particular, since the predetermined delay time has expired already, and the display has been modified accordingly already, if the determination at step 807 is a negative, the process returns to step 801 rather than proceeding to step 811.

[0061] If instead at step 811, when the five-second timer expires, the most recently received window information indicates that the shared window is stilled obscured, but by less than 30%, then the process flows to step 809 and the steps that logically follow. If at step 811 the most recently received window information when the five-second timer expires indicates that the shared window is no longer obscured, the process returns to step 805 and to execute the steps that logically follow.

[0062] With respect to the treatment of window information for purposes of creating the viewer display of a shared window, the following implementation detail variations may be employed, especially if the application sharing session is supported by the WINDOWS operating system. The application sharing program at the viewer machine maintains an off-screen bitmap matched to the sharer's application regions. The application sharing program at the sharer machine sends the application sharing program at the viewer machine a DT_WNDLST packet any time windows are moved or created on the sharer display. The DT_WNDLST packet contains a list of all shared windows and non-shared windows that intersect shared windows on the sharer machine. The list includes information as to the position and shape of each window, as well as an indication of whether the window is shared or not, and the intersections are z-order processed. For example, the lowest z-order window, if shared, is added to the shared region, after which an overlapping non-shared window next in the list may clip the shared region and augment the obscured region. Next, if the following window is shared, it will similarly be used to clip the obscured region and augment the shared region, and so on. The process proceeds in this manner through all windows in the windows list in reverse z-order.

[0063] The application sharing program at the viewer machine calculates an obscured region with respect to a displayed shared window from the received data as described above when each new window list arrives. Subsequently, the application sharing program at the viewer machine subtracts from this calculated obscured region for the window any previously calculated obscured region, yielding the newly obscured region over the previous windows information. The newly obscured region is copied to a “paused” bitmap at the viewer for future use in reconstructing the obscured areas of the window. When the viewer subsequently paints the shared window, it utilizes both the off screen bitmap and the paused bitmap, where appropriate in view of the procedure outlined with reference to FIG. 8, e.g. for minor occlusions.

[0064] All of the references cited herein, including patents, patent applications, and publications, are hereby incorporated in their entireties by reference. That is, each and every part of every such reference is considered to be part of this disclosure, and therefore no part of any such reference is excluded by this statement or by any other statement in this disclosure from being a part of this disclosure.

[0065] In view of the many possible embodiments to which the principles of this invention may be applied, it should be recognized that the embodiments described herein with respect to the drawing figures are meant to be illustrative only and should not be taken as limiting the scope of invention. For example, those of skill in the art will recognize that the elements of the illustrated embodiment shown in software may be implemented in hardware and vice versa or that the illustrated embodiment can be modified in arrangement and detail without departing from the spirit of the invention. Furthermore, although network connections are illustrated herein as lines, no limitation should thereby be imparted to the invention. Network connections may be circuit-switched, packet-switched, or otherwise, and may be transient or permanent, hard-wired or wireless, operating via any suitable protocol. Also note that although embodiments of the invention have been described largely by reference to a sharing program that is separate from the shared process, the sharing program may not be a stand alone program, but may instead be an integral part of the shared process itself, or may be a DLL or other in-process entity.

[0066] Moreover, the exact values of the various time periods and percentages given in the above description are exemplary only, and may be varied without departing from the scope of the invention. Thus, a predetermined delay time usable in the process of FIG. 8 may be two seconds, ten seconds, or any other period, and is not restricted to the period of five seconds used as an example. Furthermore, the dividing line between large and small occlusions should be set to give the best results for a given situation. As such, no limitation is intended in this regard, other than that a mechanism for defining classes of occlusions be provided. Although the foregoing description discusses a bifurcated treatment of classes of occlusions, the number of occlusion classes is not limited to two classes, but may include as many classes as are convenient in each particular implementation. It will understood that although the examples of FIGS. 3, 6, 7, and 8 refer to a sharer and a viewer computer, any number of viewers may be involved, and a viewer may become a sharer and a sharer may become a viewer without limitation. In addition, although the foregoing description gives a number of examples wherein one or more windows obscure another window, no limitation to windows is intended. That is, other types of graphical display objects may obscure and may be obscured, and many of the techniques described herein will be appreciated by those of skill in the art to be applicable to such other objects. Such other graphical objects include but are not limited to non-rectilinear objects such as animated objects rendered on the sharer display.

[0067] Furthermore, references herein to application sharing are not meant to require that all windows or material displayed on a sharer display and associated with a particular application are shared or unshared. Rather, one or more windows associated with an application running on the sharer machine are preferably sharable without requiring the sharing of all windows associated with that instance of that application. Moreover, although the steps employed to construct the viewer display of an occluded shared window are discussed herein with reference to the application sharing program of the viewer computer, such steps may alternatively be executed in whole or in part at the sharer computer.

[0068] Therefore, the invention as described herein contemplates all such embodiments as may come within the scope of the following claims and equivalents thereof.