Window scroll bar

CROSS REFERENCE TO RELATED APPLICATION

[0001] This is a divisional application of pending U.S. patent application Ser. No. 09/276,204, filed Mar. 25, 1999, entitled “WINDOW SCROLL BAR”, which is herein incorporated by reference.

FIELD OF THE INVENTION

[0002] The present invention relates in general to improved information processing systems. In particular, the present invention relates to a method and system for the generation of a window scroll-bar.

BACKGROUND

[0003] Early computer systems were controlled by batch operating systems. These systems had limited interaction with users of the system. An operator needed to load the job to be run and then send the output to a printer. With the advent of time-sharing operating systems, such as the IBM System 370, interactive computing became the norm. Time-sharing operating systems allowed many users to use the computer's resources simultaneously, so that all users appeared to have their own computer system. All users had their own terminal, which was connected to the central computer system. This terminal typically consisted of a display and a keyboard. To the user, this terminal appeared to be an interactive computer system in its own right. the advent of computer systems that allowed truly interactive computer applications came a proliferation of user interfaces. Some of these interfaces were command driven, others where menu driven, but they all allowed the user to work on only one task or application from a given terminal at a time.

[0004] Today, the state-of-the-art for computer systems and user interfaces has advanced beyond the single-task interface. Inexpensive, personal computers and workstations with powerful, graphics processors and multi-tasking, operating systems have changed the way users interact with computer systems. With these operating systems, the user can simultaneously work on many tasks at once, each task being confined to its own display panel, called a window. This interface allows the presentation of multiple windows in potentially-overlapping relationships on a display screen. The user can thus retain a window on the screen while temporarily superimposing a further window entirely or partially overlapping the retained window. This enables users to divert their attention from a first window to one or more secondary windows for assistance and/or reference, so that overall user interaction can be improved. There can be many windows with active applications running at once. As the number of open windows becomes large and the screen becomes cluttered, it becomes more and more difficult for the user to find the desired window because it may be overlaid by several other windows.

[0005] In order to find the desired window, current systems allow the user to reduce overlying windows to icons (symbols that represent the windows) by clicking the mouse button while the mouse cursor is positioned on a minimize button. Reducing a window to an icon is sometimes called “minimization”. This method suffers from the disadvantage that when the window is reduced to an icon, the user cannot see the window contents. Many times when an application in a window is running, the user might wish to see the window contents. By seeing all or a portion of the window contents, the user has a better chance of determining when the application is complete or needs attention.

[0006] In an attempt to address these problems of minimization, some operating systems create a “task bar”, which contains icons for all running tasks. The task bar is always present, regardless of the amount of space that the windows take up on the remaining area of the desktop. The task bar contains icons for all running tasks, regardless of whether the tasks are minimized, maximized, or take up some portion of the desktop. When the user selects an icon in the task bar, the operating system brings that task to the foreground of the desktop. The task bar suffers from the problem that it is an all-or-nothing solution; that is, in order to determine the contents of the window, the user must bring the entire window to the foreground. Further, the user might not be able to determine which is the desired window by examining the icons in the task bar, and thus may repeatedly need to bring different windows to the foreground in order to find the desired window.

[0007] Another method of finding the desired window is for the user to operate the mouse pointer to “grab” overlying windows, “drag” them, and “drop” them to the side or partially off the screen. In this method, the user positions the mouse pointer in some portion of the window (such as the title bar) and clicks and holds a mouse button (the grabbing action). The window then moves with the mouse pointer (the dragging action). When the window is positioned in the desired area, the user releases the mouse button (the dropping action). Grabbing, dragging, and dropping take too much of the user's time and divert the user's attention from the primary work inside the desired window.

[0008] For the foregoing reasons, there is a need for a windowing interface that permits the user to quickly and easily find the window of interest amidst the clutter of the desktop.

SUMMARY OF THE INVENTION

[0009] The invention is a method and system for generating a window scroll-bar. In the preferred embodiment, a controller displays the window scroll-bar on a display screen. The window scroll-bar contains sections associated with respective windows on the display. The window scroll-bar also contains a slider, which moves within a section and between sections. As the slider moves within a particular section, the window associated with that section moves on the display toward the nearest boundary of the display. Thus, by moving the window scroll-bar slider, the user can move overlapping windows out of the way and find the window of interest.

BRIEF DESCRIPTION OF THE DRAWING

[0010]FIG. 1 is a pictorial representation of a computer system that can be utilized to implement a preferred embodiment.

[0011]FIG. 2 is a block diagram of a representative hardware environment of the processing unit of the computer system illustrated in FIG. 1.

[0012]FIG. 3 is a block diagram of software stored within the memory of the computer system depicted in FIG. 1.

[0013]FIGS. 4, 5, <b>6</b>, <b>7</b>, <b>8</b>, <b>9</b>, <b>10</b>, and <b>11</b> are pictorial representations of the interfaces that a user can operate to control the operation of a preferred embodiment.

[0014]FIGS. 12, 13, <b>14</b>, <b>15</b>A, <b>15</b>B, <b>16</b>, <b>17</b>A, <b>17</b>B, <b>18</b>, and <b>19</b> are flowcharts that describe the operation of the preferred embodiment.

DESCRIPTION OF THE PREFERRED EMBODIMENT

[0015] With reference now to the figures and in particular with reference to FIG. 1, there is depicted an embodiment of a computer system that can be utilized to implement the preferred embodiment. Computer system <b>110</b> includes processing unit <b>112</b>, display device <b>114</b>, keyboard <b>116</b>, pointing device <b>118</b>, printer <b>120</b>, and speakers <b>126</b>. Processing unit <b>112</b> receives input data from input devices such as keyboard <b>116</b>, pointing device <b>118</b>, and local area network interfaces (not illustrated) and presents output data to a user via display device <b>114</b>, printer <b>120</b>, and speakers <b>126</b>.

[0016] Keyboard <b>116</b> is that part of computer system <b>110</b> that resembles a typewriter keyboard and that enables a user to control particular aspects of the computer. Because information flows in one direction, from keyboard <b>114</b> to processing unit <b>112</b>, keyboard <b>116</b> functions as an input-only device. Functionally, keyboard <b>116</b> represents half of a complete input/output device, the output half being video display terminal <b>114</b>. Keyboard <b>116</b> includes a standard set of printable characters presented in a “QWERTY” pattern typical of most typewriters. In addition, keyboard <b>116</b> includes a calculator-like numeric keypad at one side. Some of these keys, such as the “control,” “alt,” and “shift” keys can be utilized to change the meaning of another key. Other special keys and combinations of keys can be utilized to control program operations or to move either text or cursor on the display screen of video-display terminal <b>114</b>.

[0017] Video-display terminal <b>114</b> is the visual output of computer system <b>110</b>. As indicated herein, video-display terminal <b>114</b> can be a cathode-ray tube (CRT) based video display well-known in the art of computer hardware. But, with a portable or notebook-based computer, video-display terminal <b>114</b> can be replaced with a liquid crystal display (LCD) based or gas, plasma-based, flat-panel display.

[0018] Pointing device <b>118</b> is preferably utilized in conjunction with a graphical user-interface (GUI) in which hardware components and software objects are controlled through the selection and the manipulation of associated, graphical objects displayed within display device <b>114</b>. Although computer system <b>110</b> is illustrated with a mouse for pointing device <b>118</b>, other graphical-pointing devices such as a graphic tablet, joystick, track ball, touch pad, or track pad could also be utilized. Pointing device <b>118</b> features a casing with a flat bottom that can be gripped by a human hand. Pointing device <b>118</b> can include buttons on the top, a multidirectional-detection device such as a ball on the bottom, and cable <b>129</b> that connects pointing device <b>118</b> to processing unit <b>112</b>.

[0019] To support storage and retrieval of data, processing unit <b>112</b> further includes diskette drive <b>122</b>, hard-disk drive <b>123</b>, and CD-ROM drive <b>124</b>, which are interconnected with other components of processing unit <b>112</b>, and which are further described below under the description for FIG. 2.

[0020] Computer system <b>110</b> can be implemented utilizing any suitable computer such as the IBM Aptiva computer, a product of International Business Machines Corporation, located in Armonk, N.Y. But, a preferred embodiment of the present invention can apply to any hardware configuration that allows the display of windows, regardless of whether the computer system is a complicated, multi-user computing apparatus, a single-user workstation, or a network appliance that does not have non-volatile storage of its own.

[0021] Referring to FIG. 2, there is depicted a block diagram of the principal components of processing unit <b>112</b>. CPU <b>226</b> is connected via system bus <b>234</b> to RAM (Random Access Memory) <b>258</b>, diskette drive <b>122</b>, hard-disk drive <b>123</b>, CD-ROM drive <b>124</b>, keyboard/pointing-device controller <b>284</b>, parallel-port adapter <b>276</b>, network adapter <b>285</b>, display adapter <b>270</b>, and modem <b>287</b>. Although the various components of FIG. 2 are drawn as single entities, each may consist of a plurality of entities and may exist at multiple levels.

[0022] Processing unit <b>112</b> includes central processing unit (CPU) <b>226</b>, which executes instructions. CPU <b>226</b> includes the portion of computer system <b>110</b> that controls the operation of the entire computer system, including executing the arithmetical and logical functions contained in a particular computer program. Although not depicted in FIG. 2, CPU <b>226</b> typically includes a control unit that organizes data and program storage in a computer memory and transfers the data and other information between the various parts of the computer system. CPU <b>226</b> generally includes an arithmetic unit that executes the arithmetical and logical operations, such as addition, comparison, and multiplication. CPU <b>226</b> accesses data and instructions from and stores data to volatile RAM <b>258</b>.

[0023] CPU <b>226</b> can be implemented as one of the 80x86 or Pentium processors, or any other type of processor, which are available from a number of vendors. Although computer system <b>110</b> is shown to contain only a single CPU and a single system bus, the present invention applies equally to computer systems that have multiple CPUs and to computer systems that have multiple buses that each perform different functions in different ways.

[0024] RAM <b>258</b> comprises a number of individual, volatile-memory modules that store segments of operating system and application software while power is supplied to computer system <b>110</b>. The software segments are partitioned into one or more virtual-memory pages that each contain a uniform number of virtual-memory addresses. When the execution of software requires more pages of virtual memory than can be stored within RAM <b>258</b>, pages that are not currently needed are swapped with the required pages, which are stored within non-volatile storage devices <b>122</b> or <b>123</b>. RAM <b>258</b> is a type of memory designed such that the location of data stored in it is independent of the content. Also, any location in RAM <b>258</b> can be accessed directly without needing to start from the beginning.

[0025] Hard-disk drive <b>123</b> and diskette drive <b>122</b> are electromechanical devices that read from and write to disks. The main components of a disk drive are a spindle on which the disk is mounted, a drive motor that spins the disk when the drive is in operation, one or more read/write heads that perform the actual reading and writing, a second motor that positions the read/write heads over the disk, and controller circuitry that synchronizes read/write activities and transfers information to and from computer system <b>110</b>. A disk itself is typically a round, flat piece of flexible plastic (e.g., floppy disk) or inflexible metal (e.g. hard disk) coated with a magnetic material that can be electrically influenced to hold information recorded in digital form. A disk is, in most computers, the primary method for storing data on a permanent or semipermanent basis. Because the magnetic coating of the disk must be protected from damage and contamination, a floppy disk (e.g., 5.25 inch) or micro-floppy disk (e.g., 3.5 inch) is encased in a protective plastic jacket. But, any size of disk could be used. A hard disk, which is very finely machined, is typically enclosed in a rigid case and can be exposed only in a dust free environment.

[0026] Keyboard/pointing-device controller <b>284</b> interfaces processing unit <b>112</b> with keyboard <b>116</b> and graphical-pointing device <b>118</b>. In an alternative embodiment, keyboard <b>116</b> and graphical-pointing device <b>118</b> have separate controllers.

[0027] Display adapter <b>270</b> translates graphics data from CPU <b>226</b> into video signals utilized to drive display device <b>114</b>.

[0028] Finally, processing unit <b>112</b> includes network adapter <b>285</b>, modem <b>287</b>, and parallel-port adapter <b>276</b>, which facilitate communication between computer system <b>110</b> and peripheral devices or other computer systems. Parallel-port adapter <b>276</b> transmits printer-control signals to printer <b>120</b> through a parallel port. Network adapter <b>285</b> connects computer system <b>110</b> to an unillustrated local area network (LAN). A LAN provides a user of computer system <b>110</b> with a means of electronically communicating information, including software, with a remote computer or a network logical-storage device. In addition, a LAN supports distributed processing, which enables computer system <b>110</b> to share a task with other computer systems linked to the LAN.

[0029] Modem <b>287</b> supports communication between computer system <b>110</b> and another computer system over a standard telephone line. Furthermore, through modem <b>287</b>, computer system <b>110</b> can access other sources such as a server, an electronic bulletin board, and the Internet or World Wide Web.

[0030] The configuration depicted in FIG. 1 is but one possible implementation of the components depicted in FIG. 2. Portable computers, laptop computers, and network computers or Internet appliances are other possible configurations. The hardware depicted in FIG. 2 may vary for specific applications. For example, other peripheral devices such as optical-disk media, audio adapters, or chip-programming devices, such as PAL or EPROM programming devices well-known in the art of computer hardware, may be utilized in addition to or in place of the hardware already depicted.

[0031] As will be described in detail below, aspects of the preferred embodiment pertain to specific method steps implementable on computer systems. In an alternative embodiment, the invention may be implemented as a computer program-product for use with a computer system. The programs defining the functions of the preferred embodiment can be delivered to a computer via a variety of signal-bearing media, which include, but are not limited to, (a) information permanently stored on non-writable storage media (e.g., read-only memory devices within a computer such as CD-ROM disks readable by CD-ROM drive <b>124</b>); (b) alterable information stored on writable storage media (e.g., floppy disks within diskette drive <b>122</b> or hard-disk drive <b>123</b>); or (c) information conveyed to a computer by a communications media, such as through a computer or telephone network, including wireless communications. Such signal-bearing media, when carrying computer-readable instructions that direct the functions of the present invention, represent alternative embodiments of the present invention.

[0032] With reference now to FIG. 3, there is illustrated a block-diagram representation of the software configuration of computer system <b>110</b>. As noted above, the software executed by computer system <b>110</b> can be stored within one or more of RAM <b>258</b>, the nonvolatile storage provided by diskette drive <b>122</b>, hard-disk drive <b>123</b>, CD-ROM drive <b>124</b>, or a remote server accessible via modem <b>287</b> or network adapter <b>285</b>.

[0033] As illustrated, the software configuration of computer system <b>110</b> includes operating system <b>390</b>, which is responsible for directing the operation of computer system <b>110</b>. For example, operating systems typically include computer software for controlling the allocation and usage of hardware resources such as memory, CPU time, disk space, and peripheral devices. Other technologies also could be utilized, such as touch-screen technology or human-voice control. The operating system is the foundation upon which applications <b>395</b>, such word-processing, spreadsheet, and web-browser programs are built.

[0034] In accordance with the preferred embodiment, operating system <b>390</b> includes graphical-user-interface (GUI) <b>392</b> manager although they could be packaged separately. GUI <b>392</b> manages the graphical user-interface with which a user of computer system <b>110</b> interacts.

[0035] Operating system <b>390</b> also includes window scroll-bar controller <b>399</b>. Window scroll-bar controller <b>399</b> contains executable instructions <b>312</b> and user profile <b>309</b>. Although window scroll-bar controller <b>399</b> is drawn as being included in operating system <b>390</b>, they could be packaged separately. User profile <b>309</b> contains information that the user can set to direct the operation of window scroll-bar controller <b>399</b>. User profile <b>309</b> is further described below under the description of FIG. 5. Referring again to FIG. 3, CPU <b>226</b> is suitably programmed to carry out the preferred embodiment by executable instructions <b>312</b>, as described in more detail in the flowcharts of FIGS. <b>12</b>-<b>19</b>. In the alternative, the functions of FIGS. <b>12</b>-<b>19</b> could be implemented by control circuitry through the use of logic gates, programmable-logic devices, or other hardware components in lieu of a processor-based system.

[0036] Operating system <b>390</b> communicates with applications <b>395</b> through messages conforming to the syntax of the application-program interface (API) supported by operating system <b>390</b>. Operating system <b>390</b> further communicates with graphical-pointing device-driver <b>396</b>, printer device-driver <b>397</b>, and display-adapter device-driver <b>398</b>. For example, operating system <b>390</b> sends graphics data to display-adapter device-driver <b>398</b>, which in turn translates the messages into bus signals utilized to control display adapter <b>270</b>. In addition, graphical-pointing device-driver <b>396</b> translates signals from pointing device <b>118</b> through keyboard/pointing-device controller <b>284</b> into Cartesian coordinates and a selection status, which are then relayed to GUI manager <b>392</b>. Also, operating system <b>390</b> sends printer-control codes and data to printer device-driver <b>397</b>, which in turn translates the control codes and data into bus signals used to control printer <b>120</b>.

[0037] FIGS. <b>4</b>-<b>11</b> illustrate pictorial representations of the interfaces that are used to control the operations of the preferred embodiment. Referring to FIG. 4, there is shown desktop <b>400</b> displayed on display <b>114</b>. Desktop <b>400</b> includes task bar <b>410</b>, which contains icons <b>411</b>, <b>412</b>, <b>413</b>, <b>414</b>, and <b>415</b>, which correspond to active windows <b>451</b>, <b>452</b>, <b>453</b>, <b>454</b>, and <b>455</b>, respectively. Also contained within desktop <b>400</b> are icons LAN printers <b>420</b> and create-window scroll-bar <b>430</b>. When the user selects create-window scroll-bar <b>430</b> using pointing-device pointer <b>460</b>, controller <b>399</b> displays the dialog shown in FIG. 5, below, and creates a window scroll-bar as further described below in FIGS. <b>6</b>-<b>11</b>, and <b>12</b>.

[0038] Referring to FIG. 5, there is illustrated create-window scroll-bar dialog <b>500</b>, which controller <b>399</b> displays and processes in response to the user selecting create-window scroll-bar <b>430</b>, as previously described above under the description for FIG. 4. Controller <b>399</b> stores the user-selected options described by dialog <b>500</b> in user profile <b>309</b>. Referring again to FIG. 5, dialog <b>500</b> contains proportional-space button <b>510</b>, identify-sections button <b>520</b>, scroll-bar window-order button <b>530</b>, z-order button <b>540</b>, and left-right spatial-representation button <b>550</b>.

[0039] When the user selects button <b>510</b>, controller <b>399</b> creates a window scroll-bar on the desktop such that each displayed window has a section on the scroll bar in proportion to the amount-of-use of the window. When the user selects button <b>520</b>, controller <b>399</b> will identify the scroll-bar sections in the window scroll-bar by either color of the associated window <b>522</b>, title of the associated window <b>524</b>, or by icon of the associated window <b>526</b>.

[0040] When the user selects scroll-bar window-order button <b>530</b>, controller <b>399</b> orders the window sections in the scroll bar by last used <b>532</b>, most used <b>534</b>, most-used-weighted-by-last-used <b>532</b>, order of activation <b>538</b>, or by user choice <b>539</b>. Last used <b>532</b> means that the windows are ordered sequentially on the scroll bar with the window that was used most recently being on the top and the window that was used least recently being on the bottom. Most used <b>534</b> means that windows are ordered on the scroll bar so that the window in which the user spent the most time is positioned at the top of the scroll bar and the window in which the user spent the least time is positioned on the bottom of the scroll bar. Most-used-weighted-by-last-used <b>536</b> means that controller <b>399</b> orders the windows on the scroll bar by balancing those windows near the top of the scroll bar that are most heavily used with those that are last used. Thus, a window that the user peeks at for a small amount of time will get less priority than one that the user spent an hour looking at. But, if the user keeps looking at the window, that window will move above the other, more heavily-used windows on the scroll bar depending on the weights in the priority algorithm used by controller <b>399</b>. Order of activation <b>538</b> means that controller <b>399</b> orders the windows on the scroll bar with the window that the user activated first being placed at the top of the scroll bar and the window that the user activated last being at the bottom of the scroll bar, regardless of when the windows were last used or how heavily the windows were used. Time of “activation” refers to the time that the application associated with the window was started. Alternatively, it could refer to the time that the application was converted from an icon state to a windowed state. User choice <b>539</b> means that the user can order the windows on the window scroll-bar according to the user's preference.

[0041] Z-order tied to window-order <b>540</b> means that controller <b>399</b> will change the z-order of the windows on desktop <b>400</b> to match the order of the window sections in the window scroll-bar. “Z-order” refers to the order of the windows on the Z-axis. In a Cartesian coordinate system, the x-axis is usually thought of as being the horizontal axis, the y-axis is usually thought of as being the vertical axis and the z-axis is usually thought of as being the depth of the display screen. In the example shown in FIG. 4, z-order refers to the order of the windows on the display screen with respect with their relative depth. For example, window <b>451</b> would have the highest order within the z-order since it is displayed on top. Window <b>452</b> would be lower in the z-order, followed by window <b>453</b>, and then by window <b>455</b>. Just from looking at the example in FIG. 4, it is impossible to determine where window <b>454</b> would be positioned in the z-order, although it is surely below windows <b>452</b> and <b>451</b>.

[0042] Left-right spatial representation <b>550</b> means that controller <b>399</b> will create a left-right window scroll-bar, as further described below under the description for FIGS. 9, 10, and <b>11</b>, and FIG. 19.

[0043] Referring to FIG. 6, there is illustrated desktop <b>600</b>, which controller <b>399</b> created in response to the user selecting create window scroll-bar <b>430</b>. Controller <b>399</b> created window scroll-bar <b>605</b>, containing window sections <b>651</b>, <b>652</b>, <b>653</b>, <b>654</b>, and <b>655</b>, corresponding to windows <b>451</b>, <b>452</b>, <b>453</b>, <b>454</b>, and <b>455</b>, respectively. Controller <b>399</b> put the title of each respective window in window scroll-bar section <b>651</b>-<b>655</b> because the user previously selected window title <b>524</b>. Controller <b>399</b> created each of window scroll-bar sections <b>651</b>-<b>655</b> of a different size in proportion to the user's previous use of the window because the user previously selected proportional use <b>510</b>. Window section <b>651</b> is at the top of window scroll-bar <b>605</b> because window <b>451</b> was the last window to be used, and the user previously selected last used <b>532</b>. Window section <b>655</b> is at the bottom of window scroll-bar <b>605</b> because window <b>455</b> was the first window to be used and the user previously selected last used <b>532</b>. Controller <b>399</b> has ordered the other window sections <b>652</b>, <b>653</b>, and <b>654</b> based on their use. Controller <b>399</b> placed slider <b>670</b> at the top of window scroll-bar <b>605</b> and in window section <b>651</b>, which is associated with window <b>451</b>. Reference numerals <b>681</b>, <b>682</b>, <b>683</b>, and <b>684</b> refer to dashed lines that represent the boundaries of window sections <b>651</b>, <b>652</b>, <b>653</b>, <b>654</b>, and <b>655</b> in window scroll-bar <b>605</b>.

[0044] Referring to FIG. 7, in response to the user dragging slider <b>670</b> from the top of window scroll-bar <b>605</b> to its current position in window section <b>655</b>, controller <b>399</b> has moved window <b>451</b> to the lower left-hand corner of desktop <b>600</b>, window <b>452</b> to the upper left-hand corner of desktop <b>600</b>, window <b>453</b> to the upper right-hand comer of desktop <b>600</b>, and window <b>454</b> to the lower right-hand corner of desktop <b>600</b>. Since slider <b>670</b> is positioned in the top of the window scroll-bar section <b>655</b>, window <b>455</b> remains in the same position in desktop <b>600</b> in FIG. 7 as it was in FIG. 6. The operation of controller <b>399</b> in response to the user dragging slider <b>670</b> is further described below under the description for FIGS. 15A, 15B, <b>16</b>, and <b>19</b>.

[0045] Referring to FIG. 8, there is illustrated an embodiment for controller <b>399</b>, in which as the slider moves along window scroll-bar <b>805</b>, controller <b>399</b> gradually fades the next window into view. Thus, in the example shown, slider <b>870</b> straddles boundary <b>884</b> between window scroll-bar sections <b>854</b> and <b>855</b>. In response to this position of slider <b>870</b>, controller <b>399</b> has partially displayed the contents of window <b>864</b> and window <b>865</b>, as illustrated by the dashed lines. The operation of this embodiment of controller <b>399</b> is further described below in the flowcharts of FIGS. 17A, 17B and <b>18</b>.

[0046] Referring to FIGS. 9, 10, and <b>11</b>, there are illustrated examples of the operation of controller <b>399</b> in response to the user selecting left-right spatial representation <b>550</b>. Referring to FIG. 9, controller <b>399</b> has displayed desktop <b>900</b> on display screen <b>114</b>. Desktop <b>900</b> includes window scroll-bar <b>905</b>. Controller <b>399</b> has positioned slider <b>970</b> within window scroll-bar section <b>951</b>, which is associated with window <b>961</b>. Controller <b>399</b> placed slider <b>970</b> within the middle of section <b>951</b> because window <b>961</b> is disposed horizontally in the middle of desktop <b>900</b>. The ratio of width <b>990</b> to width <b>991</b> is proportional to the ratio of width <b>992</b> to width <b>993</b>. Slider <b>970</b> has a width <b>990</b> that is one-quarter the width <b>991</b> of scroll bar <b>905</b> because width <b>992</b> of window <b>961</b> is one-quarter the width <b>993</b> of the displayable area of desktop <b>900</b>. Distance <b>996</b> is the distance from the left edge of window scroll-bar <b>905</b> to the left edge of slider <b>970</b>. Distance <b>997</b> is the distance from the right edge of slider <b>970</b> to the right edge of window scroll-bar <b>905</b>. Distance <b>994</b> is the distance from the left edge of desktop <b>900</b> to the left edge of window <b>961</b>. Distance <b>995</b> is the distance from the right edge of window <b>961</b> to the right edge of the displayable area of desktop <b>900</b>. The ratio of distance <b>996</b> to distance <b>997</b> is proportional to the ratio of distance <b>994</b> to distance <b>995</b>.

[0047] Referring to FIG. 10, controller <b>399</b> has displayed desktop <b>1000</b> and window scrollbar <b>1005</b> on display screen <b>114</b> after the user has moved slider <b>1070</b> into window scroll-bar section <b>1051</b> associated with window <b>1061</b>. Controller <b>399</b> placed slider <b>1070</b> in the right portion of window scroll-bar <b>1005</b> because window <b>1061</b> is disposed horizontally in the right portion of the displayable area of desktop <b>1000</b>. Slider <b>1070</b> has a width <b>1090</b> that is three-quarters the width <b>1091</b> of scroll bar <b>1005</b> because width <b>1092</b> of window <b>1061</b> is three-quarters the width <b>1093</b> of the displayable area of desktop <b>1000</b>. Thus, the ratio of width <b>1090</b> to width <b>1091</b> is proportional to the ratio of width <b>1092</b> to width <b>1093</b>. Distance <b>1096</b> is the distance from the left edge of window scroll-bar <b>1005</b> to the left edge of slider <b>1090</b>. Distance <b>1094</b> is the distance from the left edge of desktop <b>1000</b> to the left edge of window <b>1061</b>. The ratio of distance <b>1096</b> to distance <b>1091</b> is proportional to the ratio of distance <b>1094</b> to distance <b>1093</b>.

[0048] Referring to FIG. 11, controller <b>399</b> has displayed desktop <b>1100</b> and window scrollbar <b>1105</b> on display screen <b>114</b> after the user has moved slider <b>1170</b> into window scroll-bar section <b>1151</b> associated with window <b>1161</b>. Controller <b>399</b> placed slider <b>1171</b> in the left portion of window scroll-bar <b>1105</b> because window <b>1161</b> is disposed horizontally in the left portion of the displayable area of desktop <b>1100</b>. Slider <b>1170</b> has a width <b>1190</b> that is one-half the width <b>1191</b> of scroll-bar <b>1105</b> because width <b>1192</b> of window <b>1161</b> is one-half the width <b>1193</b> of the displayable area of desktop <b>1100</b>. Thus, the ratio of width <b>1190</b> to width <b>1191</b> is proportional to the ratio of width <b>1192</b> to width <b>1193</b>. Distance <b>1197</b> is the distance from the right edge of slider <b>1170</b> to the right edge of window scroll-bar <b>1105</b>. Distance <b>1195</b> is the distance from the right edge of window <b>1161</b> to the right edge of the displayable area of desktop <b>1100</b>. The ratio of distance <b>1197</b> to distance <b>1191</b> is proportional to the ratio of distance <b>1195</b> to distance <b>1193</b>.

[0049] FIGS. <b>12</b>-<b>19</b> are flowcharts that describe the operation of the preferred embodiment. Referring to FIG. 12, there is illustrated an example of the main logic of controller <b>399</b> that creates a window scroll-bar. At block <b>1200</b>, controller <b>399</b> starts. Control then continues to block <b>1202</b> where controller <b>399</b> creates the window scroll-bar on the desktop. Control then continues to block <b>1204</b> where controller <b>399</b> determines whether the user requested that the window sections in the scroll bar be directly proportional to the window use, as shown by button <b>510</b> in FIG. 5. Referring again to FIG. 12, if the determination at block <b>1204</b> is true, then control continues to <b>1206</b> where controller <b>399</b> creates the window scroll-bar sections for each window and gives each window a size on the window scroll-bar proportional to the frequency of window use. Control then continues to block <b>1208</b>.

[0050] If the determination at block <b>1204</b> is false, then control continues directly to block <b>1208</b> where controller <b>399</b> determines whether the user previously requested that the scrollbar window-order be last used as selected by button <b>532</b> in FIG. 5. Referring again to FIG. 12, if the determination at block <b>1208</b> is true, then control continues to block <b>1210</b> where controller <b>399</b> orders the window sections on the scroll bar by the last use of the windows. Control then continues to block <b>1215</b>, as described below. If the determination at block <b>1208</b> is false, then control continues to block <b>1217</b> where controller <b>399</b> determines whether the user has previously selected button <b>534</b> which indicates that the order of the window sections on the scroll bar is to be sorted by most used. If the determination at block <b>1217</b> is true, then control continues to block <b>1219</b> where controller <b>399</b> orders the sections on the scroll bar by frequency of window use. Control then continues to block <b>1215</b>, as described above. Control then continues to block <b>1215</b>, as described below.

[0051] If the determination at block <b>1217</b> is false, then control continues to block <b>1221</b> where controller <b>399</b> determines whether the user requested that the order of the sections on the window scroll-bar be most-used-weighted-by-last-used, as illustrated by button <b>536</b> in FIG. 5. Referring again to FIG. 12, if the determination at block <b>1221</b> is true, then control continues to block <b>1223</b> where controller <b>399</b> orders the window sections on the scroll bar by recency of use balanced by frequency of use. Control then continues to block <b>1215</b>, as described below.

[0052] If the determination at block <b>1221</b> is false, then control continues to block <b>1225</b> where controller <b>399</b> determines whether the user requested that the window sections on the scroll bar be ordered by activation, as illustrated by button <b>538</b> in FIG. 5. Referring again to FIG. 12, if the determination at block <b>1225</b> is true, then control continues to block <b>1227</b> where controller <b>399</b> orders the sections on the window scroll-bar by order of window activation. Control then continues to block <b>1215</b>, as described below.

[0053] If the determination at block <b>1225</b> is false, then control continues to block <b>1229</b> where controller <b>399</b> determines whether the sections on the window scroll-bar are to be ordered by user choice, as indicated by button <b>539</b> in FIG. 5. Referring again to FIG. 12, if the determination at block <b>1229</b> is true, then control continues to block <b>1231</b> where controller <b>399</b> orders the sections on the window scroll-bar by user choice. Control then continues to block <b>1215</b>, as described below.

[0054] If the determination at block <b>1229</b> is false, then control continues directly to block <b>1215</b> where controller <b>399</b> determines whether the user requested that window sections in the scroll bar be identified by window color, as illustrated by button <b>522</b> in FIG. 5. Referring again to FIG. 13, if the determination at block <b>1215</b> is true, then control continues to block <b>1233</b> where controller <b>399</b> paints the respective window sections in the window scroll-bar with the colors of their associated, respective windows. Control then continues to block <b>1235</b>, as described below.

[0055] If the determination at block <b>1215</b> is false, then control continues to block <b>1237</b> where controller <b>399</b> determines whether the user requested that the window scroll-bar sections be identified by window title. If the determination at block <b>1237</b> is true, then control continues to block <b>1239</b> where controller <b>399</b> displays the title associated with the various windows in their respective, window scroll-bar sections. Control then continues to block <b>1235</b>, as described below.

[0056] If the determination at block <b>1237</b> is false, then control continues to block <b>1241</b> where controller <b>399</b> determines whether the user requested that the window scroll-bar sections be identified by window icon, as illustrated by button <b>526</b> in FIG. 5. Referring again to FIG. 13, if the determination at block <b>1241</b> is true, then control continues to block <b>1243</b> where controller <b>399</b> displays the window icons associated with each window in their respective, window scroll-bar section. Control then continues to block <b>1235</b>, as described below.

[0057] If the determination at block <b>1241</b> is false, then control continues directly to block <b>1235</b> where controller <b>399</b> determines whether the user requested that the z-order of the windows in the desktop be tied to the window scroll-bar section order. If the determination at block <b>1235</b> is true, then control continues to block <b>1245</b>. where controller <b>399</b> changes the displayed z-order of the windows in the desktop to match the window scroll-bar section order. Control then continues to block <b>1247</b> where the function returns.

[0058] If the determination at block <b>1235</b> is false, then control continues directly to block <b>1247</b> where the function returns.

[0059] Referring to FIG. 14, there is illustrated a flowchart for a function in controller <b>399</b> that responds to window events that the application running in the window does not handle.

[0060] When the window application receives an event that it does not handle, the window application sends it to a system-supplied routine, which is often called the default window procedure. FIG. 14 illustrates a flowchart for logic to handle events related to the window scroll-bar and would be executed as part of the default window procedure. Referring to block <b>1400</b>, control begins. Control then continues to block <b>1405</b> where controller <b>399</b> determines whether there is an active window scroll-bar. If the determination at block <b>1405</b> is false, then control continues to block <b>1410</b> where controller <b>399</b> performs the standard processing for unknown window events. Control then controller to block <b>1499</b> where the function returns.

[0061] If the determination at block <b>1405</b> is true, then control continues to block <b>1415</b> where controller <b>399</b> determines whether the event received is a “get focus” event. A “get focus” event can be caused by the user requesting that the window that receives the “get focus” event be brought to the foreground and be ready for user interaction. If the determination at block <b>1415</b> is false, then control continues to block <b>1410</b> as previously described above.

[0062] If the determination at block <b>1415</b> is true, then control continues to block <b>1420</b> where controller <b>399</b> sends an “end” event to the logic represented by FIGS. 15 and 16. Control then continues to block <b>1410</b>, as previously described above.

[0063] Referring to FIGS. 15A, 15B and <b>16</b>, there are illustrated flowcharts that respond to events associated with the window scroll-bar. Control begins at block <b>1500</b>. Control then continues to block <b>1502</b> where controller <b>399</b> determines, for each window active on the desktop, which corner of the desktop is closest to that window. Control then continues to block <b>1504</b> where controller <b>399</b> determines, for each window, which comer of the window is farthest from the closest desktop corner. In an alternative embodiment, controller <b>399</b> uses any boundary of the window, which might or might not be a corner of the window. For example, controller <b>399</b> could use the nearest horizontal or vertical boundary, or if the desktop is circular or oval in shape, controller <b>399</b> could determine the nearest edge of the desktop from the window. Control then continues to block <b>1506</b> where controller <b>399</b> positions the slider at the top of the window scroll-bar. Control then continues to block <b>1508</b> where controller <b>399</b> determines the horizontal slider location and size, as described below under the description for FIG. 19. Control then continues to block <b>1510</b> where controller <b>399</b> gets the next event. Control then continues to block <b>1512</b> where controller <b>399</b> determines whether the event is a slider-move event.

[0064] If the determination at block <b>1512</b> is true, then control continues to block <b>1514</b> where controller <b>399</b> determines which window scroll-bar section contains the slider. Control then continues to block <b>1516</b> where controller <b>399</b> moves the window associated with the region determined above in block <b>1514</b> and places the window in proportion from the desktop corner with the distance of the slider to the current section's end. Control then continues to block <b>1518</b> where controller <b>399</b> determines the slider size and horizontal location within the window scroll-bar, as described below under the description for FIG. 19. Referring again to FIG. 15A, control then returns to block <b>1510</b>, as previously described above.

[0065] If the determination at block <b>1512</b> is false, then control continues to block <b>1520</b> where controller <b>399</b> determines whether the event received at block <b>1510</b> is a “tab to next” event. If the determination at block <b>1520</b> is true, then control continues to block <b>1522</b> where controller <b>399</b> determines whether the slider is positioned in the bottom section of the window scroll-bar. If the determination at block <b>1522</b> is true, then control returns to block <b>1510</b>, as previously described above.

[0066] If the determination at block <b>1522</b> is false, then control continues to block <b>1524</b> where controller <b>399</b> positions the slider on the next boundary between window sections in the window scroll-bar. Control then continues to block <b>1526</b> where controller <b>399</b> determines the slider size and horizontal location within the window scroll-bar, as described below under the description for FIG. 19. Referring again to FIG. 15, control then continues to block <b>1528</b> where controller <b>399</b> moves the previous section's window just off the desktop. Control then returns to block <b>1510</b>, as previously described above.

[0067] If the determination at block <b>1520</b> is false, then control continues to block <b>1605</b> in FIG. 16 where controller <b>399</b> determines whether the event retrieved at block <b>1510</b> is an “end” event. An end event would have been sent from the default window procedure previously described above under the description for FIG. 14. Referring again to FIG. 16, if the determination at block <b>1605</b> is true, then control continues to block <b>1610</b> where controller <b>399</b> moves all windows on the desktop back to the original position that they held when the user selected create window scroll-bar icon <b>430</b>. Controller <b>399</b> also removes the window scroll-bar from the display. Control then returns to block <b>1510</b> as previously described above.

[0068] If the determination in block <b>1605</b> is false, the control continues to block <b>1615</b> where controller <b>399</b> performs the standard window processing for the received event. Control then returns to block <b>1510</b>, as previously described above.

[0069] Referring to FIGS. 17A and 17B, there is illustrated a flowchart that describes logic in controller <b>399</b> that processes the window scroll-bar in the embodiment that fades a window in and out of view. At block <b>1700</b>, control begins. Control then continues to block <b>1702</b> where controller <b>399</b> positions the slider at the top of the scroll bar. Control then continues to block <b>1704</b> where controller <b>399</b> retrieves the next event. Control then continues to block <b>1705</b> where controller <b>399</b> initializes the splat-rate variable to one, the shoot-thru variable to zero, and the splatter-adjust variable to zero. Control then continues to block <b>1706</b> where controller <b>399</b> determines whether the event previously retrieved at block <b>1704</b> is a slider-move event.

[0070] If the determination at block <b>1706</b> is true, then control continues to block <b>1708</b> where controller <b>399</b> calculates the percentage of the slider that is in each window scroll-bar section. Control then continues to block <b>1710</b> where controller <b>399</b> blocks subsequent updates from occurring in all desktop areas except for those areas in or above the window whose slider percentage decreased when compared with the previous slider-move event. Control then continues to block <b>1712</b> where controller <b>399</b> calculates a splat rate using the slider percentage and the previous slider percentage of the window whose slider percentage decreased. The splat rate equals the previous slider-percentage minus the current slider-percentage divided by the previous slider-percentage.

[0071] Control then continues to block <b>1714</b> where controller <b>399</b> refreshes every window above (in the z-order) the window whose slider percentage decreased, using the splat rate calculated in block <b>1712</b> above, as further described below under the description for FIG. 18. Thus, the effect of the action of controller <b>399</b> in blocks <b>1710</b>, <b>1712</b>, and <b>1714</b> is to fade out the window whose slider percentage decreased by refreshing the windows on top of it in the z-order. Referring again to FIG. 17B, control then continues to block <b>1716</b> where controller <b>399</b> removes the update block previously established above at block <b>1710</b>.

[0072] Control then continues to block <b>1718</b> where controller <b>399</b> determines whether there exits a window whose slider percentage increased. If the determination of block <b>1718</b> is true, then control continues to block <b>1720</b> where controller <b>399</b> calculates a shoot-through rate and a splatter-adjust rate. The shoot-through rate equals the slider percentage for the window whose slider percentage increased minus the previous slider percentage for the window whose slider percentage increased divided by one minus the previous slider percentage of the window whose slider percentage increased. The splatter adjust rate equals (slider-percentage minus (previous slider-percentage times splat rate)) divided by (one minus (previous slider percentage times splat rate)). Control then continues to block <b>1722</b> where controller <b>399</b> refreshes the window whose slider percentage increased using the calculated shoot-through rate and splatter-adjust rate, as further described below under the description for FIG. 18. Thus, the effect of the action of controller <b>399</b> in blocks <b>1720</b> and <b>1722</b> is to fade in (brighten) the window whose slider percentage increased. Referring again to FIGS. 17A and 17B, control then returns to block <b>1704</b>, as previously described above.

[0073] If the determination at block <b>1718</b> is false, then control continues directly to block <b>1704</b>, as previously described above.

[0074] If the determination at block <b>1706</b> is false, then control continues to block <b>1724</b> where controller <b>399</b> determines whether the received event is an “end” event. If the determination at block <b>1724</b> is true, then control continues to block <b>1726</b> where controller <b>399</b> sends a normal refresh event to all windows in the desktop, as further described below under the description for FIG. 18. Referring again to FIG. 17A, control then continues to block <b>1727</b> where controller <b>399</b> removes the window scroll-bar from the display. Control then continues to block <b>1728</b> where the function returns.

[0075] If the determination at block <b>1724</b> is false, then control continues to block <b>1730</b> where controller <b>399</b> performs normal event processing for the received event. Control then returns to block <b>1704</b> as previously described above.

[0076] Referring to FIG. 18, there is illustrated a flow chart showing sample logic for a function and controller <b>399</b> that refreshes a window on the desktop. The splattering action previously described above under the description for FIG. 17B has as its purpose to fade a window. The window being refreshed, as described in FIG. 18, is not the one being faded, but is the one being used to fade the window below it. At block <b>1800</b> control starts. Control then continues to block <b>1802</b> where controller <b>399</b> enters a loop for every pixel in the window. When there are no more pixels to process, control continues to block <b>1899</b> where the function returns.

[0077] As long as there are pixels in the window to process, the loop continues from block <b>1802</b> to block <b>1805</b> where controller <b>399</b> retrieves a random number between 0 and 1. Control then continues to block <b>1810</b> where controller <b>399</b> determines whether the pixel to be written is in a blocked region. (A region can be blocked as previously described above in blocks <b>1710</b> of FIG. 17B. A region can also be blocked if it is below another window in the z-order.) Referring again FIG. 18, if the determination at block <b>1810</b> is true, then control continues to block <b>1815</b> where controller <b>399</b> determines whether the blocked region was previously splattered, which would have occurred when a different invocation of the logic of FIG. 18 was called from block <b>1714</b>, as previously described above under the description for FIG. 17B. Referring again to FIG. 18, if the determination at block <b>1815</b> is true, then control continues to block <b>1820</b> where controller <b>399</b> determines whether the retrieved random number is less than the splatter-adjust rate. (The splatter-adjust rate was previously calculated at block <b>1720</b> in FIG. 17B and is used to brighten regions that were inadvertently faded by splattering.) Referring again to FIG. 18, if the determination at block <b>1820</b> is false, then control returns to block <b>1802</b>, as previously described above.

[0078] If the determination at block <b>1820</b> is true, then control continues to block <b>1840</b> where controller <b>399</b> sets the pixel. Control then returns to block <b>1802</b>, as previously described above.

[0079] If the determination at block <b>1815</b> is false, then control continues to block <b>1830</b> where controller <b>399</b> determines whether the random number is less than the shoot-through percentage. (The shoot-through percentage was previously calculated above at block <b>1720</b> in FIG. 17B.) Referring again to FIG. 18, if the determination at block <b>1830</b> is false, then control returns to block <b>1802</b>, as previously described above.

[0080] If the determination at block <b>1830</b> is true, then control continues to block <b>1825</b> where the pixel is set. Control then returns to block <b>1802</b>, as previously described above.

[0081] If the determination at block <b>1810</b> is false, then control continues to block <b>1835</b> where controller <b>399</b> determines whether the random number retrieved is less than the splat rate. (The splat rate was previously calculated above under the description for block <b>1712</b> in FIG. 17B.) If the determination at block <b>1835</b> is true, then control continues to block <b>1825</b> where controller <b>399</b> sets the pixel. Control then returns to block <b>1802</b>, as previously described above. If the determination at block <b>1835</b> is false, then control returns directly to block <b>1802</b>, as previously described above.

[0082] Referring to FIG. 19, there is illustrated a flow chart depicting sample logic that determines the slider size and horizontal location. At block <b>1900</b>, control begins. Control then continues to block <b>1905</b> where controller <b>399</b> determines whether the user previously selected width view, as previously described above by button <b>550</b> in FIG. 5. Referring again to FIG. 19, if the determination of block <b>1905</b> is false, then control continues to block <b>1910</b> where controller <b>399</b> displays a standard slider on the window scroll-bar. Control then continues to block <b>1999</b> where the function returns.

[0083] If the determination at block <b>1905</b> is true, then control continues to block <b>1915</b> where controller <b>399</b> calculates the width of the slider in proportion to the width of the window associated with the window scroll-bar section that the slider is in. Control then continues to block <b>1920</b> where controller <b>399</b> calculates the horizontal position of the slider within the window scroll-bar in proportion to the horizontal position of the associated window within the displayable area of the desktop. Control then continues to block <b>1925</b> where controller <b>399</b> displays the slider with the calculated size and the calculated horizontal location within the window scroll-bar. Control then continues to block <b>1999</b> where the function returns. The operation of the logic of FIG. 19 was previously described above under the description for FIGS. 9, 10, and <b>11</b>.

[0084] While this invention has been described with respect to the preferred and alternative embodiments, it will be understood by those skilled in the art that various changes in detail may be made therein without departing from the spirit, scope, and teaching of the invention. For example, windows may become widely employed in consumer applications such as operator panels for consumer electronics, appliances, and automobiles. Accordingly, the herein disclosed invention is to be limited only as specified in the following claims.