CA2218593C - Method and system for automatic persistence of controls in a windowing environment - Google Patents
Method and system for automatic persistence of controls in a windowing environment Download PDFInfo
- Publication number
- CA2218593C CA2218593C CA002218593A CA2218593A CA2218593C CA 2218593 C CA2218593 C CA 2218593C CA 002218593 A CA002218593 A CA 002218593A CA 2218593 A CA2218593 A CA 2218593A CA 2218593 C CA2218593 C CA 2218593C
- Authority
- CA
- Canada
- Prior art keywords
- control
- window
- user interface
- definition
- displayed
- Prior art date
- Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
- Expired - Lifetime
Links
Classifications
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F9/00—Arrangements for program control, e.g. control units
- G06F9/06—Arrangements for program control, e.g. control units using stored programs, i.e. using an internal store of processing equipment to receive or retain programs
- G06F9/44—Arrangements for executing specific programs
- G06F9/451—Execution arrangements for user interfaces
Abstract
A computer system for persistently storing information entered by a user into an edit control of a property page. In a preferred embodiment, the computer system has a registry for storage of information identified by a key. An application program has a resource file that contains a definition of controls for the property page. The controls include the edit control designated as editable by the user and a buddy control that is adjacent to the edit control, that is designated as not visible, and that has text which specifies a key within the registry. The computer system displays the property page by detecting that the buddy control is adjacent to the edit control and is designated as not visible, by retrieving the text for the buddy control, by retrieving information from the registry using the key specified by the retrieved text, and by initializing the edit control to the retrieved information. The computer system also allows a user to modify the information of the edit control and then stores the modified information of the edit control in the registry using the key specified by the retrieved text to effect persistent storage of the information for the edit control in the registry.
Description
Description METHOD AND SYSTEM FOR AUTOMATIC PERSISTENCE
OF CONTROLS IN A WINDOWING ENVIRONMENT
s Technical Field The present invention relates generally to a computer system for storing of data and, in particular, a system for persistently storing data of a control of a window.
to Background of the Invention Many computer systems provide a window-based user interface through which a user can interface with a computer program. A window is an area, typically rectangular, of a display device in which the computer program is displays its output. A window may contain several different types of "fields"
into which the computer program can display data. For example, in one field the computer program can display a label to be viewed by a user, and in another field the computer program can echo the characters entered by a user with a keyboard.
Each of these fields are typically implemented as a child window of the window 2o in which they are contained. These child windows are also known as "controls."
Figure 1 a illustrates a window that contains controls. Because this window contains information relating to properties of a document, it is known as a property sheet. A property specifies certain characteristics of an object, such as a document. For example, the properties of a document may include name of the 2s author and date of creation, whereas the properties of a character may include font and color. The property sheet 101 contains five property pages: general 102, summary 103, statistics 104, contents 105, and custom 106. Each property page is a child window of the property sheet and contains various controls, which
OF CONTROLS IN A WINDOWING ENVIRONMENT
s Technical Field The present invention relates generally to a computer system for storing of data and, in particular, a system for persistently storing data of a control of a window.
to Background of the Invention Many computer systems provide a window-based user interface through which a user can interface with a computer program. A window is an area, typically rectangular, of a display device in which the computer program is displays its output. A window may contain several different types of "fields"
into which the computer program can display data. For example, in one field the computer program can display a label to be viewed by a user, and in another field the computer program can echo the characters entered by a user with a keyboard.
Each of these fields are typically implemented as a child window of the window 2o in which they are contained. These child windows are also known as "controls."
Figure 1 a illustrates a window that contains controls. Because this window contains information relating to properties of a document, it is known as a property sheet. A property specifies certain characteristics of an object, such as a document. For example, the properties of a document may include name of the 2s author and date of creation, whereas the properties of a character may include font and color. The property sheet 101 contains five property pages: general 102, summary 103, statistics 104, contents 105, and custom 106. Each property page is a child window of the property sheet and contains various controls, which
2 are child windows of the property page. For example, the custom property page contains combobox 107, edit box 108, check box 109.
Certain windowing environments, such as Windows~ by Microsoft Corporation, provide various tools to help a programmer generate programs that s use windows and controls. In particular, to create a property page, such as the custom property page, a programmer uses a resource editor to define the layout and characteristics of the property page. These characteristics are stored in a .
resource file, which is opened and used by the computer program. Table 1 contains an excerpt of a resource file corresponding to the custom property page.
This portion of the resource file contains the definition of the combobox 107, the edit box 108, the check box 109, and their associated labels. Each line contains the definition of a control. Line 1 corresponds to the label "ape:" to the left of combobox 107 and indicates that the control is a text control (i. e. , "LTEXT") and that the control is static and located at the specified location. The location 15 represented by "[location]" in each line indicates the upper left coordinates and the lower right coordinates of the location of the control within the custom property page. Line 2 corresponds to the combobox 107, indicates that the control is a combobox (i.e., "COMBOBOX"), and contains a unique identifier for the combobox (i.e., "IDC COMBO1"). Line 2 also indicates that the 2o combobox has a drop down list and that when a user tabs through the controls, the tab will stop at this combobox. Line 3 corresponds to the label "Value:"
and indicates that the control is a text control and is static. Line 4 corresponds to the edit box 108, indicates that the control is an edit box (i.e., "EDITTEXT"), and contains a unique identifier for the control. Line 4 also indicates that the control 2s will scroll horizontally and that the tab will stop at this control. Line 5 corresponds to the check box 108, indicates that the control is a control (i.e., "CONTROL"), and contains a unique identifier for the control. Line 5 also
Certain windowing environments, such as Windows~ by Microsoft Corporation, provide various tools to help a programmer generate programs that s use windows and controls. In particular, to create a property page, such as the custom property page, a programmer uses a resource editor to define the layout and characteristics of the property page. These characteristics are stored in a .
resource file, which is opened and used by the computer program. Table 1 contains an excerpt of a resource file corresponding to the custom property page.
This portion of the resource file contains the definition of the combobox 107, the edit box 108, the check box 109, and their associated labels. Each line contains the definition of a control. Line 1 corresponds to the label "ape:" to the left of combobox 107 and indicates that the control is a text control (i. e. , "LTEXT") and that the control is static and located at the specified location. The location 15 represented by "[location]" in each line indicates the upper left coordinates and the lower right coordinates of the location of the control within the custom property page. Line 2 corresponds to the combobox 107, indicates that the control is a combobox (i.e., "COMBOBOX"), and contains a unique identifier for the combobox (i.e., "IDC COMBO1"). Line 2 also indicates that the 2o combobox has a drop down list and that when a user tabs through the controls, the tab will stop at this combobox. Line 3 corresponds to the label "Value:"
and indicates that the control is a text control and is static. Line 4 corresponds to the edit box 108, indicates that the control is an edit box (i.e., "EDITTEXT"), and contains a unique identifier for the control. Line 4 also indicates that the control 2s will scroll horizontally and that the tab will stop at this control. Line 5 corresponds to the check box 108, indicates that the control is a control (i.e., "CONTROL"), and contains a unique identifier for the control. Line 5 also
3 contains a label for the control (i.e., "Link To Content") and indicates that the control is a check box and that the tab will stop at this control.
Table 1 s BEGIN
1 LTEXT "tee:", IDC STATIC, [location]
2 COMBOBOX IDC COMBO1, (location], CBS DROPDOWNLIST, WS TABSTOP
3 LTEXT "Value:", IDC_STATIC, [location],
Table 1 s BEGIN
1 LTEXT "tee:", IDC STATIC, [location]
2 COMBOBOX IDC COMBO1, (location], CBS DROPDOWNLIST, WS TABSTOP
3 LTEXT "Value:", IDC_STATIC, [location],
4 EDITTEXT IDC EDIT1, [location], ES AUTOHSCROLL, WS TABSTOP
is s CONTROL "Link To Content", IDC CHECK1, "Button", [location]
BS AUTOCHECKBOX, WS TABSTOP
END
The use of resource files allows for various changes to be made to the arrangement and content of the controls without the need to modify the computer program that displays the controls. For example, the controls 2s corresponding to the labels of the various boxes can be changed by simply modifying the resource file. The computer program would then be re-built (but not re-compiled). The next time the re-built computer program is executed, the program will open the resource file with the modifications and will display the modified controls.
Figures lb-ld illustrate the operation of various types of controls.
Figure lb illustrates the operation of a combobox. The combobox 107 comprises an edit box 107a and a list box 107b. When the user selects the arrow to the right of the edit box 107a, the list box 107b is displayed. The list box contains a list of the possible values that can be entered into the edit box 107a. A user can select 3s one of the possible values from the list box 107b by selecting a value with a mouse and mouse pointer or can use the keyboard to enter a value directly into the edit box 107a. Figure lc illustrates the operation of an edit box. The user can type in any information into an edit box, subject to editing performed by the underlying computer program. Figure ld illustrates the operation of a check box.
The check box 109 can be checked or unchecked by a user using a mouse and s mouse pointer.
Typical computer programs allow for persistent storage of data entered into the various controls of a property page. Such data is typically persistently stored in a file on disk. Each computer program controls the retrieving of the values from the various controls and the storing of the values to within the file. Thus, each developer of a computer program that persistently stores the values of the controls needs to develop code that implements such storing.
Typical computer programs use hard-coded values (i.e., defined in the source code) for the various list boxes, including for the list box of a i s combobox. Thus, to change the content of a list box, a developer would change and recompile the source code. Such changes of the source code are error prone and costly.
Summary of the Invention 2o The present invention provides a control method and system for altering the values of controls displayed within a window. The control system has resource information that contains a definition of each control within the window. For each control, the control system determines whether a buddy control is associated with the control. The buddy control has buddy control 2s information and preferably has no visible manifestation when the window is displayed. When the control has a buddy control, the control system retrieves the buddy control information and displays the retrieved information as part of the control. A user can then modify the definition of the buddy control by modifying the buddy control information so that when the control is subsequently displayed, the modified buddy control information is displayed. The modified buddy control information is preferably displayed without modifying the computer program that controls the displaying of the window. Also, the buddy control is s preferably adjacent to the control. Moreover, when the control is a list box, the buddy control information is a list of items to be displayed in the list box.
In another aspect the control system provides a general mechanism for passing parameter data to a computer program to affect a behavior of the computer program. The computer program has a window and resource 1o information defining controls within the window. The control system defines a parameter control within the resource information in which the parameter control has no visible affect on the display of the window and contains parameter data to be passed to the computer program. The computer program retrieves the definition of the parameter control from the resource information, extracts the t s parameter data from the retrieved definition, and performs the behavior indicated by the parameter data so that the behavior of the computer program can be changed by changing the definition of the control. The parameter data preferably contains a key for persistently storing a value for a control or contains information to be displayed when a control is displayed, such as a list of items to 2o be displayed in a list box.
Brief Description of the Drawings Figure 1 a illustrates a window that contains controls.
Figure lb illustrates the operation of a combobox.
25 Figure lc illustrates the operation of an edit box.
Figure ld illustrates the operation of a check box.
Figure 2 is a block diagram illustrating a computer system upon which the present invention may be practiced.
Figure 3 is a block diagram illustrating various data structures used in a preferred embodiment.
Figure 4 is a flow diagram of the method BaseDlgProc of the CPropPagePersistent class.
s Figure 5 is a flow diagram of the method DoCommand of the CPropPagePersistent class.
Figure 6 is a flow diagram of the method SetActive of the CPropPagePersistent class.
Figure 7 is a flow diagram of the method Display of the to CPropPagePersistent class.
Figure 8 is a flow diagram of the method Apply of the CPropPagePersistent class.
Figure 9 is a flow diagram of the method Load of the CPersistentEditControl class.
is Figure 10 is a flow diagram of the method GetAndParseBuddy of the CPersistentEditControl class.
Figure 11 is a flow diagram of the method Display of the CPersistentEditControl class.
Figure 12 is a flow diagram of the method Load of the 2o CPersistentComboControl class.
Figure 13 is a flow diagram of the method Display of the CPersistentComboControl class.
Figure 14 is a flow diagram of the method Load of the CPersistentButtonControl class.
2s Figure 15 is a flow diagram of the method Display of the CPersistentButtonControl class.
Detailed Description of the Invention The present invention provides a control method and system for persistently storing user-entered values for controls and for modifying various controls. In a preferred embodiment, the control system defines a window class s and, for each type (e.g., combobox, text box) of control, a control class.
These classes provide functionality for persistently storing control values and for modifying the content of controls. A computer program that uses the control system instantiates a window object to manage the window that contains the controls, and the window object instantiates a control object for each control to to manage the control. When the window is first displayed, the window object requests each control object to load the control value from the persistent storage.
When user indicates to apply the current control values (e.g., clicking an "OK"
button), the window object requests each control object to store the control value in the persistent storage. Thus, the control values are persistently stored and then t5 are retrieved when the window is displayed. The persistent storage is preferably the system registry provided by the Microsoft Windows~ operating system.
However, other persistent storage such as a data base or a file may be used.
To persistently store the control values, the control system preferably assigns a unique key to each control and uses that key to store and 2o retrieve the control value. In one embodiment, the unique key can include a combination of program identifier, window identifier, and control identifier.
Thus, the control system generates such a unique key when the value for a control is stored and regenerates the same key when the value is retrieved.
The generation of such a combination, however, means that the control system would 2s not be able to retrieve the value stored for a control that is moved from one window to another. In particular, before the control is moved, the control system would generate a key based on the identifier of the current window. After the control is moved, the system would generate a new key based on the identifier of g the new window. However, with this new key, the value stored with the other key cannot be retrieved. For example, the control system may assign a key of "Custom\IDC COMBOBOX1" to the combobox 107 of Figure la because its window has the title "Custom" and the combobox has an identifier of s "IDC COMBOBOX1." Thus, the value of the combobox would be stored with that key. However, if the combobox were moved to the window with the title "General," then when the general window is displayed, the key "General\IDC COMBOX1" would be generated. Using this key, the control system would try to retrieve the persistently stored value for the combobox.
to However, since the control was moved, the key is incorrect and the persistently stored value would not be retrieved.
To address this problem of incorrect key generation, the control system provides a mechanism which allows each control to be assigned a key that is independent of the window in which the control is contained. With such a ~ s window-independent key, a control can be moved to a different window and the value that was persistently stored before the control was moved can still be retrieved. The mechanism allows the window-independent key to be stored in the resource file along with the definition of the control. In one embodiment, the definition of a control can be expanded to include an indication of the key for the 20 control. For example, a parameter could be added to a line that defines a control to specify the window-independent key. Such an expansion of the definitions could be accomplished by performing a re-specification of the format of the resource file.
In a preferred embodiment, a window-independent key is specified 2s without a re-specification of the format of the resource file. The control system uses a "buddy control" associated with each control that contains the window-independent key as its text (e.g., the unique identifier in the resource file). The buddy control for a specified control is defined in the resource file as a static and a not visible text control that immediately follows the specified control.
Thus, the control object for the specified control can determine if a buddy control is defined by retrieving the next control and determining whether it is a static and a not visible text control. If a buddy control is defined, then the text of that buddy s control specifies the key that is to be used when storing and retrieving the value for the specified control. Moreover, since the buddy control is not visible, it does not affect the appearance of the window.
In addition to specifying the key, the presence or absence of buddy control can be used as a flag to indicate whether the value of a control should be to persistently stored. That is, if no buddy control is defined for a certain control, then the value for that control would not be stored persistently. Conversely, if a buddy control is defined, then the value would be persistently stored using the specified key. In general, the use of a buddy control can be used as a mechanism to provide information to the computer program about the corresponding control.
~ s Moreover, the use of a control that does not affect the appearance of a window provides a generic mechanism for providing arbitrary information to a computer program.
In certain situations, the assignment of a unique key to each control may result in an unacceptable overhead. For example, the accessing of the 2o registry may involve a disk access for each key. Thus, a preferred control system allows values for certain types of controls to be combined and stored with a single key. In one embodiment, the values for all the button controls of a window are combined and stored under a single key. However, when such values are combined, the corresponding controls cannot be readily moved to a 2s different window. Thus, the decision to implement such combining of values would entail considerations of the savings in access versus the loss in the ability to easily move controls to a different window. In a preferred embodiment, the control system can be implemented to combine all values for all controls of certain types for all windows of the computer program and to store the combined values with a single key. In this way, the control could be moved to different windows and their persistently stored values could be retrieved.
The control system also allows for the items in a list box to be s specified without hard-coding the item into the computer program. In particular, the items of a list box can be stored as the text of a buddy control. Thus, a control object for a list box can determine if a buddy control is defined. If one is defined, then the control object can fill the list box with the items indicated in the text.
1o Table 2 illustrates the use of buddy controls defined in a resource file. As illustrated in this example, the control system automatically stores all control values for comboboxes and check boxes persistently. The control system combines each of these control values and stores them with a single key. The control system uses the presence or absence of a buddy control for an edit box as Is a flag to indicate whether the value for the edit box should be persistently stored.
If a buddy control is present, then its text contains the key for use in storing and retrieving the control value for the edit box. Also, if a combobox has a buddy control, the control system interprets the text of the buddy control as containing the items for the list box of the combobox. Line 2a defines a buddy control for 2o the combobox defined in line 2. The text of this buddy control contains a list of the items for the list box of the combobox. Line 4a defines a buddy control for the edit box defined in line 4. The text of this buddy control contains the key for use when storing and retrieving the value of the edit box.
Table 2 BEGIN
1 LTEXT "ape:", IDC STATIC, [location]
2 COMBOBOX IDC_COMBO1, [location], CBS_DROPDOWNLIST, WS TABSTOP
2a LTEXT "Text\nDate\nNumberlnYes or No", IDC STATIC, [location], Not WS VISIBLE I WS DISABLED
3 LTEXT "Value:", IDC STATIC, [location), 4 EDITTEXT IDC EDIT1, [location], ES AUTOHSCROLL, WS TABSTOP
4a LTEXT "HKLM, System\\CurrentControlSet\Services\VxD\VNetSup, ComputerName, 15", IDC STATIC, [location], Not WS VISIBLE
WS DISABLED
S CONTROL "Link To Content", IDC CHECK1, "Button", BS AUTOCHECKBOX, WS TABSTOP
END
Figure 2 is a block diagram illustrating a computer system upon 2s which the present invention may be practiced. The computer system 201 comprises a central processing unit, memory, and storage devices, such as a disk drive. The computer system also includes an operating system 202, a registry 203, an application program 204, and a display 205. The control system is typically stored in a computer-readable medium, such as a disk or read-only 3o memory, from which it is loaded into memory for execution. The operating system coordinates the overall operation of the computer system and acts as an interface between the application program and the various devices, such as the display. The registry provides a centralized mechanism through which various application programs can store information persistently. In a preferred 3s embodiment, the information in a registry is hierarchically organized based on a path name (i.e., key) to the data. The registry could be implemented using a database or by storing the information in a file. The application program controls the displaying of various windows. For each window, such as a property page, the application program instantiates a window object 210 having functionality for managing display of the window. The application program also includes a control object corresponding to each control on the window for managing the control. The present invention is preferably implemented as various C++ class, s which define the window and control objects.
Figure 3 is a block diagram illustrating various data structures used in a preferred embodiment. In the following, the invention is described based upon an implementation of the window as a property page. Windowing systems, such as Windows, define standard window and control classes to control the to standard operation of the windows and controls, and in particular, a property page and its controls. In a preferred embodiment, the window and control classes of the control system inherit these defined classes and add functionality to implement the various aspects of the invention. In one embodiment, each property page has a corresponding CPropPagePersistent object 301 in memory, t5 which is an instance of the CPropPagePersistent class that inherits the standard property page class. The CPropPagePersistent object contains a pointer to a list of CPersistentControl objects. Each control within the property page has a corresponding CPersistentControl object which is an instance of the CPersistentControl class that inherits the standard control class. The 2o CPersistentControl class is subclassed based on control type: edit box (CPersistentEditControl), combobox (CPersistentComboControl), and button (CPersistentButtonControl). That is, one subclass corresponds to an edit box, another subclass corresponds to a combobox, and the other subclass corresponds to a button. The CPropPagePersistent object also contains a pointer to registry 2s data 303. The registry data 303 contains information to be stored in the registry at a single key. In this example, the values for each combobox and button on the property page are combined and stored with a single key. Thus, all the combobox and button values for a single property page are stored with one key.
When a CPropPagePersistent object directs a CPersistentComboControl or CPersistentButtonControl object to persistently store its value, the object stores its value in a registry value structure 304. After the CPropPagePersistent object directs all the control objects to persistently store their values, the CPropPagePersistent object combines and persistently stores all the control values in the registry value structure 304. Each CPersistentEditControl object contains a pointer to registry data 306. The registry data 306 contains the unique key that was retrieved from the buddy control, if present, for the corresponding CPersistentEditControl object.
to Figures 4-8 illustrate flow diagrams for various methods of the CPropPagePersistent class. The CPropPagePersistent class has a method BaseDlgProc for processing window messages sent to the property page window, a method DoCommand for indicating that the value of a control has changed, a method SetActive for initializing the values of the controls to the persistently is stored values, a method Display for displaying the property page, and a method Apply for persistently storing the values of the controls. The CPropPagePersistent class contains a data member indicating whether a value of a control has changed and thus indicating whether the values need to be persistently stored.
20 Figure 4 is a flow diagram of the method BaseDlgProc of the CPropPagePersistent class. The method serves as a window procedure for the property page window. The method is passed various messages and processes the messages. The method receives an initialization message ("WM INIT") indicating that the property page should be initialized, a command message 25 ("WM COMMAND") indicating that a value of a control has been changed, and a notify message ("WM NOTIFY'') indicating whether the property page is being displayed for the first time ("SETACTIVE"), whether the OK button has been selected ("APPLY"), or whether the cancel button has been selected (''QUERYCANCEL"). The implementation of this method is preferably inherited from the standard property page class. In step 401, if the message is an initialize message, the method continues at step 402, else the method continues at step 404. In steps 404-406, the method stores the passed handle for the window s associated for this object and clears the changed and initialization flags.
This passed handle is stored so that the other methods of the CPropPagePersistent object can identify the corresponding property page window. In step 402, if the message is a command message, then the method continues at step 407, else the method continues at step 409. In step 407, the method calls the method to DoCommand of this CPropPagePersistent object and returns. In step 409, if the message is a notify message, then the method continues at step 410, else the method returns. In step 410, if the notify is an APPLY message, then the method continues at step 411. If the message is a SETACTIVE message, then the method continues at step 414. If the message is a QUERYCANCEL message, is then the method continues at step 416. In step 411, if a control value of the property page has been changed, then the changes are to be persistently stored and the method continues at step 412, else the method returns. In step 412, the method invokes the method Apply of this CPropPagePersistent object to store the control values in the registry. In step 413, the method clears the changed flag to 2o indicate that the control values have not changed since being last persistently stored and then returns. In step 414, the method invokes the method SetActive of this CPropPagePersistent object. In step 415, the method sets the initialization flag to indicate that the property page has been initialized and then returns.
In step 416, the method invokes the method QueryCancel of this 2s CPropPagePersistent object and then returns.
Figure 5 is a flow diagram of the method DoCommand of the CPropPagePersistent class. The method sets the change flag if a value of a control has changed. In step 501, if a control value has changed as indicated by l~
the message received by the property page window procedure, then the method sets the change flag in step 502. The method then returns.
Figure 6 is a flow diagram of the method SetActive of the CPropPagePersistent class. This method manages the retrieving of the s persistently stored value for each control of the property page, the initializing of the controls of the property page with the retrieved values, the initializing of the list boxes, and the displaying of the controls. Initially. the method checks the initialize flag to determine whether this CPropPagePersistent object has already been initialized and returns if it has been. In steps 601-604, the method loops to creating a CPersistentControl object for each control of the property page of the appropriate subclass. In step 601., the method selects a control of the property page starting with the first. In step 602, if all the controls have already been selected, then the method continues at step 605, else the method continues at step 603. In step 603, the method creates a CPersistentControl object of the 1s appropriate subclass for the type of the selected control. In step 604, the procedure adds the created CPersistentControl object to the list of control objects maintained by the CPropPagePersistent object. In steps 605-607, the method loops selecting each control object and directing the CPersistentControl object to load its value from persistent storage. In step 605, the method selects the next 2o CPersistentControl object starting with the first. In step 606, if all the CPersistentControl objects have already been selected, then the method continues at step 608, else the method continues at step 607. In step 607, the method invokes the method Load of the selected CPersistentControl object and loops to step 605 to select the next CPersistentControl object. In step 608, the method 2s loads from the registry all the values that were combined together to store with a single key for the property page. In step 609, the method invokes the method Display of this CPropPagePersistent object to display the controls and then returns.
Figure 7 is a flow diagram of the method Display of the CPropPagePersistent class. The method loops selecting each CPersistentControl object and invokes its method Display. In step 701, the method selects the next CPersistentControl object starting with the first. In step 702, if all the s CPersistentControl objects have already been selected, then the method returns, else the method continues at step 703. In step 703, the method invokes the method Display of the selected CPersistentControl object and loops to step 701 to select the next CPersistentControl object.
Figure 8 is a flow diagram of the method Apply of the to CPropPagePersistent class. The method loops selecting each CPersistentControl object and invokes its method Save to persistently store its value. In step 801, the method selects the next CPersistentControl object starting with the first.
In step 802, if all the CPersistentControl objects have already been selected, then the method continues at step 804, else the method continues at step 803. In step is 803, the method invokes the method Save of the selected CPersistentControl object and loops to step 801 to select the next CPersistentControl object. In step 804, the method stores in the registry all the values combined together and then returns. When the method Save is invoked in step 803 for a combobox or a button control, that method Save stored the control value in a registry value 2o structure 304 so that the CPropPagePersistent object could access and combine the control values for persistent storage.
Figure 9 is a flow diagram of the method Load of the CPersistentEditControl class. This method parses the text of the buddy control, if present, to determine the key for this control. The method then retrieves the 2s value from the registry and initializes the control to that retrieved value. (The method Save of the CPersistentControl subclasses operate in an analogous manner to the method Load for the subclasses.) In step 901, the method retrieves the definition of the next control from the resource file. In step 902, if the next control is a buddy control, then the method continues at step 903, else the method returns. In step 903, the method invokes the method GetAndParseBuddy of this CPersistentEditControl object to identify the-key for this control. In step 904, the method retrieves the control value from the registry using the key. In step 905, s the method sets the text in the control to the retrieved value and returns.
Figure 10 is a flow diagram of the method GetAndParseBuddy of the CPersistentEditControl class. The method retrieves the text associated with the buddy control and parses the text to identify the key. In step 1001, the method retrieves the text for the buddy control. In step 1002, the method parses to the key from the text. In step 1003, the method stores the key and returns.
Figure 11 is a flow diagram of the display method of the CPersistentEditControl class. This method simply returns. The display is handled when the text is loaded.
Figure 12 is a flow diagram of the method Load of the is CPersistentComboControl class. If a combobox has a buddy control, then that buddy control contains a list of the items for the list box of the combobox.
In step 1201, the method retrieves the next control. In step 1202, if the next control is a buddy control, then the method continues at step 1203, else the method returns. In step 1203, the method retrieves the text for the buddy control. In step 20 1204, the method adds the identification of this CPersistentComboControl object to a registry value structure 304 so that the CPropPagePersistent object can retrieve its value from the combined values. The stored values for a combobox is preferably an index into the list of items.
Figure 13 is a flow diagram of the method Display of the 2s CPersistentComboControl class. This method fills the listbox based on the window text of the buddy control of this CPersistentComboControl object and sets its value to the value retrieved from the combined values by the CPropPagePersistent object. In step 1301, the method resets the edit box and list box of the combobox. In step 1302, the method fills the list box with the list of items from the buddy control. In step 1303, the method retrieves the value for the edit box from a registry value structure 304. In step 1304, the method sets the retrieve value into the edit box and returns.
Figure 14 is a flow diagram of the method Load of the CPersistentButtonControl class. This method determines whether the control is a check box, and, if so, adds its identifier to a registry value structure 304 so that the CPropPagePersistent object can retrieve its value. In step 1401, the method retrieves the style of the window from the resource file. In step 1402, if the to control is a check box, then the method continues at step 1403, else the method returns. In step 1403, the method adds the identifier of the control to a registry value structure and returns.
Figure 15 is a flow diagram of the method Display of the CPersistentButtonControl class. This method retrieves its value from a registry is value structure 304 and sets the check box accordingly. In step 1501, the method retrieves the registry value. In step 1502, the method sets the check box to the retrieved value and returns.
Although the present invention has been described in terms of a preferred embodiment, it is not intended that the invention be limited to these 2o embodiments. Modifications within the spirit of the invention will be apparent to those skilled in the art. The scope of the present invention is defined by the claims that follow.
is s CONTROL "Link To Content", IDC CHECK1, "Button", [location]
BS AUTOCHECKBOX, WS TABSTOP
END
The use of resource files allows for various changes to be made to the arrangement and content of the controls without the need to modify the computer program that displays the controls. For example, the controls 2s corresponding to the labels of the various boxes can be changed by simply modifying the resource file. The computer program would then be re-built (but not re-compiled). The next time the re-built computer program is executed, the program will open the resource file with the modifications and will display the modified controls.
Figures lb-ld illustrate the operation of various types of controls.
Figure lb illustrates the operation of a combobox. The combobox 107 comprises an edit box 107a and a list box 107b. When the user selects the arrow to the right of the edit box 107a, the list box 107b is displayed. The list box contains a list of the possible values that can be entered into the edit box 107a. A user can select 3s one of the possible values from the list box 107b by selecting a value with a mouse and mouse pointer or can use the keyboard to enter a value directly into the edit box 107a. Figure lc illustrates the operation of an edit box. The user can type in any information into an edit box, subject to editing performed by the underlying computer program. Figure ld illustrates the operation of a check box.
The check box 109 can be checked or unchecked by a user using a mouse and s mouse pointer.
Typical computer programs allow for persistent storage of data entered into the various controls of a property page. Such data is typically persistently stored in a file on disk. Each computer program controls the retrieving of the values from the various controls and the storing of the values to within the file. Thus, each developer of a computer program that persistently stores the values of the controls needs to develop code that implements such storing.
Typical computer programs use hard-coded values (i.e., defined in the source code) for the various list boxes, including for the list box of a i s combobox. Thus, to change the content of a list box, a developer would change and recompile the source code. Such changes of the source code are error prone and costly.
Summary of the Invention 2o The present invention provides a control method and system for altering the values of controls displayed within a window. The control system has resource information that contains a definition of each control within the window. For each control, the control system determines whether a buddy control is associated with the control. The buddy control has buddy control 2s information and preferably has no visible manifestation when the window is displayed. When the control has a buddy control, the control system retrieves the buddy control information and displays the retrieved information as part of the control. A user can then modify the definition of the buddy control by modifying the buddy control information so that when the control is subsequently displayed, the modified buddy control information is displayed. The modified buddy control information is preferably displayed without modifying the computer program that controls the displaying of the window. Also, the buddy control is s preferably adjacent to the control. Moreover, when the control is a list box, the buddy control information is a list of items to be displayed in the list box.
In another aspect the control system provides a general mechanism for passing parameter data to a computer program to affect a behavior of the computer program. The computer program has a window and resource 1o information defining controls within the window. The control system defines a parameter control within the resource information in which the parameter control has no visible affect on the display of the window and contains parameter data to be passed to the computer program. The computer program retrieves the definition of the parameter control from the resource information, extracts the t s parameter data from the retrieved definition, and performs the behavior indicated by the parameter data so that the behavior of the computer program can be changed by changing the definition of the control. The parameter data preferably contains a key for persistently storing a value for a control or contains information to be displayed when a control is displayed, such as a list of items to 2o be displayed in a list box.
Brief Description of the Drawings Figure 1 a illustrates a window that contains controls.
Figure lb illustrates the operation of a combobox.
25 Figure lc illustrates the operation of an edit box.
Figure ld illustrates the operation of a check box.
Figure 2 is a block diagram illustrating a computer system upon which the present invention may be practiced.
Figure 3 is a block diagram illustrating various data structures used in a preferred embodiment.
Figure 4 is a flow diagram of the method BaseDlgProc of the CPropPagePersistent class.
s Figure 5 is a flow diagram of the method DoCommand of the CPropPagePersistent class.
Figure 6 is a flow diagram of the method SetActive of the CPropPagePersistent class.
Figure 7 is a flow diagram of the method Display of the to CPropPagePersistent class.
Figure 8 is a flow diagram of the method Apply of the CPropPagePersistent class.
Figure 9 is a flow diagram of the method Load of the CPersistentEditControl class.
is Figure 10 is a flow diagram of the method GetAndParseBuddy of the CPersistentEditControl class.
Figure 11 is a flow diagram of the method Display of the CPersistentEditControl class.
Figure 12 is a flow diagram of the method Load of the 2o CPersistentComboControl class.
Figure 13 is a flow diagram of the method Display of the CPersistentComboControl class.
Figure 14 is a flow diagram of the method Load of the CPersistentButtonControl class.
2s Figure 15 is a flow diagram of the method Display of the CPersistentButtonControl class.
Detailed Description of the Invention The present invention provides a control method and system for persistently storing user-entered values for controls and for modifying various controls. In a preferred embodiment, the control system defines a window class s and, for each type (e.g., combobox, text box) of control, a control class.
These classes provide functionality for persistently storing control values and for modifying the content of controls. A computer program that uses the control system instantiates a window object to manage the window that contains the controls, and the window object instantiates a control object for each control to to manage the control. When the window is first displayed, the window object requests each control object to load the control value from the persistent storage.
When user indicates to apply the current control values (e.g., clicking an "OK"
button), the window object requests each control object to store the control value in the persistent storage. Thus, the control values are persistently stored and then t5 are retrieved when the window is displayed. The persistent storage is preferably the system registry provided by the Microsoft Windows~ operating system.
However, other persistent storage such as a data base or a file may be used.
To persistently store the control values, the control system preferably assigns a unique key to each control and uses that key to store and 2o retrieve the control value. In one embodiment, the unique key can include a combination of program identifier, window identifier, and control identifier.
Thus, the control system generates such a unique key when the value for a control is stored and regenerates the same key when the value is retrieved.
The generation of such a combination, however, means that the control system would 2s not be able to retrieve the value stored for a control that is moved from one window to another. In particular, before the control is moved, the control system would generate a key based on the identifier of the current window. After the control is moved, the system would generate a new key based on the identifier of g the new window. However, with this new key, the value stored with the other key cannot be retrieved. For example, the control system may assign a key of "Custom\IDC COMBOBOX1" to the combobox 107 of Figure la because its window has the title "Custom" and the combobox has an identifier of s "IDC COMBOBOX1." Thus, the value of the combobox would be stored with that key. However, if the combobox were moved to the window with the title "General," then when the general window is displayed, the key "General\IDC COMBOX1" would be generated. Using this key, the control system would try to retrieve the persistently stored value for the combobox.
to However, since the control was moved, the key is incorrect and the persistently stored value would not be retrieved.
To address this problem of incorrect key generation, the control system provides a mechanism which allows each control to be assigned a key that is independent of the window in which the control is contained. With such a ~ s window-independent key, a control can be moved to a different window and the value that was persistently stored before the control was moved can still be retrieved. The mechanism allows the window-independent key to be stored in the resource file along with the definition of the control. In one embodiment, the definition of a control can be expanded to include an indication of the key for the 20 control. For example, a parameter could be added to a line that defines a control to specify the window-independent key. Such an expansion of the definitions could be accomplished by performing a re-specification of the format of the resource file.
In a preferred embodiment, a window-independent key is specified 2s without a re-specification of the format of the resource file. The control system uses a "buddy control" associated with each control that contains the window-independent key as its text (e.g., the unique identifier in the resource file). The buddy control for a specified control is defined in the resource file as a static and a not visible text control that immediately follows the specified control.
Thus, the control object for the specified control can determine if a buddy control is defined by retrieving the next control and determining whether it is a static and a not visible text control. If a buddy control is defined, then the text of that buddy s control specifies the key that is to be used when storing and retrieving the value for the specified control. Moreover, since the buddy control is not visible, it does not affect the appearance of the window.
In addition to specifying the key, the presence or absence of buddy control can be used as a flag to indicate whether the value of a control should be to persistently stored. That is, if no buddy control is defined for a certain control, then the value for that control would not be stored persistently. Conversely, if a buddy control is defined, then the value would be persistently stored using the specified key. In general, the use of a buddy control can be used as a mechanism to provide information to the computer program about the corresponding control.
~ s Moreover, the use of a control that does not affect the appearance of a window provides a generic mechanism for providing arbitrary information to a computer program.
In certain situations, the assignment of a unique key to each control may result in an unacceptable overhead. For example, the accessing of the 2o registry may involve a disk access for each key. Thus, a preferred control system allows values for certain types of controls to be combined and stored with a single key. In one embodiment, the values for all the button controls of a window are combined and stored under a single key. However, when such values are combined, the corresponding controls cannot be readily moved to a 2s different window. Thus, the decision to implement such combining of values would entail considerations of the savings in access versus the loss in the ability to easily move controls to a different window. In a preferred embodiment, the control system can be implemented to combine all values for all controls of certain types for all windows of the computer program and to store the combined values with a single key. In this way, the control could be moved to different windows and their persistently stored values could be retrieved.
The control system also allows for the items in a list box to be s specified without hard-coding the item into the computer program. In particular, the items of a list box can be stored as the text of a buddy control. Thus, a control object for a list box can determine if a buddy control is defined. If one is defined, then the control object can fill the list box with the items indicated in the text.
1o Table 2 illustrates the use of buddy controls defined in a resource file. As illustrated in this example, the control system automatically stores all control values for comboboxes and check boxes persistently. The control system combines each of these control values and stores them with a single key. The control system uses the presence or absence of a buddy control for an edit box as Is a flag to indicate whether the value for the edit box should be persistently stored.
If a buddy control is present, then its text contains the key for use in storing and retrieving the control value for the edit box. Also, if a combobox has a buddy control, the control system interprets the text of the buddy control as containing the items for the list box of the combobox. Line 2a defines a buddy control for 2o the combobox defined in line 2. The text of this buddy control contains a list of the items for the list box of the combobox. Line 4a defines a buddy control for the edit box defined in line 4. The text of this buddy control contains the key for use when storing and retrieving the value of the edit box.
Table 2 BEGIN
1 LTEXT "ape:", IDC STATIC, [location]
2 COMBOBOX IDC_COMBO1, [location], CBS_DROPDOWNLIST, WS TABSTOP
2a LTEXT "Text\nDate\nNumberlnYes or No", IDC STATIC, [location], Not WS VISIBLE I WS DISABLED
3 LTEXT "Value:", IDC STATIC, [location), 4 EDITTEXT IDC EDIT1, [location], ES AUTOHSCROLL, WS TABSTOP
4a LTEXT "HKLM, System\\CurrentControlSet\Services\VxD\VNetSup, ComputerName, 15", IDC STATIC, [location], Not WS VISIBLE
WS DISABLED
S CONTROL "Link To Content", IDC CHECK1, "Button", BS AUTOCHECKBOX, WS TABSTOP
END
Figure 2 is a block diagram illustrating a computer system upon 2s which the present invention may be practiced. The computer system 201 comprises a central processing unit, memory, and storage devices, such as a disk drive. The computer system also includes an operating system 202, a registry 203, an application program 204, and a display 205. The control system is typically stored in a computer-readable medium, such as a disk or read-only 3o memory, from which it is loaded into memory for execution. The operating system coordinates the overall operation of the computer system and acts as an interface between the application program and the various devices, such as the display. The registry provides a centralized mechanism through which various application programs can store information persistently. In a preferred 3s embodiment, the information in a registry is hierarchically organized based on a path name (i.e., key) to the data. The registry could be implemented using a database or by storing the information in a file. The application program controls the displaying of various windows. For each window, such as a property page, the application program instantiates a window object 210 having functionality for managing display of the window. The application program also includes a control object corresponding to each control on the window for managing the control. The present invention is preferably implemented as various C++ class, s which define the window and control objects.
Figure 3 is a block diagram illustrating various data structures used in a preferred embodiment. In the following, the invention is described based upon an implementation of the window as a property page. Windowing systems, such as Windows, define standard window and control classes to control the to standard operation of the windows and controls, and in particular, a property page and its controls. In a preferred embodiment, the window and control classes of the control system inherit these defined classes and add functionality to implement the various aspects of the invention. In one embodiment, each property page has a corresponding CPropPagePersistent object 301 in memory, t5 which is an instance of the CPropPagePersistent class that inherits the standard property page class. The CPropPagePersistent object contains a pointer to a list of CPersistentControl objects. Each control within the property page has a corresponding CPersistentControl object which is an instance of the CPersistentControl class that inherits the standard control class. The 2o CPersistentControl class is subclassed based on control type: edit box (CPersistentEditControl), combobox (CPersistentComboControl), and button (CPersistentButtonControl). That is, one subclass corresponds to an edit box, another subclass corresponds to a combobox, and the other subclass corresponds to a button. The CPropPagePersistent object also contains a pointer to registry 2s data 303. The registry data 303 contains information to be stored in the registry at a single key. In this example, the values for each combobox and button on the property page are combined and stored with a single key. Thus, all the combobox and button values for a single property page are stored with one key.
When a CPropPagePersistent object directs a CPersistentComboControl or CPersistentButtonControl object to persistently store its value, the object stores its value in a registry value structure 304. After the CPropPagePersistent object directs all the control objects to persistently store their values, the CPropPagePersistent object combines and persistently stores all the control values in the registry value structure 304. Each CPersistentEditControl object contains a pointer to registry data 306. The registry data 306 contains the unique key that was retrieved from the buddy control, if present, for the corresponding CPersistentEditControl object.
to Figures 4-8 illustrate flow diagrams for various methods of the CPropPagePersistent class. The CPropPagePersistent class has a method BaseDlgProc for processing window messages sent to the property page window, a method DoCommand for indicating that the value of a control has changed, a method SetActive for initializing the values of the controls to the persistently is stored values, a method Display for displaying the property page, and a method Apply for persistently storing the values of the controls. The CPropPagePersistent class contains a data member indicating whether a value of a control has changed and thus indicating whether the values need to be persistently stored.
20 Figure 4 is a flow diagram of the method BaseDlgProc of the CPropPagePersistent class. The method serves as a window procedure for the property page window. The method is passed various messages and processes the messages. The method receives an initialization message ("WM INIT") indicating that the property page should be initialized, a command message 25 ("WM COMMAND") indicating that a value of a control has been changed, and a notify message ("WM NOTIFY'') indicating whether the property page is being displayed for the first time ("SETACTIVE"), whether the OK button has been selected ("APPLY"), or whether the cancel button has been selected (''QUERYCANCEL"). The implementation of this method is preferably inherited from the standard property page class. In step 401, if the message is an initialize message, the method continues at step 402, else the method continues at step 404. In steps 404-406, the method stores the passed handle for the window s associated for this object and clears the changed and initialization flags.
This passed handle is stored so that the other methods of the CPropPagePersistent object can identify the corresponding property page window. In step 402, if the message is a command message, then the method continues at step 407, else the method continues at step 409. In step 407, the method calls the method to DoCommand of this CPropPagePersistent object and returns. In step 409, if the message is a notify message, then the method continues at step 410, else the method returns. In step 410, if the notify is an APPLY message, then the method continues at step 411. If the message is a SETACTIVE message, then the method continues at step 414. If the message is a QUERYCANCEL message, is then the method continues at step 416. In step 411, if a control value of the property page has been changed, then the changes are to be persistently stored and the method continues at step 412, else the method returns. In step 412, the method invokes the method Apply of this CPropPagePersistent object to store the control values in the registry. In step 413, the method clears the changed flag to 2o indicate that the control values have not changed since being last persistently stored and then returns. In step 414, the method invokes the method SetActive of this CPropPagePersistent object. In step 415, the method sets the initialization flag to indicate that the property page has been initialized and then returns.
In step 416, the method invokes the method QueryCancel of this 2s CPropPagePersistent object and then returns.
Figure 5 is a flow diagram of the method DoCommand of the CPropPagePersistent class. The method sets the change flag if a value of a control has changed. In step 501, if a control value has changed as indicated by l~
the message received by the property page window procedure, then the method sets the change flag in step 502. The method then returns.
Figure 6 is a flow diagram of the method SetActive of the CPropPagePersistent class. This method manages the retrieving of the s persistently stored value for each control of the property page, the initializing of the controls of the property page with the retrieved values, the initializing of the list boxes, and the displaying of the controls. Initially. the method checks the initialize flag to determine whether this CPropPagePersistent object has already been initialized and returns if it has been. In steps 601-604, the method loops to creating a CPersistentControl object for each control of the property page of the appropriate subclass. In step 601., the method selects a control of the property page starting with the first. In step 602, if all the controls have already been selected, then the method continues at step 605, else the method continues at step 603. In step 603, the method creates a CPersistentControl object of the 1s appropriate subclass for the type of the selected control. In step 604, the procedure adds the created CPersistentControl object to the list of control objects maintained by the CPropPagePersistent object. In steps 605-607, the method loops selecting each control object and directing the CPersistentControl object to load its value from persistent storage. In step 605, the method selects the next 2o CPersistentControl object starting with the first. In step 606, if all the CPersistentControl objects have already been selected, then the method continues at step 608, else the method continues at step 607. In step 607, the method invokes the method Load of the selected CPersistentControl object and loops to step 605 to select the next CPersistentControl object. In step 608, the method 2s loads from the registry all the values that were combined together to store with a single key for the property page. In step 609, the method invokes the method Display of this CPropPagePersistent object to display the controls and then returns.
Figure 7 is a flow diagram of the method Display of the CPropPagePersistent class. The method loops selecting each CPersistentControl object and invokes its method Display. In step 701, the method selects the next CPersistentControl object starting with the first. In step 702, if all the s CPersistentControl objects have already been selected, then the method returns, else the method continues at step 703. In step 703, the method invokes the method Display of the selected CPersistentControl object and loops to step 701 to select the next CPersistentControl object.
Figure 8 is a flow diagram of the method Apply of the to CPropPagePersistent class. The method loops selecting each CPersistentControl object and invokes its method Save to persistently store its value. In step 801, the method selects the next CPersistentControl object starting with the first.
In step 802, if all the CPersistentControl objects have already been selected, then the method continues at step 804, else the method continues at step 803. In step is 803, the method invokes the method Save of the selected CPersistentControl object and loops to step 801 to select the next CPersistentControl object. In step 804, the method stores in the registry all the values combined together and then returns. When the method Save is invoked in step 803 for a combobox or a button control, that method Save stored the control value in a registry value 2o structure 304 so that the CPropPagePersistent object could access and combine the control values for persistent storage.
Figure 9 is a flow diagram of the method Load of the CPersistentEditControl class. This method parses the text of the buddy control, if present, to determine the key for this control. The method then retrieves the 2s value from the registry and initializes the control to that retrieved value. (The method Save of the CPersistentControl subclasses operate in an analogous manner to the method Load for the subclasses.) In step 901, the method retrieves the definition of the next control from the resource file. In step 902, if the next control is a buddy control, then the method continues at step 903, else the method returns. In step 903, the method invokes the method GetAndParseBuddy of this CPersistentEditControl object to identify the-key for this control. In step 904, the method retrieves the control value from the registry using the key. In step 905, s the method sets the text in the control to the retrieved value and returns.
Figure 10 is a flow diagram of the method GetAndParseBuddy of the CPersistentEditControl class. The method retrieves the text associated with the buddy control and parses the text to identify the key. In step 1001, the method retrieves the text for the buddy control. In step 1002, the method parses to the key from the text. In step 1003, the method stores the key and returns.
Figure 11 is a flow diagram of the display method of the CPersistentEditControl class. This method simply returns. The display is handled when the text is loaded.
Figure 12 is a flow diagram of the method Load of the is CPersistentComboControl class. If a combobox has a buddy control, then that buddy control contains a list of the items for the list box of the combobox.
In step 1201, the method retrieves the next control. In step 1202, if the next control is a buddy control, then the method continues at step 1203, else the method returns. In step 1203, the method retrieves the text for the buddy control. In step 20 1204, the method adds the identification of this CPersistentComboControl object to a registry value structure 304 so that the CPropPagePersistent object can retrieve its value from the combined values. The stored values for a combobox is preferably an index into the list of items.
Figure 13 is a flow diagram of the method Display of the 2s CPersistentComboControl class. This method fills the listbox based on the window text of the buddy control of this CPersistentComboControl object and sets its value to the value retrieved from the combined values by the CPropPagePersistent object. In step 1301, the method resets the edit box and list box of the combobox. In step 1302, the method fills the list box with the list of items from the buddy control. In step 1303, the method retrieves the value for the edit box from a registry value structure 304. In step 1304, the method sets the retrieve value into the edit box and returns.
Figure 14 is a flow diagram of the method Load of the CPersistentButtonControl class. This method determines whether the control is a check box, and, if so, adds its identifier to a registry value structure 304 so that the CPropPagePersistent object can retrieve its value. In step 1401, the method retrieves the style of the window from the resource file. In step 1402, if the to control is a check box, then the method continues at step 1403, else the method returns. In step 1403, the method adds the identifier of the control to a registry value structure and returns.
Figure 15 is a flow diagram of the method Display of the CPersistentButtonControl class. This method retrieves its value from a registry is value structure 304 and sets the check box accordingly. In step 1501, the method retrieves the registry value. In step 1502, the method sets the check box to the retrieved value and returns.
Although the present invention has been described in terms of a preferred embodiment, it is not intended that the invention be limited to these 2o embodiments. Modifications within the spirit of the invention will be apparent to those skilled in the art. The scope of the present invention is defined by the claims that follow.
Claims (9)
1. In a computer system, a method for specifying a user interface comprising at least one displayed control for display in a window, the method comprising:
at development time of the user interface, specifying a first control definition in a format for defining a user interface element and defining the at least one displayed control for display in a window, wherein the at least one displayed control has a display method for displaying itself at runtime; and at development time of the user interface, specifying a second control definition in a format for defining a user interface element and defining information for use by the display method of the displayed control specified by the first control definition at run time of the user interface, wherein the second control definition defines a control not to be presented in the user interface as a control at run time of the user interface.
at development time of the user interface, specifying a first control definition in a format for defining a user interface element and defining the at least one displayed control for display in a window, wherein the at least one displayed control has a display method for displaying itself at runtime; and at development time of the user interface, specifying a second control definition in a format for defining a user interface element and defining information for use by the display method of the displayed control specified by the first control definition at run time of the user interface, wherein the second control definition defines a control not to be presented in the user interface as a control at run time of the user interface.
2. A computer readable medium containing computer executable instructions for performing the method of claim 1.
3. The method of claim 1 wherein the user interface is displayed by a computer program that controls displaying the window; and the second control definition defining information for assisting in presentation of the displayed control specified by the first control definition at run time of the user interface is modifiable to modify behavior of the at least one displayed control specified by the first control definition for display in a window without modifying the computer program that controls displaying the window.
4. The method of claim 1 wherein the second control definition comprises a text parameter, wherein the text parameter comprises the information for assisting in presentation of the displayed control specified by the first control definition at run time of the user interface.
5. The method of claim 1 wherein the second control definition is specified by defining an invisible, static, and disabled control.
6. The method of claim 1 wherein the information defined by the second control definition for assisting in presentation of the displayed control specified by the first control definition at run time of the user interface comprises a list of choices associated with the displayed control specified by the first control definition for presentation in the user interface at run time.
7. The method of claim 6 wherein the first control definition defines a combobox control having a set of items for presentation in the window at run time of the user interface and the second control definition specifies the set of items.
8. A computer-implemented method for presenting a property page as part of a computer program, the method comprising:
at development time of the computer program, specifying in a resource file a first control definition defining a combobox for presentation on the property page at runtime of the computer program;
at development time of the computer program, in the resource file, immediately following the first control definition, specifying a second control definition defining an invisible, static, disabled control comprising information specifying choices to be presented in association with the combobox on the property page, wherein the invisible, static, disabled control is never presented as a control; and at runtime of the computer program, presenting the property page with the combobox having the choices specified by the second control definition without ever presenting the invisible, static, disabled control as a control.
at development time of the computer program, specifying in a resource file a first control definition defining a combobox for presentation on the property page at runtime of the computer program;
at development time of the computer program, in the resource file, immediately following the first control definition, specifying a second control definition defining an invisible, static, disabled control comprising information specifying choices to be presented in association with the combobox on the property page, wherein the invisible, static, disabled control is never presented as a control; and at runtime of the computer program, presenting the property page with the combobox having the choices specified by the second control definition without ever presenting the invisible, static, disabled control as a control.
9. A computer readable medium containing computer executable instructions for performing the method of claim 8.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CA002475002A CA2475002C (en) | 1996-12-09 | 1997-10-17 | Method and system for automatic persistence of controls in a windowing environment |
Applications Claiming Priority (2)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| US08/762,237 | 1996-12-09 | ||
| US08/762,237 US6121964A (en) | 1996-12-09 | 1996-12-09 | Method and system for automatic persistence of controls in a windowing environment |
Related Child Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CA002475002A Division CA2475002C (en) | 1996-12-09 | 1997-10-17 | Method and system for automatic persistence of controls in a windowing environment |
Publications (2)
| Publication Number | Publication Date |
|---|---|
| CA2218593A1 CA2218593A1 (en) | 1998-06-09 |
| CA2218593C true CA2218593C (en) | 2004-11-30 |
Family
ID=25064486
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CA002218593A Expired - Lifetime CA2218593C (en) | 1996-12-09 | 1997-10-17 | Method and system for automatic persistence of controls in a windowing environment |
Country Status (4)
| Country | Link |
|---|---|
| US (2) | US6121964A (en) |
| EP (2) | EP0851345B1 (en) |
| JP (1) | JP4053637B2 (en) |
| CA (1) | CA2218593C (en) |
Families Citing this family (27)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| US6182092B1 (en) * | 1997-07-14 | 2001-01-30 | Microsoft Corporation | Method and system for converting between structured language elements and objects embeddable in a document |
| US6473102B1 (en) * | 1998-05-11 | 2002-10-29 | Apple Computer, Inc. | Method and system for automatically resizing and repositioning windows in response to changes in display |
| US7062773B1 (en) * | 1998-07-20 | 2006-06-13 | International Business Machines Corporation | System and method for providing graphical user interface control enhancers |
| US7017143B1 (en) | 1999-12-01 | 2006-03-21 | Microsoft Corporation | External resource files for application development and management |
| US7243335B1 (en) | 2000-02-17 | 2007-07-10 | Microsoft Corporation | Method and system for reducing coding complexity by providing intelligent manipulable defaults |
| US7568152B1 (en) * | 2000-07-14 | 2009-07-28 | International Business Machines Corporation | Text file interface support in an object oriented application |
| US7086067B1 (en) | 2000-07-14 | 2006-08-01 | International Business Machines Corporation | Dynamic Java bean for VisualAge for Java |
| US6766475B2 (en) * | 2001-01-04 | 2004-07-20 | International Business Machines Corporation | Method and apparatus for exercising an unknown program with a graphical user interface |
| US20030030675A1 (en) * | 2001-08-09 | 2003-02-13 | International Business Machines Corporation | Entry panel processing system |
| US7240326B2 (en) * | 2002-01-14 | 2007-07-03 | International Business Machines Corporation | System and method for obtaining display names from management models |
| US20030135661A1 (en) * | 2002-01-14 | 2003-07-17 | International Business Machines Corporation | System and method for packaging and installing management models with specific console interfaces |
| US7065744B2 (en) * | 2002-01-14 | 2006-06-20 | International Business Machines Corporation | System and method for converting management models to specific console interfaces |
| US7191404B2 (en) * | 2002-01-14 | 2007-03-13 | International Business Machines Corporation | System and method for mapping management objects to console neutral user interface |
| US7177793B2 (en) * | 2002-01-14 | 2007-02-13 | International Business Machines Corporation | System and method for managing translatable strings displayed on console interfaces |
| US8166101B2 (en) | 2003-08-21 | 2012-04-24 | Microsoft Corporation | Systems and methods for the implementation of a synchronization schemas for units of information manageable by a hardware/software interface system |
| US8238696B2 (en) | 2003-08-21 | 2012-08-07 | Microsoft Corporation | Systems and methods for the implementation of a digital images schema for organizing units of information manageable by a hardware/software interface system |
| US20050091181A1 (en) * | 2003-10-23 | 2005-04-28 | Mckee Timothy P. | System and method for the presentation of items stored on a computer |
| US7730073B2 (en) * | 2003-10-23 | 2010-06-01 | Microsoft Corporation | System and a method for presenting related items to a user |
| US7908562B2 (en) * | 2003-10-23 | 2011-03-15 | Microsoft Corporation | System and a method for presenting items to a user with a contextual presentation |
| US7546542B2 (en) * | 2004-03-23 | 2009-06-09 | Microsoft Corporation | User interface incorporating graphically based management of controls |
| US20070143678A1 (en) * | 2005-12-21 | 2007-06-21 | Feigenbaum Barry A | Method and apparatus for persistently resolving events to event source |
| US20080109466A1 (en) * | 2006-11-02 | 2008-05-08 | Microsoft Corporation | Virtual Deletion In Merged Registry keys |
| US7895170B2 (en) * | 2007-02-14 | 2011-02-22 | Ricoh Company, Ltd. | Document management apparatus, document management program, and recording medium |
| US20090300592A1 (en) * | 2008-05-30 | 2009-12-03 | Microsoft Corporation | Automated dialog compliance mechanisms |
| JP5141971B2 (en) * | 2008-09-24 | 2013-02-13 | 横河電機株式会社 | Device information display device |
| USD747343S1 (en) * | 2009-09-30 | 2016-01-12 | Htc Corporation | Display screen with an animated graphical user interface |
| CA2904813C (en) | 2013-03-14 | 2023-10-03 | Wix.Com Ltd. | Device, system, and method of website building by utilizing data lists |
Family Cites Families (14)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| US4899136A (en) * | 1986-04-28 | 1990-02-06 | Xerox Corporation | Data processor having a user interface display with metaphoric objects |
| AU612681B2 (en) * | 1987-08-21 | 1991-07-18 | Samsung Electronics Co., Ltd. | Customization by automated resource substitution |
| JPH0833862B2 (en) * | 1989-10-23 | 1996-03-29 | インターナシヨナル・ビジネス・マシーンズ・コーポレーシヨン | Object-oriented computer system |
| US5546525A (en) * | 1989-11-13 | 1996-08-13 | Lotus Development Corporation | Computer user interface with multimode selection of displayed controls |
| CA2054026A1 (en) * | 1990-10-31 | 1992-05-01 | William Monroe Turpin | Goal oriented electronic form system |
| US5416895A (en) * | 1992-04-08 | 1995-05-16 | Borland International, Inc. | System and methods for improved spreadsheet interface with user-familiar objects |
| US5371675A (en) * | 1992-06-03 | 1994-12-06 | Lotus Development Corporation | Spreadsheet program which implements alternative range references |
| US5563997A (en) * | 1992-11-16 | 1996-10-08 | Canon Kabushiki Kaisha | Method and apparatus for sorting records into a list box in a graphic user interface |
| US5487141A (en) * | 1994-01-21 | 1996-01-23 | Borland International, Inc. | Development system with methods for visual inheritance and improved object reusability |
| WO1995031769A1 (en) * | 1994-05-16 | 1995-11-23 | Apple Computer, Inc. | Method and apparatus for associating and storing arbitrary data with graphical user interface elements |
| US5694561A (en) * | 1994-12-12 | 1997-12-02 | Microsoft Corporation | Method and system for grouping and manipulating windows |
| US5838317A (en) * | 1995-06-30 | 1998-11-17 | Microsoft Corporation | Method and apparatus for arranging displayed graphical representations on a computer interface |
| US5815703A (en) * | 1996-06-28 | 1998-09-29 | Microsoft Corporation | Computer-based uniform data interface (UDI) method and system using an application programming interface (API) |
| US5844554A (en) * | 1996-09-17 | 1998-12-01 | Bt Squared Technologies, Inc. | Methods and systems for user interfaces and constraint handling configurations software |
-
1996
- 1996-12-09 US US08/762,237 patent/US6121964A/en not_active Expired - Lifetime
-
1997
- 1997-10-17 CA CA002218593A patent/CA2218593C/en not_active Expired - Lifetime
- 1997-10-22 EP EP97118375.1A patent/EP0851345B1/en not_active Expired - Lifetime
- 1997-10-22 EP EP04029909A patent/EP1517234A3/en not_active Withdrawn
- 1997-11-10 US US08/966,836 patent/US6252593B1/en not_active Expired - Lifetime
- 1997-12-09 JP JP33756697A patent/JP4053637B2/en not_active Expired - Lifetime
Also Published As
| Publication number | Publication date |
|---|---|
| EP0851345B1 (en) | 2015-01-07 |
| EP0851345A3 (en) | 2003-04-09 |
| US6252593B1 (en) | 2001-06-26 |
| EP0851345A2 (en) | 1998-07-01 |
| CA2218593A1 (en) | 1998-06-09 |
| JPH11119963A (en) | 1999-04-30 |
| EP1517234A3 (en) | 2005-03-30 |
| EP1517234A2 (en) | 2005-03-23 |
| JP4053637B2 (en) | 2008-02-27 |
| US6121964A (en) | 2000-09-19 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| CA2218593C (en) | Method and system for automatic persistence of controls in a windowing environment | |
| US6470364B1 (en) | Method and apparatus for generating text components | |
| US6857103B1 (en) | Flexible help support in an object oriented application | |
| US6133917A (en) | Tracking changes to a computer software application when creating context-sensitive help functions | |
| Englander | Developing java beans | |
| US7039875B2 (en) | Computer user interfaces that are generated as needed | |
| US6175364B1 (en) | Framework and method for interfacing a GUI, container with a GUI component | |
| US6144377A (en) | Providing access to user interface elements of legacy application programs | |
| US7600046B2 (en) | Event notification | |
| US5327529A (en) | Process of designing user's interfaces for application programs | |
| US5682510A (en) | Method and system for adding application defined properties and application defined property sheet pages | |
| US6246403B1 (en) | Method and apparatus for generating a graphical user interface | |
| US20020054148A1 (en) | GUI control method and apparatus and recording medium | |
| US9507606B2 (en) | Dynamic creation of object classes | |
| US20030071860A1 (en) | System and method for managing graphical components | |
| US6486893B1 (en) | Property browser which displays properties of sub-objects in an Active X control | |
| US6310632B1 (en) | System and method for a graphical user interface including buddy dialogs | |
| US20050289450A1 (en) | User interface virtualization | |
| EP0438877B1 (en) | Method of reducing data storage requirements associated with computer windowing environments | |
| US7089500B2 (en) | Wizard user interface providing interim system product generation and reversion during wizard traversal | |
| EP0981086A1 (en) | Method for creating composite object methods and attributes | |
| US6587102B2 (en) | Rendering panels in multiple display contexts | |
| CA2475002C (en) | Method and system for automatic persistence of controls in a windowing environment | |
| JP2794339B2 (en) | The process of designing the user interface of an application program | |
| US6418482B1 (en) | Reference attributes within an object-oriented system |
Legal Events
| Date | Code | Title | Description |
|---|---|---|---|
| EEER | Examination request | ||
| MKEX | Expiry |
Effective date: 20171017 |