Abstract: When a user is responding to a message in a thread and a new response message is detected for the thread, the user's response is automatically re-parented so the user's response is sent as a response to the newly detected response message in the thread.

Abstract: When a user is responding to a message in a thread and a new response message is detected for the thread, the user's response is automatically re-parented so the user's response is sent as a response to the newly detected response message in the thread.

Abstract: When a user is responding to a message in a thread and a new response message is detected for the thread, the user's response is automatically re-parented so the user's response is sent as a response to the newly detected response message in the thread.

Abstract: Methods and systems providing for collaborative commenting in a drawing tool are provided. One example method includes receiving a shape on a drawing canvas, and receiving a comment associated with the shape, the comment including a name of a commenting user. The method also includes receiving an indication of a movement of the shape from the first position to a second position, and, in response to the indication of the movement of the shape, automatically moving the comment closer to the second position of the shape. In some cases, the commenting user can be a user other than the user adding the shape to the document, and can be performed by a concurrent editor of the document.

Abstract: When a user is responding to a message in a thread and a new response message is detected for the thread, the user's response is automatically re-parented so the user's response is sent as a response to the newly detected response message in the thread.

Abstract: Concepts and technologies are described herein for touch interactions with a drawing application. In accordance with the concepts and technologies disclosed herein, user devices can obtain drawing data generated by a web-based drawing application and can display a drawing by rendering the data in one or more UIs. The user device can interpret touch gestures at a touch sensitive display used to present the UIs and can interpret the touch gestures as corresponding to one or more commands for modifying the UIs. According to various embodiments, the user device can interpret the touch gestures by determining if the touch gestures intersect an object in the drawing and other behavior associated with the touch gesture such as movement, subsequent touches, and whether or not an object intersected was selected when the touch gesture was commenced.

Abstract: A view of data is captured on a mobile device. The view of data can be presented to an augmented visualization system and augmented visualizations for the data are received from the augmented visualization system. The augmented visualization is displayed on the mobile device.

Abstract: Concepts and technologies are described herein for touch interactions with a drawing application. In accordance with the concepts and technologies disclosed herein, user devices can obtain drawing data generated by a web-based drawing application and can display a drawing by rendering the data in one or more UIs. The user device can interpret touch gestures at a touch sensitive display used to present the UIs and can interpret the touch gestures as corresponding to one or more commands for modifying the UIs. According to various embodiments, the user device can interpret the touch gestures by determining if the touch gestures intersect an object in the drawing and other behavior associated with the touch gesture such as movement, subsequent touches, and whether or not an object intersected was selected when the touch gesture was commenced.

Abstract: Methods and systems for coauthoring in a drawing tool are described. One computer-implemented method includes displaying a first user name of a first user in association with a first shape on a drawing, and receiving an indication that a second user is collaborating on the drawing. The method includes receiving an indication that the second user has modified a second shape on the drawing. The method also includes, in response to the indication that the second user has modified the second shape, displaying a second user name of the second user in association with the second shape on the drawing. The methods and systems can also include, in some cases, periodic sharing of metadata among coauthors, to indicate edits made by other coauthors.

Abstract: Methods and systems providing for collaborative commenting in a drawing tool are provided. One example method includes receiving a shape on a drawing canvas, and receiving a comment associated with the shape, the comment including a name of a commenting user. The method also includes receiving an indication of a movement of the shape from the first position to a second position, and, in response to the indication of the movement of the shape, automatically moving the comment closer to the second position of the shape. In some cases, the commenting user can be a user other than the user adding the shape to the document, and can be performed by a concurrent editor of the document.

Abstract: Custom user interfaces are inserted into native applications enabling various presentation formats to be used for integrating inserted user interfaces with existing user interface(s) of the native application. Inserted user interfaces may be presented as collapsible adjoining form regions, task panes, and/or large form regions as part of a tab collection of the native application. Registering the added user interfaces in a structured file in the operating system registry instead of an application protocol interface registration specific to the application enables synchronized installation of custom user interfaces and their controls.

Abstract: A system and method for handling the generation of an unexpected exception by an application. When the application generates an unexpected exception (i.e., crashes), the application's exception filter launches an outside exception handling program (EHP) that is separate and distinct from the application. Through a special protocol, the application and the EHP collaborate in responding to the unexpected exception. In this protocol, the application and the EHP communicate through kernel objects accessible by handles in a shared memory structure that the application creates before launching of the exception handling program and then shares with the EHP. Through this shared memory, the application also provides the EHP with information about the types of recovery options to offer the user. Through a graphical user interface, the EHP is then responsible for notifying the user of the application that an unexpected exception has occurred.

Abstract: A system and method for handling the generation of an unexpected exception by an application. When the application generates an unexpected exception (i.e., crashes), the application's exception filter launches an outside exception handling program (EHP) that is separate and distinct from the application. Through a special protocol, the application and the EHP collaborate in responding to the unexpected exception. In this protocol, the application and the EHP communicate through kernel objects accessible by handles in a shared memory structure that the application creates before launching of the exception handling program and then shares with the EHP. Through this shared memory, the application also provides the EHP with information about the types of recovery options to offer the user. Through a graphical user interface, the EHP is then responsible for notifying the user of the application that an unexpected exception has occurred.

Abstract: A system and method for handling the generation of an unexpected exception by an application. When the application generates an unexpected exception (i.e., crashes), the application's exception filter launches an outside exception handling program (EHP) that is separate and distinct from the application. Through a special protocol, the application and the EHP collaborate in responding to the unexpected exception. In this protocol, the application and the EHP communicate through kernel objects accessible by handles in a shared memory structure that the application creates before launching of the exception handling program and then shares with the EHP. Through this shared memory, the application also provides the EHP with information about the types of recovery options to offer the user. Through a graphical user interface, the EHP is then responsible for notifying the user of the application that an unexpected exception has occurred.

Abstract: Method and system for recovering information from open files during a failure in a program module. Once a failure is detected in the program module, control passes to an exception handler that determines whether the open files have been modified. If so, the open files are verified and stored as recovery versions of the files at the time of the failure. The program module is then terminated and restarted. Upon restarting the program module, the recovery version of the file at the time of the failure is opened and displayed to the user.

Abstract: Methods and systems for detecting and correcting computer software problems that cause an application program to crash upon startup are provided. Unsafe startup actions that are costly to initiate in terms of processor time and memory are handled by placing an unsafe startup action marker into the system registry prior to attempting startup. If an unsafe program module starts or boots successfully without causing the software application to crash, the unsafe startup action marker is deleted from the system registry. If loading the unsafe program module causes the application to crash, then startup actions, including corrective actions, are written into the unsafe startup action marker and are used on subsequent startup of the crashed application program to instruct the application on how to fix the problem. Other unsafe startup actions that are not costly in terms of processor time and memory are initially handled by an exception handler.

Abstract: A system allows for transferring messages between microprocessor based devices, such as programmable logic controllers (PLC), and a host computer over an Ethernet communications network. At the host computer level, these messages can be directed globally or locally. The host computer can immediately obtain messages from a programmable logic controller without interruption of the execution of the PLC's ladder program. The host computer can also receive unsolicited messages from the PLC.

Abstract: A control system contains a communications network, a host computer and a programmable logic controller (PLC). The host computer includes prioritized alarm queues for receiving prioritized alarms from the programmable logic controller. Alarms fall into either a local or a global category, and each category supports three types of alarms: warnings, alerts or faults.

Abstract: A control system allows for transferring messages between a programmable logic controller and a host computer over an Ethernet communications network. The messages include a routing address specifying an originating drop number, a destination drop number, and a routing drop number. The system is responsive to the routing address for transferring the messages between the programmable logic controller and the host computer. The host computer can immediately obtain messages from a programmable logic controller without interruption of the execution of its ladder program. The host computer can also receive unsolicited messages from the programmable logic controller.