The present disclosure relates to methods for managing non-overlapping objects in a windows-like environment.
This section provides background information related to the present disclosure which is not necessarily prior art.
Graphical user interfaces may contain one or more windows. Windows may enable a user to view data, control software, etc. Users may edit the graphical user interface by moving and resizing windows. Such editing can become tedious when the interface includes multiple windows.
Some graphical user interfaces prevent some windows from overlapping. For example, a medical system may contain several patient status windows that cannot overlap. Further, it is difficult to communicate window overlapping restrictions to the user. Users who are accustomed to overlapping windows may become confused or frustrated when they are unable to overlap windows and must manually move each window to avoid overlap.
This section provides a general summary of the disclosure, and is not a comprehensive disclosure of its full scope or all of its features.
According to one aspect of the present disclosure, a method of editing a graphical user interface is disclosed. The method includes detecting a user command to adjust a first window to at least partially overlap with a second window, modifying the second window to prevent the overlap, and adjusting the first window as directed by the user command.
According to another aspect of the present disclosure, an apparatus includes a display and a controller configured to edit a graphical user interface shown on the display. The controller is configured to: detecting a user command to adjust a first window to at least partially overlap with a second window, modifying the second window to prevent the overlap, and adjusting the first window as directed by the user command.
Further areas of applicability will become apparent from the description provided herein. The description and specific examples in this summary are intended for purposes of illustration only and are not intended to limit the scope of the present disclosure.
The drawings described herein are for illustrative purposes only of selected embodiments and not all possible implementations, and are not intended to limit the scope of the present disclosure.
Corresponding reference numerals indicate corresponding parts throughout the several views of the drawings.
Example embodiments will now be described more fully with reference to the accompanying drawings.
Example embodiments are provided so that this disclosure will be thorough, and will fully convey the scope to those who are skilled in the art. Numerous specific details are set forth such as examples of specific components, devices, and methods, to provide a thorough understanding of embodiments of the present disclosure. It will be apparent to those skilled in the art that specific details need not be employed, that example embodiments may be embodied in many different forms and that neither should be construed to limit the scope of the disclosure. In some example embodiments, well-known processes, well-known device structures, and well-known technologies are not described in detail.
The terminology used herein is for the purpose of describing particular example embodiments only and is not intended to be limiting. As used herein, the singular forms “a”, “an” and “the” may be intended to include the plural forms as well, unless the context clearly indicates otherwise. The terms “comprises,” “comprising,” “including,” and “having,” are inclusive and therefore specify the presence of stated features, integers, steps, operations, elements, and/or components, but do not preclude the presence or addition of one or more other features, integers, steps, operations, elements, components, and/or groups thereof. The method steps, processes, and operations described herein are not to be construed as necessarily requiring their performance in the particular order discussed or illustrated, unless specifically identified as an order of performance. It is also to be understood that additional or alternative steps may be employed.
The windows may be graphical objects displayed on a graphical workspace. The windows may be, for example, rectangular, square, oval, etc. The windows may include graphical control features such as, for example, toolbars, menus, buttons, etc. The windows may be control windows which contain control features. Also, the windows may be display windows which display data, videos, etc. The windows may be represented in two dimensions or in three dimensions.
This method automates the process of managing non-overlapping windows. Thus, the tedium and confusion experienced by the user is reduced.
The method is not limited to user commands to move a window. For example, the user command may be to move a group of windows. Also, the user command may be to resize one or more windows.
The user may initiate user commands by clicking on a window and dragging it with a mouse. User commands may be initiated in other ways, for example, by typing on a keyboard or by activating other user interface devices.
The boundaries of the display area 104 are not the only possible constraints. Some types of windows, for example control windows, may be confined to a sub-area of the display area 104. The edges of such a sub-area may also create constraints.
Sub-window 172 and sub-window 174 may be, for example, control windows. Window 170 may encompass all control windows located on the display area 104. In this way the control windows are conveniently grouped and are easily discernable.
A preferred embodiment of the graphical user interface implemented as part of a medical system is indicated generally as 300 in
For a variety of reasons including regulatory, system design preferences, and system user preferences, there are occasions where one or more of the windows should remain visible on the display at all times. This means that certain windows 306′ should not be overlapped by other windows, which makes it very difficult to rearrange the windows 306 on the display 304. Examples of such windows in this description are identified as 306′, while 306 identifies the windows generically. Windows 306′ may be displayed with a distinctive (in color or appearance) border 308.
In accordance with the principles of this invention, when a window 306 is moved (for example by clicking and dragging) or expanded (by clicking and dragging a corner or side) on the display 304 and encounters a window 306′ rather than the action being blocked by the boundary of the window 306′, the action is allowed to continue, and the window 306′ is displaced. This is illustrated in
These same rules of movement of a window 306′ can apply when the window 306′ is moved directly (either by clicking and dragging) or expanded (by clicking and dragging a side) and is not being pushed by another window 306 or 306′.
An image from an actual user interface is shown in
Although the terms first, second, third, etc. may be used herein to describe various elements, components, regions, layers and/or sections, these elements, components, regions, layers and/or sections should not be limited by these terms. These terms may be only used to distinguish one element, component, region, layer or section from another region, layer or section. Terms such as “first,” “second,” and other numerical terms when used herein do not imply a sequence or order unless clearly indicated by the context. Thus, a first element, component, region, layer or section discussed below could be termed a second element, component, region, layer or section without departing from the teachings of the example embodiments.
Spatially relative terms, such as “inner,” “outer,” “beneath”, “below”, “lower”, “above”, “upper” and the like, may be used herein for ease of description to describe one element or feature's relationship to another element(s) or feature(s) as illustrated in the figures. Spatially relative terms may be intended to encompass different orientations of the device in use or operation in addition to the orientation depicted in the figures. For example, if the device in the figures is turned over, elements described as “below” or “beneath” other elements or features would then be oriented “above” the other elements or features. Thus, the example term “below” can encompass both an orientation of above and below. The device may be otherwise oriented (rotated 90 degrees or at other orientations) and the spatially relative descriptors used herein interpreted accordingly.
The foregoing description of the embodiments has been provided for purposes of illustration and description. It is not intended to be exhaustive or to limit the invention. Individual elements or features of a particular embodiment are generally not limited to that particular embodiment, but, where applicable, are interchangeable and can be used in a selected embodiment, even if not specifically shown or described. The same may also be varied in many ways. Such variations are not to be regarded as a departure from the invention, and all such modifications are intended to be included within the scope of the invention.
This application is a continuation of PCT/US2011/027470, filed Mar. 8, 2011, which claims benefit of U.S. Provisional Application No. 61/311,510, filed on Mar. 8, 2010, the entire disclosures of both are incorporated herein by reference.
Number | Date | Country | |
---|---|---|---|
61311510 | Mar 2010 | US |
Number | Date | Country | |
---|---|---|---|
Parent | PCT/US2011/027470 | Mar 2011 | US |
Child | 13592896 | US |