Abstract: Prior art attempts to manage authority designation in GUI-based computer systems have set up various “handshaking” schemes between a graphics management system, such as a window server, and the various processes that are attempting to offer and accept access to each other. However, these schemes have certain limitations. In particular, when windows are used as the “fundamental basis” for implementing authority designation, events that should treat all content within a window identically can't do so because, even though all content in the window may appear to be “owned” by the window, there may be some other process that is actually rendering the content to some portion of the window. Thus, described herein are systems and methods to manage authority designation and event handling within “hierarchical” GUIs using “handshaking” schemes that are secure, sub-window granular, and that generalize recursively when applied to the various graphical layers used to construct the windows.

Abstract: Prior art attempts to manage authority designation in GUI-based computer systems have set up various “handshaking” schemes between a graphics management system, such as a window server, and the various processes that are attempting to offer and accept access to each other. However, these schemes have certain limitations. In particular, when windows are used as the “fundamental basis” for implementing authority designation, events that should treat all content within a window identically can't do so because, even though all content in the window may appear to be “owned” by the window, there may be some other process that is actually rendering the content to some portion of the window. Thus, described herein are systems and methods to manage authority designation and event handling within “hierarchical” GUIs using “handshaking” schemes that are secure, sub-window granular, and that generalize recursively when applied to the various graphical layers used to construct the windows.

Abstract: A first workspace, which may include one or more windows, may be associated with a first display device. A second workspace, which may also include one or more windows, may be associated with a second display device. The first and second workspaces may be provided for display to the first and second display devices, respectively. The first and second display devices may be independent such that manipulation a window of the first workspace across a coordinate location of the second display device does not affect the second display device.

Abstract: Prior art attempts to manage authority designation in GUI-based computer systems have set up various “handshaking” schemes between a graphics management system, such as a window server, and the various processes that are attempting to offer and accept access to each other. However, these schemes have certain limitations. In particular, when windows are used as the “fundamental basis” for implementing authority designation, events that should treat all content within a window identically can't do so because, even though all content in the window may appear to be “owned” by the window, there may be some other process that is actually rendering the content to some portion of the window. Thus, described herein are systems and methods to manage authority designation and event handling within “hierarchical” GUIs using “handshaking” schemes that are secure, sub-window granular, and that generalize recursively when applied to the various graphical layers used to construct the windows.

Abstract: A first workspace, which may include one or more windows, may be associated with a first display device. A second workspace, which may also include one or more windows, may be associated with a second display device. The first and second workspaces may be provided for display to the first and second display devices, respectively. The first and second display devices may be independent such that manipulation a window of the first workspace across a coordinate location of the second display device does not affect the second display device.

Abstract: A first workspace, which may include one or more windows, may be associated with a first display device. A second workspace, which may also include one or more windows, may be associated with a second display device. The first and second workspaces may be provided for display to the first and second display devices, respectively. The first and second display devices may be independent such that manipulation a window of the first workspace across a coordinate location of the second display device does not affect the second display device.

Abstract: Prior art attempts to manage authority designation in GUI-based computer systems have set up various “handshaking” schemes between a graphics management system, such as a window server, and the various processes that are attempting to offer and accept access to each other. However, these schemes have certain limitations. In particular, when windows are used as the “fundamental basis” for implementing authority designation, events that should treat all content within a window identically can't do so because, even though all content in the window may appear to be “owned” by the window, there may be some other process that is actually rendering the content to some portion of the window. Thus, described herein are systems and methods to manage authority designation and event handling within “hierarchical” GUIs using “handshaking” schemes that are secure, sub-window granular, and that generalize recursively when applied to the various graphical layers used to construct the windows.

Abstract: The present application is related to a method for providing output for a computing device. The method includes determining, by a processor, a location of a cursor, the cursor corresponding to an input device; analyzing, by the processor, whether the location is in a first tracking area for a first application; if the location is in a first tracking area, activating a first feedback profile for the first tracking area; sensing, by the input device, a first input to the input device; and providing a first output corresponding to one or more parameters determined by the first feedback profile.

Abstract: According to one aspect, a graphics management system receives a first message from a first process for granting one or more rights to a second process for accessing a GUI element owned by the first process. In response, the graphics management system transmits a second message to the second process, the second message offering the one or more rights to the second process. The graphics management system receives a third message from the second process indicating an acceptance of the offer. Thereafter, the graphics management system restricts access of the GUI element by the second process based on the one or more rights accepted by the second process.

Abstract: According to one aspect, a graphics management system receives a first message from a first process for granting one or more rights to a second process for accessing a GUI element owned by the first process. In response, the graphics management system transmits a second message to the second process, the second message offering the one or more rights to the second process. The graphics management system receives a third message from the second process indicating an acceptance of the offer. Thereafter, the graphics management system restricts access of the GUI element by the second process based on the one or more rights accepted by the second process.

Abstract: A first workspace, which may include one or more windows, may be associated with a first display device. A second workspace, which may also include one or more windows, may be associated with a second display device. The first and second workspaces may be provided for display to the first and second display devices, respectively. The first and second display devices may be independent such that manipulation a window of the first workspace across a coordinate location of the second display device does not affect the second display device.

Abstract: According to one aspect, a graphics management system receives a first message from a first process for granting one or more rights to a second process for accessing a GUI element owned by the first process. In response, the graphics management system transmits a second message to the second process, the second message offering the one or more rights to the second process. The graphics management system receives a third message from the second process indicating an acceptance of the offer. Thereafter, the graphics management system restricts access of the GUI element by the second process based on the one or more rights accepted by the second process.

Abstract: According to one aspect, a graphics management system receives a first message from a first process for granting one or more rights to a second process for accessing a GUI element owned by the first process. In response, the graphics management system transmits a second message to the second process, the second message offering the one or more rights to the second process. The graphics management system receives a third message from the second process indicating an acceptance of the offer. Thereafter, the graphics management system restricts access of the GUI element by the second process based on the one or more rights accepted by the second process.

Abstract: According to one aspect, a graphics management system receives a first message from a first process for granting one or more rights to a second process for accessing a GUI element owned by the first process. In response, the graphics management system transmits a second message to the second process, the second message offering the one or more rights to the second process. The graphics management system receives a third message from the second process indicating an acceptance of the offer. Thereafter, the graphics management system restricts access of the GUI element by the second process based on the one or more rights accepted by the second process.