JPH08212035A - Method and mechanism for customization of display of user interface function - Google Patents

Abstract

PROBLEM TO BE SOLVED: To provide a method and mechanism of computer execution for allowing a user to easily customize a user interface to eliminate unrequited functions or fields to perform simplification to subscribe the title of a part of the field. SOLUTION: The user places a focus or a cursor on the field to be changed and performs button combination input by a selector. Thus, regardless of whether or not display is performed at present, a pop-up menu 11 for list- displaying all elements possible in the field is displayed. The actually displayed elements are identified inside a list. By clicking one of the elements inside the list, the user makes a computer change the display characteristics of the function.

Description

Detailed Description of the Invention

[0001]

FIELD OF THE INVENTION The present invention relates to the field of user interface controls and more specifically provides a mechanism for adjusting various functions displayed to the user. The present invention, in one aspect, provides a simple method of displaying only one subset of all selections at a time,
Another aspect provides a means for replacing the titles and keywords of user interface elements on the screen with item terms selected by the user, which is particularly useful for users who need unnecessary reduction in screen display complexity.

To meet the current and future evolving demands of many users, many computer operating systems are provided to users with many options. Icon representation in window display, symbol placed in window frame and title bar,
Both pop-up menus and pull-down menus are user interface options currently available to the user to select an action. The purpose of using attractive visual formats is, of course, to make programs "user friendly" and encourage "computer newbies" to use such programs as well.

However, if some of the options or actions expressed are not suitable for a particular system use, or the symbols and keywords displayed are generic and have no meaning for a particular application use, Or, if it is misleading, it may be overwhelmed by such a rapid increase in symbol display. Many window components, even though specifically designed by the manufacturer as "user friendly",
The user interface may appear more complex and less user friendly because it is more noticeable.

An example of this is a general purpose terminal in a central office setting that is used only for selected activities. Faced with the proliferation of symbolic options and actions provided by standard operating system programs, many of which are confusing to the user if they are not needed to use a particular terminal.

Also, when the prompts for actions are common (as is often the case with off-the-shelf software), sometimes-used users often forget which actions are activated by each prompt. It can be time consuming, either by trial and error, or manually looking up this information.

In addition to the above, the proliferation of unnecessary symbols causes
Usability of the workspace on the screen is also reduced. Window components such as title bars and scroll bars fill valuable space. Removing unnecessary items should help provide enough space on the screen to display all the information the user needs to provide for minimal scrolling and other windowing. .

[0007]

BACKGROUND OF THE INVENTION Flemming and Torres, "User Interface Design to Hide Complexity in Dia."
Recognized and discussed in IBM Technical Disclosure Bulletin Vol. 34, No. 9, published in February 1992, entitled "logs." This paper presents a standard approach to the prior art and a user interface to the user. It discusses new techniques that allow the display to be adjusted.
As mentioned above, many applications on the market today offer pull-down menus from the menu bar to resize, minimize, or position the display actions for a particular action in various main windows. Choices for controlling the customization of the user interface display for are listed. The new solution proposed in the above paper is to bring down the pull-down'Options 'menu by clicking'Options' on the pull-down menu which is related to the system menu icon on the title bar of that window.
It is to replace with a selection item. If you select the "Options" choice, a pop-up menu should list the available options that you can customize later. This should allow especially inexperienced users to carefully select a customization rather than initiating an unplanned screen change without knowing how to "undo" the changes. The above paper describes one particular customization that may be done, namely "sorting", from smallest to largest, alphabetically, etc.
It only mentions the choice of the particular way in which the option will perform.

Similarly, "System for In" by Koopmans et al.
teractively Creating Action BarPull-Down Windows o
US Pat. No. 5,121,477 entitled "fa User Interface for Use at Program Run Time" discusses the lack of end-user control specific to off-the-shelf software products in the display of user interface items. The patent relates to a system that automatically displays a screen during initialization of an application or process that allows the user to customize the data display for running the application, including the definition of subsequent pull-down menus. The entered customizations can be saved for subsequent application execution.

"Method and System for Padawer et al.
Customizing a User Interface inan Integrated Envir
U.S. Pat. No. 5,220,675 entitled "onment"
It describes a mechanism that allows a user to easily install and remove features from an application by a simple means of editing a menu list of application features. The "Customize Menu" option is displayed to the user by selecting the "Utilities" title on the menu displayed for that application. Selecting this option launches a series of windows that guide the user through the programming required to link to the new feature.

Other applications have also addressed the problem of user interface customization at the system design level. For example, "Multi-Lev" by Lane et al., Which suppresses the display of items previously designated as "not selectable".
US Patent No. 484353 entitled "el Dynamic Menu"
No. 8 and "Software Development System" by Geary et al.
US Pat. No. 5,206,950 entitled "and Method Using Expanding Outline Interface" relates to a mechanism for facilitating the customization of user displays during application development. US Pat.
The No. 8 dynamic menu automatically includes application or process means for suppressing menu items that represent actions or options that are unavailable or non-functional in the system engineer designed application or process. US Patent No. 520695
No. 0 relates to a mechanism that facilitates program designers' task of designing customized menus and other display-oriented program objects for a particular application. One such mechanism is an outliner editor that includes a flag that indicates whether high level menu items can be extended to lower level subdivisions. An interactive drawing program for designing a visual display is also disclosed.

Torres "Computer User Interface w
U.S. Pat. No. 5,140,678 entitled "ith Window Title Bar Icons" discloses a mechanism for hiding title and action bars from the display by windows. However, the problem of customization is not addressed. No mechanism is provided to change the items displayed in the title bar or action bar and the items available on those bars, rather the user "covers" the bars by clicking the mouse. You can redisplay it by repeating this action. Also, Torr
US Pat. No. 5,040,131, entitled "Graphical Processing" by es, relates to a user interface that displays only iconic pictorial representations of processes, such as in database settings, which are determined as a response to the system. Yes, it is not a user initiated customization.

In contrast to all of the above patents, the present invention does not actually affect the execution of the application, nor does it affect the execution of the application. It relates to a means for allowing the user to customize the display of interface fields very simply. The type of customization proposed in the present invention is to remove these elements from the display so that they can easily be re-incorporated with elements that are rarely used or not used at all in response to changing user demands, title·
And a means for rewriting titles and keywords displayed on user interface elements such as bars. The clarity and simplicity of this customizing technique means that even unskilled users can use it,
The customization can easily be reversed or changed later.

[0013]

SUMMARY OF THE INVENTION It is therefore an object of the present invention to provide means for customizing a user interface to display only one subset of all selected items at a time, whereby It can help inexperienced users learn software and help other users to gain more "physical property" on the display.

Experienced users may need access to the full set of features as they gain experience, and other users may need access to features for different applications. It must be possible to re-embed selections removed from the interface. Therefore, another object of the present invention is to
It is to provide a control mechanism that temporarily removes window components from the interface, but allows the removed components to be easily re-incorporated.

Another object of the invention is a means for allowing a user to customize the title of the user interface and command prompt keywords so that such text symbols are more meaningful to a particular application. To provide.

[0016]

SUMMARY OF THE INVENTION Therefore, the present invention provides
Provides a process for customizing the display of user interface features in application windows. This process consists of displaying a list of user interface features for an application window that distinguishes between show and hide feature settings in response to a single user action, and at least one item in the list. It comprises the computer-implemented steps of receiving a user selection and responsively entering a change to the list of features, and changing the display of the feature in the window in response to the change to the list of features.

The invention also provides a mechanism for displaying an application window with a user interface feature from a master file that includes an on / off setting for displaying each of a plurality of user interface features. A user-initiated customizer for modifying the displayed user interface features also provides a list of user interface features that distinguish between show and hide feature settings in response to a single user input action. Means, means for reversing the setting of functions in the list in response to user selection, and means for reversing the display of functions in the application window.

The mechanism of the present invention comprises means for receiving a user input title in a list of user interface functions,
It is also preferable to provide a means for changing the title displayed in the user application window to a user input title.

Embodiments of the present invention will now be described in detail with reference to the accompanying drawings.

[0020]

DETAILED DESCRIPTION OF THE INVENTION A typical application window (1) having a window frame (2) and a client area (3), shown in FIG. 1, generally includes a plurality of user interface fields or components. Is displayed. Such fields include a title bar (4) that identifies the characteristics of the file associated with the application window, a menu bar (5) with a title that identifies the various actions the user can take, a window that the user can There is a system menu icon (7) that allows you to operate and close the. Both the system menu icon (7) and the resize icon (8) shown in FIG. 1 may have associated functionality that is outside the scope of the present invention.

Other typical user interface components not shown in FIG. 1 include scroll bars and menu bars that allow the user to move forward or backward within the text of multiple pages. (5)
There is an area of information that provides the user with execution annotations that describe either the purpose of the various action titles (6) within or what operation the computer is processing at a given time. An example of an information area in the form of a bar across the lower window frame (2) is shown in FIG. 7 (9).

The present invention provides for customizing the information displayed in the user interface fields because the typical window display provided by a general purpose application program cannot meet all user requirements. Provide the means. Several customized applications according to the present invention are shown in Figures 2-7, as described below.

In the preferred embodiment of the invention, the on-screen mechanism that allows the user easy access for customizing the window display is a pop-up menu. Although a range of pop-up menus showing various ranges and functions is shown in FIG. 2, according to a preferred embodiment of the present invention, only one customized pop-up menu should appear on the display at a time. Yes, multiple popups may confuse the user.

Two pop-up menus are shown in FIG. The first menu in (11) is Menu
Related to title (6) displayed in bar (5), (1
The second menu in 2) is related to the action title (6) pull-down menu (10) for "display" on the menu bar (5), and the third menu in (13) is the window client area. Related to (3).

However, in general, if the user wants some customize action related to one of the user interface fields, then only one popup menu should be displayed, and another field for customization. Selecting will cause the first pop-up menu to disappear and be replaced on the display by the pop-up menu associated with the second field selected. Therefore, if the user wants to customize the title (6) on the menu bar (5), only the popup menu (11) associated with this field will be displayed, as shown in FIG.

FIG. 3 illustrates one aspect of the present invention. The menu bar (5) displays four titles (6). 5 in the related pop-up menu (11)
There are two possible title choices,
Only the titles actually displayed on the menu bar (5) are displayed on the menu (11) with a selection marker (14) in the form of "X" on the side. Since the title selection item "Annotate" is not selected, it is hidden in the menu bar (5).

Another aspect of the invention is outlined in FIG. 4, which illustrates the sequential steps for changing the terminology of the title (6) shown in the menu bar (5). Shows. When the popup menu (11) is first displayed, this menu lists the titles (6) actually displayed as well as the hidden titles. However, by focusing (15) on one of the titles as shown in the pop-up menu (11a), the user can
You can enter the new title "New" shown in b) and when this change is performed, the title (6) that is actually displayed in the menu bar (5a).
a) will be updated. Figure 5 shows the customization of other fields. Usually, the action title (6) of the menu bar (5) represents the overall action. By selecting a particular action title (6), the user can menu (10) to list the finer actions associated with that title.
Pull down. Similar to the diagram of FIG. 3, the customize pop-up menu (12) related to the action title pull-down menu (10) displays a list of the displayed detailed action titles with a selection marker (14). Then, the hidden titles are displayed in a list without a selection marker.

6 and 7 show the function of the pop-up menu (13) associated with the client area (3) of the window (1). The pop-up menu (13) of Figure 6 lists four functions, only two of which are shown, the title bar (4) and the menu bar (5), with a selection marker (14). ,
The screen is displayed accordingly. However, in the window shown in FIG. 7, the user removes the selection marker from the menu bar (this feature will no longer appear in the window), and the "information area" (9) is displayed in the window so that the "information area" is displayed. (Info area) ”, a selection marker is added.

8-11 are flow charts illustrating aspects of practicing the present invention within the computer of the preferred embodiment of the present invention. The basic process for performing the customization shown in FIGS. 6 and 7 is shown in FIG. Figure 9
Shows computer steps for implementing the customization shown in FIG. 4, and FIGS. 10 and 11 show two kinds of safety protection functions applicable to various system requirements.

Referring first to FIG. 8, start-up (block 2
1) Later the program is initialized in the system (block 22). A file containing window feature settings is accessed and loaded into the system (block 2).
3). To display the main window of the initialized program until the user closes the window,
The current settings from the settings file are implemented (block 2
4).

Note that the settings file contains all of the display settings for the main window available on this system or under the initialized program.
The "current" setting, i.e. what is visually realized when the main window is displayed, is "true" and the setting for the feature the user has chosen to hide from the user interface display is " Become false.

The standard defaults for configuration files all have the setting "true" so that all possible user interface features are visible when the main window is first displayed. The user can then customize the main window to remove unnecessary features, as described below.

The following code sets up the data area of the preferred embodiment, specifying a variable for each item that can be turned on or off. When this is set up, all values are "on". next,
The configuration file is read and the values in the configuration file overwrite the default values.

The definition for setting up the data area is as follows.

# Define MAXLEN 255 typedef struct APPLSTATUS {BOOL fEnable; ULONG ulControlID; CHAR szControl String [MAX_LEN];} APPLSTATUS;

Using this definition, a typical configuration file should look like this when all values are "on": However, it should be noted that the configuration file shown below is a subset of all the functions shown in FIG.

APPLSTATUS applStatus = {{{TRUE, MAB_IDM_POP_BILLOFLADING}, {TRUE, MAB_IDM_POP_ANNOTATE}, {TRUE, MAB_IDM_POP_VIEW}, {TRUE, MAB_IDM_POP_OPTIONS}, {TRUE, MAB_IDM_POP_HELP_}, {TRUE, MAB_IDM_POP_HELP_}, {TRUE, MA, {TRUE, MAB_IDM_POP_GO}, {TRUE, MAB_IDM_POP_NEXT}, {TRUE, MAB_IDM_POP_ROTATE}, {TRUE, MAB_IDM_POP_ZOOM}, {TRUE, MAB_IDM_POP_SHRINK}, {TRUE, MAB_IDM_POP_VERTSCROLL_, TRUE_MAB __, _ BAR, _, _ TRUE, MAY , MAB_IDM_POP_MENUBAR}}},

When an item is turned off or on, a call is sent to the graphics engine to disable or display its control.

If the user makes a button combination input (ie, presses all mouse buttons at the same time) in any area of the user interface display while the window is open (block 25), the customer is prompted by the user. In response to a user selection to edit or otherwise change the interface display, a series of steps beginning at block 26 of FIG. 8 are performed. The term "button combination input" is used here to indicate one of the selection methods. Generally, by using a mouse-oriented cursor, a user can focus on a user interface display field such as a menu bar, pull-down menu, client area of the main window itself, or click the mouse. Or, press the key to display a pop-up menu as shown in any of FIGS. 3, 5, 6, or 7 (block 26).

The binding of mouse button and / or key and button combination input can be programmed in a known manner. For example, place the cursor anywhere in a field of the main window to display a pop-up "Customize" menu, or the mechanism provided by the present invention allows you to customize the field to start it. When the user needs to focus on the occupied space, it may be preferable to allow the user to click the right mouse button that is rarely used.

The present invention should allow the user to place the cursor focus within the boundaries of the menu bar and make a button combination entry on that field (block 25). This will cause an appropriate pop-up menu to be displayed (block 26), which is a pop-up menu listing the title bar functions (11), as shown in FIG. User·
The list of interface functions includes means for indicating to the user which functions are currently displayed and which are available but not currently displayed in the fields of the window selected by the user. The means of distinguishing between displayed and undisplayed features is to include a check mark beside the features that are "on" or "true" and therefore displayed in that field.

The user can move through the list of items simply by changing the focus of the cursor or by using the up and down arrow terminal navigation keys on the terminal keyboard. To select an item to modify (block 27 of Figure 8), the user can click the mouse or use any other known selection method. The computer performs a check to determine if the "ALT" key has been pressed (block 40) at the same time the user has selected an item (block 27), which activates the steps of FIG.

If the user's choice is simple, and the user's choice in the pop-up menu is marked as true and the feature is visible (block 28), then the user's choice for that choice is Removes the check mark and sets the function to "false" (block 29). When the pop-up window is dismissed (block 31), its functionality is removed from the window block during window redisplay (block 35). If the popup menu choice is unmarked (block 28), it is "false"
And its functionality is currently hidden in the fields of the window. When the user clicks on the choice to add a check mark to the choice and sets it to "true" (block 30), the feature is reinserted into the window during the refresh (block 35). It

Removing a given function modifies the physical size of the window. For example, if the selected field is an entire window, removing the title bar from the window will change the frame (block 33) and the size of the client area of the main window before redisplaying (block 35). A modification (block 34) is needed.

In the double buffer system, all changes in the window can be written to the background window. When that writing is complete, the background window can be switched to the foreground. This operation is not needed in the more general single buffer system to which the steps shown in FIG. 8 relate.

After redisplaying the window (block 35), the changes are written to the configuration file (block 3).
6) The user can exit the program (blocks 37, 38). If, after invoking the popup menu, the user chooses not to make any changes to the user interface customization (block 27), the popup menu for that field is cleared (block 31) and the window settings Exit the change loop without making any changes (block 3
2, 37), the user only has to click the mouse button in another position (block 39).

Alternatively, by making a button combination entry in another field on the window (block 25), an appropriate pop-up menu for the new field is displayed to customize the user interface functionality of that field. (Block 26).

FIG. 4 shows an outline of a procedure for customizing titles and keywords by rewriting as desired. This procedure is implemented in a computer, as shown in the flow chart of Figure 9, according to a preferred embodiment of the present invention.

The standard window display steps shown in FIG. 8 are performed, but when the user selects an item in the pop-up menu (block 27 of FIG. 8):
The "ALT" key is also pressed (block 40). As shown in FIG. 9, this changes the item in the popup menu to an input field (block 41) and allows the user to overwrite the existing item title (block 42). The user enters a new title by selecting the enter key (block 43) to update the pop-up menu with the new title (block 46).

To avoid entering a new title, the user can select the "ESC" key (block 44). This returns the field to the original title (block 45) and the user returns to the main loop at block 27 of FIG.

When the pop-up menu is updated with the new name (block 46), the user either returns to the main loop at block 27 of FIG. 8 or clicks another field in the window (block 47). , Update the control by changing the name of the function actually displayed in the window (block 49),
It is also possible to update the settings in memory (block 50) by passing a string for the new name after clearing the pop-up menu (block 48). The user then returns to block 37 of FIG.

10 and 11 show a user I set up by a separate program using known methods.
6 shows how to integrate user profile functionality into the present invention based on D. In FIG. 10, the user's logon ID is used to identify the appropriate window setting. After startup (block 51), the program is called (block 52) and the logon screen is displayed (block 5).
3). The user logs in with his specific ID to enter the program (block 54) and uses this information to
The configuration file is searched for predefined settings associated with this user ID (block 55). If a predefined setting exists for this user ID (block 56), that setting is loaded into the system (block 5).
7). If there is no predefined setting corresponding to this user ID (block 56), the default setting profile is loaded into the system (block 58). Once the settings file is established, a window is displayed based on the values in this file (block 24, also shown in Figure 8).

With this user identification system, the user
User permissions for security controls can be put in place for the types of changes that can be made to customize the interface, an example of this system is shown in FIG. When the system receives a button combination input by the user in the user interface field (block 25), the user's ID is checked to see if this user ID has permission to customize the window function (block 60). The setting profile is checked (block 59).
If you have permission, block 26 of FIGS. 8 and 9.
Customization continues as shown below. If you do not have permission, the customize program will end automatically.

In the preferred embodiment, establishing a meta-data area ensures that both user profiles and permissions are in place. The modification of the above data area definition should be as follows.

Typedef struct USER_PROFILE {CHAR szUserID [MAX_USERID_LEN]; CHAR szPassword [MAX_PASSWORD_LEN]; BOOL fUpdatable; APPLSTATUS applstatus [MAX_CONTROLS]; CHAR szControl String [MAX_LEN];} USER_PROFILE;

Modifications of the invention that are obvious to those skilled in the art are intended to be covered by the following claims.

In summary, the following matters will be disclosed regarding the configuration of the present invention.

(1) A method of customizing the display of the user interface function of the application window displayed from the master file, wherein the setting of the display function and the non-display function is distinguished in response to a single user action. Computer-implemented steps for displaying a list of user interface features for an application window and receiving a user selection for at least one item in the list and responsively entering a change to the list of features. , A computer-implemented step of changing the display of the function in the window in response to a change in the list of functions. (2) The method according to (1) above, wherein the step of receiving a user selection and inputting a modification of the list of functions comprises the step of reversing display settings for said at least one item in the list. . (3) Receiving a user selection and inputting a change to the list of functions includes receiving and replacing user input text in said at least one item, and changing the display of user interface functions is an application. The method according to (1) above, including the step of replacing the user input text in the window. (4) The method according to (1) above, wherein the step of displaying the list of user interface functions includes the step of displaying a list of user interface functions for fields in the application window. (5) The step of displaying a list of user interface features for fields in the application window is a menu in the application window.
Method according to (4) above, including the step of displaying a list of action titles for the bar. (6) The step of displaying a list of user interface functions for fields in an application window includes the step of displaying a list of actions for a pull-down menu in the application window. The method according to 4). (7) Displaying a list of user interface features for fields in an application window includes displaying a list of user interface features for a client area in an application window. The method according to (4) above. (8) The method of (4) above, further comprising the step of receiving a user selection of a field in the application window before displaying a list of user interface functions for the field. (9) Master on receiving a user selection of a field in the application window before displaying the list of user interface features for that field.
The method according to (8) above, further comprising the step of checking the authorization of the user ID from the file. (10) In a mechanism for displaying an application window with said user interface function from a master file containing on / off settings for displaying each of a plurality of user interface functions, the displayed user A means for a user-initiated customizer to modify interface features, in response to a single user input action, to display a list of user interface features that distinguish between visible and hidden feature settings, and in response to a user selection. And a means for reversing the setting of the function in the list and a means for reversing the display of the function in the application window according to the change of the list. (11) Means for displaying a list of user interface features includes means for displaying a list of user interface features for said field in response to a single user select action on a field in an application window. The mechanism described in (10) above. (12) The above (10), further comprising means for receiving a user input title in the list of user interface functions and means for changing the title displayed in the application window to the user input title. Mechanism. (13) means for displaying a list of user interface features includes means for displaying a list of user interface features for said field in response to a single user select action on a field in an application window, The mechanism according to (12) above, characterized in that the means for receiving a user input title in the list of user interface functions comprises receiving a composite user selection on any item in the list. (14) The mechanism according to (10) or (12) above, further comprising means for updating the settings for displaying each of the user interface functions after the display in the application window. (15) The mechanism according to (10) above, further comprising means for accessing the master file for checking the user ID to change the displayed user interface function. (16) A data storage medium recorded by a user interface customization program, which is combined with a general-purpose computer installed to read and execute program data from the data storage medium into a memory, A data storage medium comprising the mechanism according to 10) or 11). (17) A data storage medium recorded by a user interface customize program, which is combined with a general-purpose computer mounted to read and execute program data from the data storage medium in a memory, and A data storage medium comprising the mechanism according to (12) or (13).

[Brief description of drawings]

FIG. 1 is an exemplary diagram of a user interface window on a computer display screen showing commonly used fields, components, and titles.

2 is a diagram of the window of FIG. 1 showing a pop-up menu of multiple fields within the window in accordance with the present invention.

FIG. 3 illustrates a procedure for changing text options in the menu bar of the window of FIG. 1 according to one aspect of the invention.

FIG. 4 illustrates a procedure for changing a text option in the menu bar of the window of FIG. 1 according to one aspect of the present invention.

5 is a diagram showing hidden options for the pull-down "View" menu shown in the window representation of FIG.

6 illustrates a procedure for modifying a user interface component within a field of a frame of the window of FIG. 1 according to another aspect of the present invention.

7 illustrates a procedure for modifying a user interface component within a field of a frame of the window of FIG. 1 according to another aspect of the present invention.

FIG. 8 is a flow chart illustrating aspects for implementing the invention in a computer in accordance with a preferred embodiment of the invention.

FIG. 9 is a flow chart illustrating aspects for implementing the invention in a computer in accordance with a preferred embodiment of the invention.

FIG. 10 is a flow chart illustrating aspects for implementing the invention in a computer in accordance with a preferred embodiment of the invention.

FIG. 11 is a flow chart illustrating aspects for implementing the invention in a computer in accordance with a preferred embodiment of the invention.

[Explanation of symbols]

 1 Application Window 2 Window Frame 3 Client Area 4 Title Bar 5 Menu Bar 6 Action Title 7 System Menu Icon 8 Resize Icon 11 Popup Menu 14 Selection Marker

 ─────────────────────────────────────────────────── ─── Continued Front Page (72) Inventor Robert Joseph Krieg Raleigh Cooper Hill Drive, North Carolina, USA 114 (72) Inventor David George Like United States Charlotte Voice Road, North Carolina 652 (72) Inventor Cynthia A. Roskin, USA Austin, Texas Bakero Trail, 10118 (72) Inventor David A. Shell, Reston, Newbridge Court, Virginia, USA 11661

Claims (17)

[Claims] 1. A method of customizing the display of user interface features of an application window displayed from a master file, the method distinguishing between show and hide feature settings in response to a single user action. A computer-implemented step of displaying a list of user interface features for an application window; receiving a user selection on at least one item in the list and responsively entering a change to the list of features; Computer-implemented step of changing the display of the function in the window in response to a change in the list of functions. 2. A step of receiving a user selection and inputting a modification of a list of functions, said at least one in the list.
The method of claim 1 including the step of reversing display settings for one item. 3. Receiving a user selection and entering a change in a list of features includes receiving and replacing user input text in said at least one item, and altering the display of user interface features. The method of claim 1 including the step of replacing the user input text in the application window. 4. The method of claim 1, wherein displaying a list of user interface features includes displaying a list of user interface features for fields in an application window. . 5. The step of displaying a list of user interface features for a field in an application window includes the step of displaying a list of action titles for a menu bar in the application window. The method of claim 4, wherein 6. The step of displaying a list of user interface features for a field in an application window comprises the step of displaying a list of actions for a pull-down menu in the application window. The method of claim 4. 7. The step of displaying a list of user interface features for a field in an application window includes the step of displaying a list of user interface features for a client area in an application window. The method of claim 4, wherein 8. The method of claim 4, further comprising the step of receiving a user selection in a field in the application window before displaying a list of user interface features for that field. 9. The method further comprises the step of checking the authorization of the user ID from the master file in receiving the user selection in the field before displaying the list of user interface features for the field in the application window. 9. The method according to claim 8, characterized in that 10. A master including on / off settings for displaying each of a plurality of user interface features.
In a mechanism for displaying an application window with said user interface function from a file, a user initiated customizer for changing the displayed user interface function displays in response to a single user input action. A user interface that distinguishes between hidden and hidden feature settings. A way to display a list of features, a way to reverse feature settings in the list in response to user selection, and an application window in response to changes in the list. And a means for reversing the display of the function of. 11. A means for displaying a list of user interface features for displaying a list of user interface features for a field in an application window in response to a single user select action on the field. 11. Mechanism according to claim 10, characterized in that it comprises. 12. The method of claim 10, further comprising means for receiving a user input title in the list of user interface functions and means for changing the title displayed in the application window to the user input title. The described mechanism. 13. A means for displaying a list of user interface features in response to a single user select action on a field in an application window, the means for displaying a list of user interface features for said field. 13. The mechanism of claim 12, comprising and means for receiving a user input title in the list of user interface features includes receiving a composite user selection on any item in the list. 14. A mechanism as claimed in claim 10 or 12, further comprising means for updating settings for displaying each of said user interface features after display in an application window. 15. The mechanism of claim 10, further comprising means for accessing the master file for verification of a user ID to modify displayed user interface functionality. 16. A data storage medium recorded by a user interface customize program, together with a general-purpose computer mounted to read and execute program data from the data storage medium into a memory, A data storage medium comprising the mechanism according to claim 10 or 11. 17. A data storage medium recorded by a user interface customize program, together with a general-purpose computer mounted to read and execute program data from the data storage medium into a memory. A data storage medium comprising the mechanism according to claim 12 or 13.