Patent Application
20100259560
The present invention relates to computer graphics applications. More particularly, the present invention relates to the application of graphics software to reduce the legibility of a computer screen to a potential viewer.
The evolution of computer screens has been progressively achieving higher resolution, brightness, sharpness, response time and contrast ratio. As screens are becoming larger, brighter and sharper, they are generally easier to read from a greater distance and wider angles. For example, laptops with passive-matrix screens, popular in the late 1990s, have been replaced with active-matrix, or TFT screens, in which each pixel is illuminated. The direct result is that a computer's TFT screen appears clearer and easier to read from a greater distance and wider viewing angle. New technologies continue to improve computer screens by increasing brightness and reducing glare, making screens easier to read in daylight and from greater distances and wider angles.
While the trend of bigger, better, brighter, and sharper screens offers a great benefit to the user, it also presents a drawback: the content of the screen may be more visible to prying eyes in the vicinity of the user. The proliferation of portable computers, e.g. the iPad® and similar hand-held computing devices, as well as laptops and smart phones with larger screen—and their usage at public places, compromise privacy. For example, more and more corporate users use their portable computers for work of potentially sensitive nature—ordinarily conducted behind closed doors in an office—at public places such as coffee shops and airplanes, where their screens could be read by dozens of people at any given time.
In recognition of the increased need for privacy demanded by computer users, hardware manufacturers have introduced hardware-based monitor security devices. Examples of hardware-based monitor security devices include computer privacy filters, or screens (collectively, privacy filters, unless otherwise noted), introduced by companies such as 3M®, feature a physical device that is adhered to, or placed over, a computer screen. Once such privacy filter is applied (i.e. placed over or adhered to) to a computer screen, its optics are designed to distort the view of the computer screen, when viewed from a wide angle or greater distance. The usage of a privacy filter may keep information displayed away from prying eyes, as a person to either side of the user may find their view of the computer screen distorted and intangible. Other related hardware-based monitor security devices are computer LCD screens that are manufactured in such way that they can be “read” (or viewed in a tangible way) only by a user sitting directly in front of them.
Hardware-based monitor security devices have multiple drawbacks. Among these drawbacks is the bulk and inconvenience, especially for mobile computing. Some filters are not easily removed from a monitor to allow viewing without the distorting effect of the screen, which users may want to do when security is less of a concern (as when a computer user may be using the computer to show something to others). Additionally, hardware monitor security devices in the form of privacy screens are ineffective in giving the audience of a presentation on a large display, such as an LCD projector or large flat screen TV, privacy from prying audience who may be standing a substantial distance away. (e.g. a LCD projected presentation at a company board room with glass walls, where people standing outside the room may be able to see sensitive projected information). There are other limitations and drawbacks of hardware monitor security devices to those described above.
For a more complete understanding of the present invention and further advantages thereof, references are now made to the following Detailed Description, taken in conjunction with the drawings, in which:
A software-implemented method for allowing a user to enhance privacy over any portion of their computer's display, is disclosed. The user may choose to display one or more translucent region(s) over any portion of their screen in such a manner as to allow the user to discern the content covered by the region, while making the task of discerning the content covered by the region more difficult to a person at a greater distance and wider angle to the screen, than the user. The translucent region may be turned on and off randomly by the user, via a pointing device, keyboard command, software hot-key, designated key on the keyboard or any other method. In an alternate embodiment, the translucent region may be displayed automatically in response to a display of a particular application or email.
The user may control the translucent region's shape, size, position, opaqueness and other behavioral characteristics. Applications covered by the translucent region are unaffected by it in terms of behavior. The translucent region may be optimized in such a manner as to have a minimal impact on the user sitting in front of the screen—so that they can read content covered by the translucent region with minimal strain—while offering the maximum obstruction to viewers further and at wider angles to the screen than the user. Different patterns may be applied to the translucent region, either automatically or at the user's choosing, so as to optimize its effectiveness under various conditions. The user may manually choose the pattern to be applied to the translucent region from a library of patterns; or, allow the software to choose, apply and adjust a pattern automatically.
The user may move and reposition the translucent region over an application manually; or, instruct the software to track an application and reposition the translucent region automatically. Various application types (e.g. documents, emails containing particular words in their subject lines or sent by a particular sender, etc.) may trigger the display of the translucent region automatically, as pre-set by the user.
Alternatively, the computer display may be for either a portion of the visible desktop, or of more than one visible desktop. A security window 104 may be displayed at any position of a user's visible display 102. the security window may be any size or shape, as desired or needed to cover the portion of the monitor the user wishes to enhance security. Security window 104 may include a border 106. Security window 104 includes one or more security graphical effects 108. In the presently preferred embodiment, the graphical effects 108 occupies the entire area inside the security window 104 (inside the border area in an embodiment with a border) Border 106 may provide for resizing the security window (or security window) 104, as is a common practice with applications displayed in a framed window in an operation system such as Microsoft Windows®.
Graphical effects 108 may contain one or more effects, colors, patterns, shapes, images and any other graphical effects. For example, Graphical effects 108 may have dynamic effects which change the effect, color, pattern, etc. to enhance security. Graphical effects 108 is translucent so that it may allow a user viewing display screen 102 to see objects 114 on display 102 “covered” by region 104. The objects may be text, images, or other graphical elements as rendered by computers and computer applications. The visibility of objects 114 which are covered by region 104 are distorted by the graphical effects 108 to a user viewing display device 102. In one preferred embodiment, the user may be presented with graphical effects control 110 which allows the user to alter the graphics of the graphical effects 108. in embodiments with the graphical effects control, the graphical effects control 110 may be permanently displayed in the security window 104, or may be temporarily displayed (when the region is activated, or in response to a command from the user).
In another embodiment of the present invention, the user may use graphical effects control 110 for selecting the graphical effects 108 from a library of patterns. The user may also be presented with a second graphical effects control 112 for altering the transparency level of the graphical effects 108, thereby affecting the visibility of objects 114 covered by the graphical effects 108, visible to a user viewing display device 102. The user may use graphical effects control 110 and 112 to optimize the visual quality of graphical effects 108 such that objects 114 obscured by security window 104 are readable to the user while sitting at a normal distance in front of display 102—yet are substantially indiscernible to another person at a greater distance and/or wider angle viewing display 102. Additional graphical controls may also be presented to the user, either together, sequentially, or in response to a command from the user. In this manner, the present invention allows for adjusting of the security enhancement to suit the possible security threat posed by the users surroundings.
In one preferred embodiment of the present invention, the graphical effect 204 may be a radial gradient with the darkest shading at the center of security window 200 and lightest at the periphery of the security window 200. (Please note that in
The uncovered region 310 of the application 302 may receive user input as the application 302 may be considered to be “in focus” (or “in use”) by the operating system running on that device. When user input is received by an operating system running on a user device, the operating system determines which application is in focus and passes to it the user input. The security window 304 does not change the user's ability to interact with an application, yet enhances the security by altering tiling of applications typically performed by conventional operating systems to allow the security window 304 to remain “on top” of the application 302 (or portion of the application 302) despite user inputs to application 302.
The maintaining of the security window 304 “on top” may be performed by the operating system (for example in an embodiment where the security window is part of the operating system), as part of the application 302; or, as a separate application. The user may position the security window 304 manually, using a pointing device, to a shape and size allowing the security window 304 to cover only a portion of application 302. Or, in another embodiment of the present invention, the user may instruct the security window 304 to “attach” itself to the application 302 such that when the user repositions the application 302, the security window 304 “follows” the application 302 and repositions itself accordingly, such that it may cover the same portion of application 302 in application's 302 new position. As shown in
The security window 304 may include a shaded, translucent region 306 as the graphical effect. The shading 306 of security window 304 may be in darker color so as to allow a user in proximity to the display device to read the content of a document 312 displayed in covered-application 302, through region 306. Alternatively, the shading 306 may be in a lighter color, or may be in a different color which is not noticeably darker or lighter than the area of the desktop covered by (or adjacent to) the security window. To a person at a greater distance from the display device, discerning the content of document 312, when viewed from “under” shaded region 306, may be comparatively more difficult, as the dark shading of region 306 may tend to appear more like a solid dark cover. In the current embodiment, region 306 may contain a watermark 308 which may be in some form of a tangible text or pattern, in a different color, brightness or contrast than shading pattern 306, and substantially translucent.
A watermark 508, superimposed on light region 506, may be of a darker, translucent color. While applicable to many different types of monitors or displays, this embodiment may be especially effective against viewers viewing LCD screens from above. It is the nature of LCD screens to invert colors, when viewed from above, which may make document 502 appear to be “washed out” and indiscernible. The optics and physical properties of LCD screens may change the appearance of objects when viewed from different angles and distances. When viewed from above, the colors of objects displayed by an LCD screen may invert, such that light colors appear dark and dark colors appear light. The watermark 508, while mostly transparent and substantially invisible to a user at a normal viewing position, may appear very prominent and further distract the prying viewer from being able to discern the portion 510 of content 502, covered by the security window 504, when viewed from above.
The complexity of graphical effect 606 may serve to further distract the prying user from discerning obscured content 608, though content 608 may remain partly visible to that user. The user may be able to alter the content, coloration, brightness, translucency level and any other visual property of graphical effect 606. In another embodiment of the present invention, a “skin” (graphics of the user's choosing applied to an application) 612 bearing a logo 610 may be a part of security window 604 to provide application skinning and branding.
Activation of the security window may be accomplished by launching the security window as a program, as done on PCs and other electronic devices, by a button or command associated with an application or operating system, through the use of a dedicated button (as may be included on a smart phone or on a laptop), or through the use of a hotkey. Automatic means of launching the security window are illustrated in FIGS. 15A,B and 16A,B. Yet another possible embodiment is shown in
An application may register a hot key with an operating system running on a device, instructing the operating system on what key (or keys) would define the hot-key-shortcut, and what application to invoke once that key (or keys) is pressed. Process 700 registers hot keys with the operation system, allowing the hot keys to open and close security windows, and un-registers the hot keys. At step 702 hot keys are defined and registered with the operating system running on a device, preferably one specific key to designate the launching of a new security window, and one for closing a security window. At step 704 the application which registered the hot keys is hidden such that it may become a process running away from the user's view. At any point in time, a user may press the specific key on the keyboard designated as a hot key in step 702. In step 706, the operating system, having received they user's pressing of a key designated as a hot key, notifies the application controlling security windows.
At step 708 a determination is made whether the hot key pressed is a hot key designated for launching a new security window, or closing an existing security window. If at step 708 a determination is made that the hot key pressed was intended to create a new security window, at step 710 a new security window is created. To “apply” the new security window to a window that is currently in focus (or “on top”), at steps 712-716 the newly-created security window may be positioned on top of the current window in focus. In one preferred embodiment, pressing the hot key initiates associating the security window with a specific window in order to cover that window; thus, the newly-created security window should match the location and dimensions of the window in focus. At step 712 a determination is made whether there is a window in focus.
At step 714 the location and size of the window in focus are obtained. At step 718 the security window created at step 710 is resized to the location and dimensions determined in step 714. If at step 712 the determination is made there is no window in focus, at step 716 the security window created at step 710 is set to a default location and size. If at step 708 the hot key invoked as denoting closing is identified, at step 720 a determination is made whether there is a window currently in focus. If the determination at step 720 is affirmative, at step 722 the size and location of the window in focus may be obtained. At step 724 a determination may be made whether any one of the existing security windows is associated with the window in focus. The determination may be made by accessing a stored record of security windows associated with other windows; or, it may be determined that, upon recursion of all security windows, the security window having the closest size and position to the window in focus, is said to be associated with the window in focus. Thus, an assumption may be made that that is the security window the user wishes to close and the handle to that security window may be obtained in step 728.
Step 730 then terminates that security window. If step 720 determines there is no window in focus, or if at step 724 it is determined there is no security window associated with the window in focus, at step 726 a handle to the first security window is obtained, and at step 730 this window is terminated. In other embodiments of the present invention, at step 726 a handle to the first, last or any arbitrary security window may be obtained; or, at step 726 the security window closest to the mouse cursor may be determined. For a complete shutdown of the application exhibiting the behavior of this invention, at step 732 a message from the operating system indicating the user has taken action to close this application may be received. at step 734 the hot keys registered in step 702 may be unregistered. At step 736 a common procedure to terminate the application's running on the device may be executed.
The security window 812 may be created at a default location and with a default size; or, in another embodiment of the present invention, security window 812 may be automatically created at the right location and size to cover the application in focus—in the present case, the application window 804. The user may resize or reposition the security window 812 as they would with any other application, such that it covers any desired portion of application 804. The user may instantiate another security window 816 such that it may cover application window 810. Security window 816 may contain a translucent region of darker shading 818 and a translucent watermark 820 in a lighter shade. Security window 816 may be positioned, either by the user or automatically by the software, in such way that it covers the content portion of application window 810, leaving the margins 822 of application window 810 open to user input. This configuration may allow the operating system to consider application 810 to be “in focus”, thus receiving user input though a substantial portion of it may be covered by the security window 816.
The security windows 812 and 816 may be moved or resized individually. In another embodiment of the present invention, security windows 812 and 816, along with any other similar security windows, may be closed summarily by a single form of user input, such as pressing a “hot key” or closing an application governing the security windows. The user may use a hot key to launch new security windows with a single click.
At step 904 the operating-system-issued handle of the first application window is obtained. At step 906 the coordinates and size of the application window whose handle was obtained in step 904, are obtained. At step 908 the coordinates and size obtained in step 906 are compared with the coordinates and size of the security window receiving input. If at step 910 it is determined the application window does not overlap with the security window, at step 924 a handle to the next application window is obtained, and step 906 is reverted to. Steps 904 through 924 repeat until it is determined at step 910 that the coordinates and size of an application window suggest the application overlaps the security window; or, until all application windows have been examined. Upon identifying an application window as overlapping a security window in step 910, at step 912 an instruction to make the security window non-top-most may be issued so that it may receive operating system input.
At step 914 a determination is made as to the nature of the user input as being either pointing device input or data input. If at step 914 it is determined that the input is pointing device input, at step 916 the coordinates of the inputted operating system message may be translated to the proper relative coordinates of the application window. At step 918 the translated-coordinate-bearing-input-message may then re-posted to the application. For example, let us assume the application discovered in step 910 is a word processor and the user intended to move the cursor to a new line and left-click to place the edit cursor at that specific location in the document, displayed within the word processor application.
A security window may cover the word processor and may be considered the application in focus, causing the user mouse move-and-click, intended for the word processor, to be directed to the security window by the operating system. At steps 912 through 918 the word processor application window may temporarily be brought into focus and be sent the translated coordinates for the mouse instruction the user had indented to send. Coordinate translation me be necessary as pointing device movement coordinates may differ among various applications displayed on the same screen. If at step 914 it is determined the input message is data (such as a user typing text) at step 918 the data intercepted by the security window would be re-posted , to the application. At step 920 the operating system may be instructed to make the security window top most, so it would cover the application once more.
From a user's perspective, it may appear the cursor moved smoothly and as intended within the word processor application, or their keystrokes registered instantaneously with the document, as the process in flow chart 900 would typically happen in milliseconds and may imperceptible to a user. In an alternate embodiment, process 900 may remove the security window from the top of the applications in the operating system as far as input is concerned (yet keep the security window topmost as far as display is concerned). In such an embodiment, input is directed to the application the operating system considers as topmost/active while continuing to cover the designated area or application with the security window.
The application 1000a may contain content 1004a which in this case contains the text “This is Personal Very Personal”. The words “This” and “Very” happen to be obscured by the security window 1006a, possibly due to the user's positioning of the security window 1006a at that given location. Nonetheless, the user 1002 is still able to read “through” the translucent security window 1006a and discern the phrase “This is Personal Very Personal”.
Referring now to
At step 1104 the handle to the first application window registered with the operating system may be obtained. At step 1106 the coordinates of the first window obtained in step 1104 may be obtained. At step 1108 the coordinates of the application window and the security window may be compared, to determine whether both windows overlap. Various embodiments of the present invention could determine whether such overlap exists, in various ways and varying degrees of tolerance. For example, an overlap could be determined to exist if the coordinates of the given application window match the coordinates of the security window more closely than the coordinates of any other application window.
If at step 1110 it is determined such overlap exists and the application window is covered by the security window, step 1114 may be executed. At step 1114 application programming interface calls may be used to obtain the content portion of the application window. For example, if the application window is a web browser, at step 1114 the coordinates of the webpage displayed within the browser window may be obtained, as opposed to the entire browser application window, which includes toolbars and skin. This step may allow the user to cover a smaller part of their screen, confined to information which is truly personal, as opposed to covering generic parts of applications such as toolbars.
At step 1116 the security window may be repositioned and resized to fit the coordinates obtained in step 1114. Step 1118 is then reached which ends the current flow. If at step 1110 it is determined the current application window does not overlap the security window, step 1112 may advance to the next application window registered with the operation system, until all windows have been examined. If no window has been found to overlap, at step 1120 the current flow end.
At step 1204 a handle to the application window to which the user chose to snap the filter may be retrieved. In step 1206 the association between the security window and application window may be recorded in the application's own memory space. Step 1208 ends the current flow until the user takes further action in the future. Once the user repositions an application window (e.g. if the application is an interne browser, the user may resize it and reposition it on the screen) step 1210 may be invoked, triggered by a standard operating system message of the window's repositioning.
In one possible embodiment the security window application may need to monitor operating system messages and trigger on messages calling for the movement of windows. At step 1212 a handle to the application window repositioned may be obtained. At step 1214 the handle of the window being repositioned may be compared with the handles placed in memory at step 1206 to determine whether there is an association between the application window the user is moving and any security window. If in step 1216 it is determined the handle of the window being repositioned is recorded in memory, i.e. there is a security window associated with that application window, steps 1218-1224 may be invoked.
At step 1218 the coordinates of the client-portion of the application window in step 1212 may be obtained. At step 1220 the handle to the specific security window that had been associated with the application window in step 1212, in step 1206, may be obtained from the software's memory space. At step 1222 the security window may be resized and repositioned to fit within the client-portion coordinates from step 1218. Step 1224 ends the current flow. If at step 1216 a match between the handle of the application window in step 1212 and the handles stored in the software's memory space in step 1206, is not found, the flow may end. The assumption is that the user has moved an application window which had not been associated with a security window, so there is no reason for the software to take action.
Application 1300 may contain one or more documents 1302. A document 1302 may contain one or more objects. (The definition of an object herein is any portion of an application which obtains a handle from the operating system. E.g. in an Excel® spreadsheet, every cell obtains a unique handle from the operating system, and this is an object. Document 1302 is in itself an object, as it is addressable by a unique handle assigned by the operating system.) Other examples of objects which may be tagged for association with a security window include a given word, phrase, or combination of words used in a document (such as the names of the parties in a contract, e.g. “Dr. Wellfield” or “Morgan Stanley”), figures, icons, images, numbers, etc. In this alternate embodiment, the user may instruct the security window software to affix one or more security windows 1304 to one or more objects in application 1300.
Document 1302 contains cells A1-E9. The user may enter data into various cells, such as the word “Projected” into cell B2 1310 and the number “$1,300,000” into cell D3 1306, as part of the normal operation of application 1300. The user may instruct the creation of security window 1304 which may contain a shaded region 1308. The user may affix the security window 1304 to specific objects such as cells D2, D3, D4, D5, D6 and, in document 1302 which is part of application 1300. The user may do so to enhance privacy over specific objects containing sensitive data, such as cell D3 1306, while keeping other cells, such as B3 1310, containing less sensitive data, un-obscured. Upon receiving instruction to be affixed to specific objects (cells D2, D3, D4, D5, D6 and D7) the security window 1304 may track the location and size of these objects and adjust itself to any changes in their physical disposition, automatically. For example, if the user chooses to scroll the worksheet document 1302 to the right (such that column D would shift left to occupy the present location of column C), the security window 1304 would be automatically repositioned in a similar manner, such that cells D2-D7 would remain covered by the security window 1304 in their new position. In an embodiment where the user chooses to associate a key word or similar object with a security window, a security window covering the associated object will be generated when and where the associated object appears in the document or application.
The user may decide that the entire desktop 1402 (or a large portion of the desktop) should be covered by a security window 1410, such that the view of the desktop and any applications 1404, 1406 displayed on it may be obstructed. The user may define a viewing window 1412 which leaves a region of the desktop 1402 un-obstructed. The user may position and size viewing window 1412 over an application in a manner allowing any content inside viewing window 1412, such as application 1408, to remain unobstructed. In the example shown in
In another possible embodiment, the size and position of the application 1408 displayed in the view window 1412, are tracked in a manner allowing view window 1412 to adjust automatically to application's 1408 new size and position, as the latter moves or is resized.
Referring to
At step 1506, user selections may be written to a data store (e.g. Windows®' registry, a cookie used by a web browser, a database connected to an internet service accessed via a web browser, etc.) The user selections recorded at this step may be used later to automatically display a security window upon detection of an application associated with the user selection.
At step 1508 the privacy application may be hidden from view (i.e. become “memory resident”) but maintain its OS-running status. For example, the privacy application may be a Windows® service, spawning one or more processes, such as a process to hook into the OS and a process to display a security window.
At step 1510 the privacy application may hook into the OS running on the electronic device; i.e. the privacy application may register a request with the OS to receive an event when the OS launches a new process.
Referring now to
At step 1552 the OS may send an event to the privacy application notifying the privacy application that a new process has been started (indicating a new application) has been launched. In response, at step 1554 the memory-resident privacy application may be invoked to compare the new process with the list of selected applications over which to display a security window.
If at step 1556 it is determined that the new process from step 1552 is on the list of selected applications, at step 1560-1566 a security window may be displayed over the new application and may be repositioned to entirely cover the new application. At step 1560, a handle to the new application window may be obtained (or any other means of communicating with the new application window.)
At step 1562 coordinates of the new application window may be obtained, for example by querying the OS via the application handle obtained at step 1562. At step 1564 a new instance of a security window may be created and displayed, and at step 1566 the new instance of the security window may be automatically resized and repositioned to overlay the new application window. I an alternate embodiment, the security window may overlay a significant portion of the new application window, according to various preferences and presets. If at step 1558 it is determined that the new application is not within the list of selected applications, at step 1570 no further action is taken.
Referring to
At step 1602 a plug-in or add-on may be added to an email client application (e.g. in a case of a web-based client, a plug-in may be added, whereas in a case of an application-based email client, an add-on type module may be installed on the same OS.)
At step 1604, the user may define criteria (“email security-window criteria”) based upon which a security window may be display in association with a specific email. Drawing an analogy to criteria used to filter spam or automatically route emails, the email security-window criteria may be based on one or more of the following attributes: sender's name, sender's email address, key words included in the email's subject-line and/or email body, etc. For example, the user may set a rule whereby all emails coming in from email address “ceo@mycompany.com” are displayed with a security filter automatically overlaying the window/browser in which the emails are displayed. Similarly, a more complex rule may be set up whereby a series of conditions need to be met for a security window to be displayed (e.g. email sender's address must include a certain domain name and subject like must include a certain key word.)
Past step 1604, the email application may resume normal functionality, until a new email-opening event is received. In response to a user's opening an email at step 1608, at step 1610 it may be determined whether an individual email, requested to be opened at step 1608, meets the email security-window criteria defined at step 1604. For example, if at step 1604 the criteria had been defined to include emails whose sender address is ceo@mycompany.com, at step 1610 it may be determined that the individual email meets the email security-window criteria.
Following a positive determination at step 1610, at steps 1612-1618 a security window may be displayed, substantially covering the individual email. At step 1612 the individual email may open in a new email window (alternatively, the individual email may be displayed within an existing email application window, in which case the existing email application window may be substituted for the new email window in this illustration.) At step 1614 coordinates of the new email window may be obtained, at step 1616 a new instance of the security window may be created (alternatively, an existing security window may be repositioned) and at step 1618 the new security window may be resized and/or repositioned to substantially cover the new email window. Following a negative determination at step 1610—or following the action at step 1618, at step 1620 normal email operation may resume.
Alternatively, or in addition to, the methodology illustrated in
At step 1652, an email may be composed be a sender. At step 1654, the sender may set an attribute (“security tag”) in the email indicating a request to display a security window over the email when received and opened by a recipient. In one possible embodiment, the sender may use the email client to set the security tag using a menu selection or any graphical mean (e.g. similarly to a common way in the prior art for setting the “importance” attribute of an email—typically by selecting a designated graphical control in the email client, such as a button labeled with an exclamation mark—causing the email to be received by the recipient and be displayed marked as “important”.)
At step 1656 the sender may send the email using any known, common method, and at step 1658 the recipient's email client may receive the email. At step 1660, the recipient's email client (e.g. a desktop-based productivity application, a web-based email application accessible via a web-browser, etc.) may determine whether the email contains the security tag. If it is determined at step 1660 that the email contains the security tag, at steps 1662-1668 a security window may be displayed over the email. At step 1662 the email may be displayed. At step 1664 coordinates of a window containing the email may be obtained. At step 1666 the security window may be instantiated, and at step 1668 the security window may be resized and/or repositioned to substantially overlay the window containing the email.
Following step 1668, or following a negative outcome of the conditional evaluation at step 1660, at step 1670 normal email operation may resume. The security window described in the present embodiments may be a separate application (or window) overlaying the application/window displaying the email; or, in an alternate embodiment, may be an integral part of the window displaying the email.
The invention has been described with reference to particular embodiments. However, it will be readily apparent to those skilled in the art that it is possible to embody the invention in specific forms other than those of the preferred embodiments described above. This may be done without departing from the spirit of the invention.
Thus, the preferred embodiment is merely illustrative and should not be considered restrictive in any way. The scope of the invention is given by the appended claims, rather than the preceding description, and all variations and equivalents which fall within the range of the claims are intended to be embraced therein.
Continuation-in-Part of application Ser. No. 11/496,382, Filed 31 Jul. 2006
| Number | Date | Country | |
|---|---|---|---|
| Parent | 11496382 | Jul 2006 | US |
| Child | 12802713 | US |
