(12) Patent Application Publication (10) Pub. No.: US 2013/ A1. Dhar et al. (43) Pub. Date: Jun. 6, 2013 NY (US) (57) ABSTRACT

Transcription

1 (19) United State US A1 (12) Patent Application Publication (10) Pub. No.: US 2013/ A1 Dhar et al. (43) Pub. Date: Jun. 6, 2013 (54) SYSTEMAND METHOD FORCHANGEABLE (52) U.S. Cl. FOCUS MODAL WINDOWS CPC... G06F 3/0481 ( ) USPC /803 (76) Inventor: Ahih Dhar, Peekkill, NY (US); Thinakaran Keavan, Wet Havetraw, NY (US) (57) ABSTRACT (21) Appl. No.: 13/635,982 A parent and child window are arranged in a uer interface to (22) PCT Filed: Mar. 17, 2011 caue the child window to behave a a modal window with repect to the parent window, and to behave a a modele (86). PCT No.: PCT/US11A28802 window with repect to a remainder of the uer interface. The S371 (c)(1), uer interface focu can be hifted without having to cloe the (2), (4) Date: Oct. 18, 2012 child window, a would ordinarily be the cae with a modal Related U.S. Application Data window. Opening the child window from the parent window pp caue one or more event handler to be intalled in the parent (60) Proviional application No. 61/315,482, filed on Mar. window to prevent input event from being proceed by the 19, parent window. The event handler() i(are) deintalled when Publication Claification the child window i cloed. Thi arrangement permit the uer interface to take advantage of the propertie of modal win (51) Int. Cl. dow, while providing flexibility for interacting with a G06F 3/048. I ( ) remainder of the uer interface. Title Bar DX Root Frame 120 Child Frame 122 Child Control 124 Child Control 126 ChildWindoW 140 Command 150

2 Patent Application Publication Jun. 6, 2013 Sheet 1 of 8 US 2013/ A1 WindoW Title Bar 112 D Root Frame 120 Child Frame 122 Child Control 124 e 140 Command Child Control FIG

3 Patent Application Publication Jun. 6, 2013 Sheet 2 of 8 US 2013/ A1 [ ] A GOZ00Z C???T][T?TO GOGOGOGOCZOCTOGO Z 9IAI

4 Patent Application Publication Jun. 6, 2013 Sheet 3 of 8 US 2013/ A1 GOZ00Z H GOEDGOEDGE) V nº 19 3SOO )[?AES (9 IAI

5 Patent Application Publication Jun. 6, 2013 Sheet 4 of 8 US 2013/ A1 SS eo O?AeS [YTIÐ

6 Patent Application Publication Jun. 6, 2013 Sheet 5 of 8 US 2013/ A1 X 8 SS XX X C X? $ ) SX X XX 8 X K XX 3 X XXX X XX & X SS C-<DC GDC º DC-8 DOZ DC U (9 IAI

7 Patent Application Publication [X],55 Jun. 6, 2013 Sheet 6 of 8 US 2013/ A1

8 Patent Application Publication Jun. 6, 2013 Sheet 7 of 8 US 2013/ A1 X O S O.

9 Patent Application Publication Jun. 6, 2013 Sheet 8 of 8 US 2013/ A1 Open modele child window indicated by Control 812 Intall event handler in parent window to prevent proceing of input event by parent window 814 Input event for parent Window? 816 SOftmodal Window cloed? 820 NO Prevent input event proceing or maintain or give focu to child Softmodal Window 818 Deintall event handler in parent window to permit input event proceing 822 FIG. 8 End

10 US 2013/ A1 Jun. 6, 2013 SYSTEMAND METHOD FORCHANGEABLE FOCUS MODAL WINDOWS STATEMENT REGARDING FEDERALLY SPONSORED RESEARCH ORDEVELOPMENT 0001 N/A BACKGROUND OF THE INVENTION 0002 The preent dicloure relate generally to opera tion in a window baed uer interface, and relate more particularly to modal window that permit a changeable focu Window baed uer interface provide different type of window, typically a ingle one of which i active in the uer interface at a time. The active window in the window baed interface i decribed a having the focu of the uer interface, indicating that input provided to the uer interface i proceed by the active window Window are typically implemented in a graphical uer interface (GUI), and typically provide a graphical and memory tructure for permitting oftware program to execute. That i, a Software program i typically aigned to a window in a GUI for execution. Initiating or activating a Software program in a GUI typically involve creating or preenting a window The concept of a window baed GUI enable a uer to work with everal Software program at the ame time. Window typically are permitted to overlap in the GUI, and their behavior i typically controlled by a window manager. A window manager typically provide facilitie for permitting window to be tacked or tiled and i often configured accord ing to a given GUI metaphor, Such a a multiple document interface (MDI) or ingle document interface (SDI). MDI GUI permit multiple child window under a ingle parent, while SDI GUI tend to have window that are eparate from each other. A GUI that operate in MDI mode typically per mit child window to embed other child window to form a neted hierarchy Window appearance can take many form, includ ing window frame that are arranged in particular pattern to ait in meeting a tak oriented goal. For example, ome application may lend themelve to a tab oriented preenta tion in a window frame, while other application may have collapible child window within a window frame. Some example of window frame type include grid, flow, pixel, tab, and collapible In an MDI mode, the focu can often be witched between child window to align with a given tak or a work flow of the uer. In either MDI or SDI mode, window type are typically offered that can be a window child, a floating win dow, a pinned window, a modele window or a modal win dow. A modele window permit the focu to hift to other uer interface component without being cloed. A modal window i a child window that obtain the focu of the GUI and doe not releae the focu until being cloed. In compari on, a modele window can remain open while the focu i hifted to another window. Example of modal window are often oberved in configuration etting or other important interface action, uch a opening or aving file. In Such example, the modal window maintain the focu of the GUI to draw uer attention to the window without interruption from other procee, thread, or window application. The ue of a modal window thu prevent a uer from activating other window or hifting the focu from the modal window until the modal window i cloed. In mot intance, modal window are configured to be preented foremot in the GUI, that i, on top of other window in the GUI A modal window i typically configured to have a behavior that exclude all other window and panel from receiving event. Initiation of a modal window typically caue the window to monopolize all event, including input event, however, other thread and procee can continue to operate. The modal window typically releae event monopo lization upon being cloed o that other window can receive the focu and proce event in the uer interface In a multi-taking, multi-threaded environment, Such a i typically implemented in peronal computer, micro and mini computer, and in ditributed computing envi ronment, event can occur that are preferably annunciated to a uer with a high priority. For example, in a laboratory ditributed computing environment, event may occur in rela tion to intrument operation that warrant immediate atten tion of a uer. If the uer ha intructed a uer interface to open amodal window, event that warrant immediate uer attention may not be viible or annunciated to the uer. In addition, if the uer i informed of a high priority event while a modal window i open, the uer typically i required to cloe the modal window to take action in the uer interface to addre the high priority ituation. If the open modal window wa being ued for data entry or other important apect of a uer workflow, Such a file aving or communication, cloing the modal window may terminate or eliminate input provided to the modal window by the uer. Thu, while the ue of modal window have a number of recognized advantage for main taining the attention of a uer and the focu of a GUI, their ue can repreent an obtacle to dealing with event that are external to the modal window. BRIEF SUMMARY OF THE INVENTION In accordance with the preent dicloure, a GUI i provided that permit window focu Switching in the preence of a modal window. The modal window that i opened at the time of the focu witching i referred to herein a a oftmodal window. The oftmodal window behavior i modal to it parent window and modele with repect to other uer inter face component, o that the uer can Switch to other window or otherwie interact with other part of the GUI. Several parent window may be open imultaneouly and diplaying oftmodal child window, where the uer i able to witch between the oftmodal child window, which remain modal to their parent window The contruction of a oftmodal window i baed on the ue of a modele window that i opened in repone to event directed to a modele or oftmodal parent window. When the child modele window i opened, event that are directed to the parent modele window that might caue the parent window to receive the focu are prevented from being proceed, or caue the child modele window to receive or maintain the focu, o that the child modele window appear to be modal with repect to the parent window, or a Softmodal window in accordance with the preent dicloure. While a oftmodal window i open, other window can be activated that are not within the hierarchy of the oftmodal window, that i, not a parent or grandparent of the oftmodal window, for example. Other window outide the hierarchy of the oftmodal window can alo have oftmodal child win dow, o that it i poible to witch between oftmodal win

11 US 2013/ A1 Jun. 6, 2013 dow of different window hierarchie without having to cloe window in a window hierarchy The ue of oftmodal window in a GUI interface permit greater flexibility in preenting and permitting repone to event that are unrelated to the window or win dow hierarchy of the current focu. For example, ynchro nou or aynchronou event that are annunciated to the GUI can be ued to prompt the uer to Switch the focu away from the oftmodal window. Such a feature i highly ueful in dealing with event uch a alert or alarm preented to the GUI. BRIEF DESCRIPTION OF THE SEVERAL VIEWS OF THE DRAWINGS 0013 The preent dicloure i decribed in greater detail below, with reference to the accompanying drawing, in which: 0014 FIG. 1 i a block diagram illutrating a hierarchy of window component; 0015 FIGS. 2-6 are uer interface creen example illu trating a feature of the preent dicloure; 0016 FIG. 7 i chematic block diagram illutrating operation of oftmodal window in accordance with the preent dicloure; 0017 FIG. 8 i a flowchart illutrating creation of a oft modal window. DETAILED DESCRIPTION OF THE INVENTION Thi application claim the benefit of U.S. provi ional application No. 61/315,482, filed Mar. 19, 2010, the entire dicloure of which i hereby incorporated herein by reference A modal window i typically implemented through a contruct provided by a window oriented uer interface or a GUI that i available to an application developer. The appli cation developer typically invoke the modal window con truct to form a modal window according to parameter peci fied by the application developer. For example, the application developer may pecify a window ize, title bar text, control uch a button or drop down boxe, and other common or familiar window parameter. Becaue the win dow i invoked a a modal window, the uer interface, or operating ytem that provide the mechanim for forming a window in a diplay, caue the modal window to be formed according to the parameter accompanying the modal win dow intance The modal window contruct include etting to exclude proceing of uer interface input event from com ponent outide the modal window. Such uer input event include keytroke and moue movement or click, which event are not proceed or are caued to be directed to the modal window for proceing. For example, moue click outide the modal window may not be proceed, while pre ing the Enter key on a uer interface-connected keyboard may be directed to a default button election in the modal window. Accordingly, the nature of the modal window con truct prevent uer interface input event from being pro ceed outide the modal window. The modal window con truct continue thi behavior until the modal window i cloed, at which time the uer interface or operating ytem caue uer interface input event to again be directed to appropriate target in the uer interface inaccordance with the uer interface tate Modal window can be ueful in a number of apect of a Software application, ince they commanda uer' atten tion and focu the uer on the content of the modal window, ince interaction with the uer interface outide the modal window i prevented. Application developer can ue modal window to pecify a workflow, Such a by cauing the uer to take ome action in relation to a modal window before pro ceeding with other tak. Modal window are often ued for important data entry or equence action, uch a opening or aving file or configuring parameter value However, becaue modal window by their nature prevent acce to other portion of a uer interface, they can obtruct ome type of uer workflow, ince the modal win dow i cloed to permit interaction with other apect of the uer interface. Accordingly, upon the occurrence of an event that i external to the modal window, the uer i often unable to oberve the event, or i unable to repond to uch an event while a modal window i open. In addition, a uer eeking to oberve or repond to uch an external event i forced to cloe the modal window to permit acce to other apect of the uer interface. The modal window being thu cloed interrupt the workflow of the uer, and may caue lo of data or facility for inputting or modifying data or parameter etting In accordance with the preently dicloed ytem and method, a oftmodal window i provided a a child of a parent window that need not be cloed before interacting with other apect of the uer interface. Referring to FIG. 1, a hierarchical diagram of window component i illutrated for a window 110. Window 110 include a title bar 112 that provide familiar window parameter, uch a window title text, a help button 114, a izing button 116 and a cloe button 118. The layout of title bar 112 i a grid layout frame familiar to uer of window baed GUI Window 110 further include a root frame 120 that provide the main window frame for window 110. Mot type of window typically include a root frame in which the win dow layout i contructed. Layout for window or frame can include a grid layout, uch a i provided with title bar 112, or flow, pixel, tabbed or collapible layout. Root frame 120 include everal child component, including child frame 122 and child control 126. Child frame 122 can be arranged within root frame 120 to provide conceptual eparation for window component, uch a may be provided in a window pane arrangement. Each of child frame 122 may alo include one or more child control 124, which may take the form of dropdown boxe, text boxe, radio button, puhbutton, and other familiar window control component. Similarly, root frame 120 can alo have child control component 126 that are related to activity in root frame 120 in the ame way that child control 124 are active in relation to child frame 122. (0025 Window 110 may alo include child window 140, which can be generated through control or command in window 110. Child window 140 can be of any typical type, including MDI child window, floating type window, pinned or modal window. In accordance with the preent dicloure, a child window 140 i a oftmodal window correponding to window 110 a a parent window. Window 110 may alo include one or more command 150, which are clae that implement a command interface loaded at runtime In accordance with the preent dicloure, a child window 140 i a oftmodal window that act a a modal window with repect to it parent window 110. When oft modal child window 140 i opened, uer interface event that are directed to window 110 are prevented from being pro

12 US 2013/ A1 Jun. 6, 2013 ceed, or caue oftmodal child window 140 to receive the focu of the uer interface. Softmodal child window 140 i initially implemented a a modele window, that i, a win dow that permit a hift of the focu to other portion of the uer interface without firt being cloed The action of opening oftmodal child window 140 prompt one or more event handler to be intalled for win dow 110. The event handler are triggered by uer interface input event directed to window 110, and prevent proceing of the event or caue oftmodal child window 140 to receive the focu. In thi way, oftmodal child window 140 act a a modal window with repect to parent window 110. Uer interface input event that are directed to other portion of the uer interface outide of window 110 and oftmodal window 140 operate a if the combination of window 110 and oft modal 140 were modele, imilar to typical window behav ior in a general MDI etting. In thi way, window 110 and oftmodal window 140 act a a window hierarchy, o that window 110 i prevented from accepting uer interface input event while oftmodal child window 140 i open. However, uer interface input event outide of window 110 and oft modal window 140 are treated a modele to permit uer interaction with the remainder of the uer interface without firt cloing oftmodal child window Referring now to FIG. 2, an illutration of a window 200 i provided that operate in accordance with the preently dicloed ytem and method. Window 200 i arranged in a tab layout, o that election of different tab caue different child window to be opened. Window 200 how a child quality control (QC) window 210 being active in the diplay window 200. QC window 210 alo include tabbed feature that can be implemented a child window or frame to di play relevant data and permit uer interface input and/or out put. QC window 210 alo include control in the form of drop-down boxe and button, including Addbutton 212. Add button 212 i ued to add a QC definition in accordance with the active tab of QC window Referring now to FIG. 3, QC window 210 i hown after activating Add button 212 to produce a oftmodal win dow 300. Softmodal window 300 i a Softmodal child window of window 210, o that uer input event directed to window 210. Such a moue movement or moue click, are not proceed, or may caue oftmodal window 300 to receive more maintain the focu. In addition, or alternately, keytroke entrie may be directed to oftmodal window 300 when it ha or receive the focu, intead of being directed to the parent window 210. Uer interaction with QC window 210 a a parent window of oftmodal window 300 i thu prevented in accordance with the defined contraint of the preent diclo Sure. Accordingly, placing the moue in the viible region of QC window 210 or moue clicking in thoe area or providing keytroke entry, are all event that are prevented from being proceed or become directed to oftmodal window 300 a having the current focu. Uer interaction with QC window 210 continue to be prevented while oftmodal window 300 i open, o that oftmodal window 300 act a a modal window with repect to QC window 210 a a parent window. While oftmodal window 300 i open, a uer may enter QC defini tion data, uch a a QC ID, name, level or expiration param eter. In addition, variou data i tabulated in oftmodal win dow 300 that i obervable by the uer. 0030) Referring now to FIG. 4, an event tab 420 i illu trated a indicating the occurrence of an event, uch a by changing color, flahing or by providing other alerting indi cia. Tab 420 repreent a control for witching to an event window 510 (FIG. 5) to review or react to the event. The activity indicated by event tab 420 i external to oftmodal window 300 and QC window 210, and may be ynchronou or aynchronou with operation of the uer interface preented by window 200. However, oftmodal window 300 being open while event activity occur illutrate an important feature of the preently dicloed ytem and method. If oftmodal win dow 300 were to operate on a trictly modal bai, the uer would cloe oftmodal window 300 before being able to witch to the event window indicated by event tab 420. Thi contraint i preent in the cae of trictly modal window due to the nature of the modal window contruct that prevent uer-interface input event from being proceed outide of a trictly modal window, until the trictly modal window i cloed. However, in accordance with the preently dicloed ytem and method, event tab 420 i acceible by the uer while oftmodal window 300 i open, even though QC win dow 210 may not be activated while oftmodal window 300 i open Referring now to FIG. 5, event window 510 i illu trated a being opened by the uer electing event tab 420. Event window 510 provide an event occurrence diplay 520 for uer review and to which the uer can react while event window 510 i open. Event diplay 520 fall under the tab labeled Uer Event' in event window 510, which can be automatically elected when event tab 420 i activated to diplay event window 510. The uer can review and react to event diplay 520, which can repreent an alert or an alarm annunciated in the oftware application. While the uer review event diplay 520 in event window 510, QC window 210 i till active in the background in that it continue pro ceing, and continue to hot oftmodal window Referring now to FIG. 6, once the uer ha reviewed and/or reponded to event diplay 520, QC tab. 205 can be elected to caue window 210 to be preented within window 200, with oftmodal window 300 continuing to receive the focu of QC window 210. That i, when QC tab 205 i elected to preent QC window 210, oftmodal window 300 continue to be able to receive uer interface input event, while input event directed to QC window 210 are not pro ceed. In window 210, a uer can continue to enter data into oftmodal window 300 after QC tab. 205 i elected, without interruption that can occur if oftmodal window 300 were to be cloed prior to electing other window by activating the tab in window Referring now to FIG. 7, a window diplay 700 i illutrated howing a hierarchy of parent and child oftmodal window in accordance with the preent dicloure. Window diplay 700 include et of window A, B, C and X, Y, Z that illutrate the oftmodal window concept. In window diplay 700, window A and window X are parent window that include control (not hown) that, upon activation, can caue oftmodal window Band Y to be opened, repectively. When oftmodal window B i opened from parent window A, it i initially et a a modele window that doe not otherwie prevent other portion of the uer interface from proceing uer interface input event. However, upon window B being opened, window A i reconfigured to prevent proceing of input event or to direct thoe event to window Buing event handler aociated with window A input event. 0034) For example, a moue click in window A caue a Software interrupt that i proceed through a handler in win dow A. If a handler according to the preent dicloure i not

13 US 2013/ A1 Jun. 6, 2013 intalled, the moue click on window A caue window A to receive the focu. The preent dicloure provide for intall ing a handler for input event directed to window A, o that thoe event trigger the handler for proceing in accordance with a oftmodal window treatment. The intalled handler ha a tored window reference to window B, or can locate a window reference to window B, uch a by looking up a window handle. The intalled handler then repond to oft ware interrupt that may be caued by input event uch a moue movement or click in window A, or other input event that might caue window A to receive the focu, and caue window B to receive or maintain the focu intead. The intalled handler look up or retrieve the window reference to window B, and caue the focu to be hifted to or main tained by window B Accordingly, the intalled handler for input event in window A prevent window A from receiving the focu, and caue window B to receive or maintain the focu to act a a modal window with repect to window A. However, input event that are not directed to window A or window B, that i, input event that are directed to elewhere in the uer inter face, are proceed according to input event handler for thoe uer interface component. For example, while Softmodal window B i open, the uer can caue window X to receive the current focu, and can interact with window X and caue window Y to be loaded baed on input event directed to window X. Window Y i loaded a a oftmodal child window of window X in the ame way that oftmodal window B i formed with repect to parent window A, a decribed above. Accordingly, once Softmodal window Y i opened, window X doe not receive the focu in repone to input event. How ever, a uer can witch between window B and window Y without having to firt cloe one or the other Softmodal window C and Zhave imilar behavior to oftmodal window B and Y, repectively, with oftmodal window B and Y acting a the parent window of oftmodal window Cand Z, repectively. Accordingly, when Softmodal window C i opened, neither parent window A nor oftmodal window B repond to input event directed to thoe win dow. Input event handler are intalled for parent window A and oftmodal window B to prevent thoe window from receiving the focu or proceing input event, and to hift or maintain the focu in window C. However, uer interface input event directed to parent window X or oftmodal win dow Y caue oftmodal window Z to obtain the focu to become the active window. Window A, B and C, a well a window X,Y and Z thu illutrate the hierarchical tructure that i made available through proviion of oftmodal win dow in window diplay There i no limit to the number of oftmodal child window that can be formed beginning with parent window A or X, other than practical implementation contraint. In each hierarchy, the topmot oftmodal window receive the focu when uer interface input entrie are directed to any of the window in the hierarchy. Accordingly, a uer can Switch between window hierarchie when oftmodal window are employed in the window hierarchy. The facility for witching between window hierarchie permit improved workflow for the uer, ince the tatu of the window hierarchy i main tained by the lat open oftmodal window, even when the focu witche to one or more other window or window hierarchie. That i, the uer can return to a window hierarchy and continue to interact with the topmot oftmodal window that remain open during Switching between different win dow or window hierarchie. Such an arrangement repreent a ignificant advantage for the uer, by not having to cloe modal window prior to Switching to other window in a window-baed uer interface Referring now to FIG. 8, a flowchart 800 illutrate the proce for generating a oftmodal window. The proce of generating oftmodal window begin with a uer actuating a control in a parent window. Deciion block 810 illutrate the determination of when a control in a parent window i activated to open a Softmodal window. If a control i actuated to activate a oftmodal window, a child window i opened a a modele window in accordance with the actuated control, a illutrated in block 812, which i reached by proceeding on the Ye path from deciion block 810. Once the modele child window i opened, event handler are intalled in the parent window to prevent proceing of input event by the parent window, a illutrated in block The intallation of the event handler in the parent window can be prompted by the opening of the child window to caue the child window to act a a oftmodal window. The event handler prevent input event that are directed to the parent window from being proceed, or from cauing the parent window to receive the focu. A determination of whether an input event for the parent window ha occurred i illutrated in deciion block 816. Block 818 illutrate pre vention of input event proceing, or cauing the focu to be hifted to or maintained by the child oftmodal window, in accordance with the Ye path taken from deciion block 816. Flowchart 800 illutrate continuou checking for input event in the parent window to how the activity of oftware interrupt prompted by input event, uch a moue activity or keytroke entry. If there are no input event for the parent window, the illutrated proce determine whether the oft modal window i cloed, a illutrated in deciion block 820. If the oftmodal window i not cloed, the illutrated proce continue to check for input event for the parent window, a illutrated by the No branch being taken to deciion block 816 from deciion block 820. If the oftmodal window i cloed, event handler in the parent window are deintalled to permit input event proceing, a i illutrated in block 822 that i reached by the Ye branch of deciion block The preently dicloed approach uing oftmodal window provide a number of advantage over the conven tional modal window approach. The uer i preented with a oftmodal window that act a a modal window within the parent window framework to obtain the advantage offered with the modal window paradigm. In addition, the uer i able to change the focu of the uer interface without cloing the oftmodal window to permit interaction with other apect of the uer interface. The uer can witchback to the oftmodal window, which remain in a current tate when the focu i hifted to other area of the uer interface The operation herein decribed are purely exem plary and imply no particular order. Further, the operation can be ued in any equence when appropriate and can be partially ued. With the above embodiment in mind, it hould be undertood that the dicloed ytem, device, method and/or ue can employ variou computer-implemented operation involving data tranferred or tored in computer ytem. Thee operation are thoe requiring phyical manipulation of phyical quantitie. Uually, though not nec earily, thee quantitie take the form of electrical, magnetic, or optical ignal capable of being tored, tranferred, com bined, compared, and otherwie manipulated.

14 US 2013/ A1 Jun. 6, Any of the operation decribed herein that form part of the preent dicloure are ueful machine operation. The preent dicloure alo relate to a device or an apparatu for performing thee operation. The apparatu can be pe cially contructed for the required purpoe, or the apparatu can be a general-purpoe computer electively activated or configured by a computer program Stored in the computer. In particular, variou general-purpoe machine employing one or more proceor coupled to one or more computer readable medium, decribed below, can be ued with computer pro gram written in accordance with the teaching herein, or it may be more convenient to contruct a more pecialized apparatu to perform the required operation The dicloed ytem and method can alo be embodied a computer readable code on a computer readable medium. The computer readable medium i any data torage device that can tore data, which can thereafter be read by a computer ytem. Example of the computer readable medium include hard drive, read-only memory, random acce memory, CD-ROM, CD-R, CD-RW, magnetic tape and other optical and non-optical data torage device. The computer readable medium can alo be ditributed over a network-coupled computer ytem o that the computer read able code i tored and executed in a ditributed fahion. 0044) The foregoing decription ha been directed to par ticular embodiment of the preent dicloure. It will be apparent, however, that other variation and modification may be made to the decribed embodiment, with the attain ment of ome or all of their advantage. The procedure, procee and/or module decribed herein may be imple mented in hardware, oftware, embodied a a computer-read able medium having program intruction, firmware, or a combination thereof. For example, the function decribed herein may be performed by a proceor executing program intruction out of a memory or other torage device. There fore, it i the object of the appended claim to cover all uch variation and modification a come within the true pirit and Scope of the preent dicloure. What i claimed i: 1. A ytem for implementing a changeable focu modal window in a uer interface, compriing: a proceor coupled to a memory unit and operable to retrieve and execute intruction tored in the memory unit to implement: a parent window that include a control that can be actuated to caue a child window to be opened; a child window opened in a modele tate a a reult of the actuated control; and intallation of an event handler in the parent window to prevent the parent window from receiving an interface focu in repone to input event, uch that the child window behave a a modal window with repect to the parent window, and behave a a modele window with repect to a remainder of the uer interface. 2. The ytem according to claim 1, wherein the parent window and opened child window form a hierarchy. 3. The ytem according to claim 2, wherein the hierarchy behave a a modele window with repect to the remainder of the uer interface. 4. The ytem according to claim 1, further compriing implementing an event indication in repone to an event that occur externally to the parent window and the child window, uch that the event indication i preented in the uer interface when the child window i open. 5. The ytem according to claim 1, further compriing implementing a firt window externally to the parent window and the child window and permitting the uer interface focu to be hifted to the firt window while the child window remain open. 6. The ytem according to claim 5, wherein the firt win dow comprie a econd child window that act a a modal window with repect to a econd parent window, and act a a modele window with repect to the child window. 7. The ytem according to claim 1, further compriing implementing deintallation of the event handler in the parent window when the child window i cloed. 8. A method for implementing a changeable focu modal window in a uer interface, compriing: actuating a control in a parent window to caue a child window to be opened; opening the child window in a modele tate; and intalling an event handler in the parent window to prevent the parent window from receiving an interface focu in repone to input event, uch that the child window behave a a modal window with repect to the parent window, and behave a a modele window with repect to a remainder of the uer interface. 9. The method according to claim 8, further compriing forming a hierarchy with the parent window and opened child window. 10. The method according to claim 9, wherein the hierar chy behave a a modele window with repect to the remainder of the uer interface. 11. The method according to claim 8, further compriing implementing an event indication in repone to an event that occur externally to the parent window and the child window, uch that the event indication i preented in the uer interface when the child window i open. 12. The method according to claim 8, further compriing implementing a firt window externally to the parent window and the child window and permitting the uer interface focu to be hifted to the firt window while the child window remain open. 13. The method according to claim 12, wherein the firt window comprie a econd child window that act a a modal window with repect to a econd parent window, and act a a modele window with repect to the child window. 14. The method according to claim 8, further compriing implementing deintallation of the event handler in the parent window when the child window i cloed. 15. A uer interface implemented on a numerical comput ing device and operative to diplay a window, the uer inter face compriing: a parent window that include a control that can be actuated to caue a child window to be opened; a child window opened in a modele State in repone to the actuated control; and an event handler intallation in the parent window in repone to the opened child window to prevent the parent window from receiving focu, uch that the child window behave a a modal window with repect to the parent window, and behave a a modele window with repect to a remainder of the uer interface. k k k k k