Abstract: An adhesive device used as a wound dressing, ingredient delivery device or IV hold-down in which inadvertent edge release of these devices along the periphery of the polymeric film layer is minimized when the handling layer, which is adhered to the polymeric film layer, is removed after application of the polymeric film layer to the patient.

Abstract: Adhesive devices used as wound dressings, ingredient delivery devices and IV hold-downs include a handling layer comprised of a layer of conductive material and at least one layer of non-conductive material, adhered to the non-adhesive coated side of an adhesive coated polymeric film layer, by an electrostatic charge, rather than by an adhesive.

Abstract: A panel system includes a first panel having a first frame and a first cladding connected to the first frame and a second panel having a second frame and a second cladding connected to the second frame. Various components are used to secure the panels together, to secure the claddings, and to stabilize the panels. The panels can be arranged in different configurations to create a variety of work areas.

Abstract: An electronic cigarette is provided in two or three sections. One section is a reusable barrel containing the electrical components, including a rechargeable battery and a heater or atomizer. Another section may include the atomizer and a replaceable and disposable cartridge having the desired volatile substance, such as nicotine, a medicament, and/or a flavoring agent.

Abstract: A file operations engine is provided that manages many user interactions with their files via a computer system. The operation engine may provide a user with the option to keep both files that have a file name conflict. It may further permit the user to rename a file involved with a file name conflict. The operations engine may also automatically rename one of the files of a file name conflict by appending a character to a root of the filename. The character may include the lowest integer available for the root in a destination for the files. The operations engine may provide the option to keep both files as part of a pre-calculation of potential errors for a requested operation. The operations engine may place file name conflicts in an error queue and permit the user to select an option to keep both files after the conflict is encountered.

Abstract: Approaches for monitoring traffic signal preemption at one or more intersections. According to one embodiment, a road map that includes a plurality of roads and intersections is displayed with a computer system. Preemption data periodically received by the computer system from at least one preemption controller at a respective intersection is used to update the road map. In response to the preemption data, the road map is updated to include a traffic signal icon at the respective intersection and a vehicle icon at a location on the map corresponding to a location of a vehicle transmitting a preemption request as indicated by the preemption data.

Abstract: A file operations engine is provided that manages many user interactions with their files via a computer system. The operation engine may provide a user with the option to keep both files that have a file name conflict. It may further permit the user to rename a file involved with a file name conflict. The operations engine may also automatically rename one of the files of a file name conflict by appending a character to a root of the filename. The character may include the lowest integer available for the root in a destination for the files. The operations engine may provide the option to keep both files as part of a pre-calculation of potential errors for a requested operation. The operations engine may place file name conflicts in an error queue and permit the user to select an option to keep both files after the conflict is encountered.

Abstract: A file operations engine is provided that manages many user interactions with their files via a computer system. The operation engine may provide a user with the option to keep both files that have a file name conflict. It may further permit the user to rename a file involved with a file name conflict. The operations engine may also automatically rename one of the files of a file name conflict by appending a character to a root of the filename. The character may include the lowest integer available for the root in a destination for the files. The operations engine may provide the option to keep both files as part of a pre-calculation of potential errors for a requested operation. The operations engine may place file name conflicts in an error queue and permit the user to select an option to keep both files after the conflict is encountered.

Abstract: An adhesive device used as a wound dressing, ingredient delivery device or IV hold-down in which inadvertent edge release of these devices along the periphery of the polymeric film layer is minimized when the handling layer, which is adhered to the polymeric film layer, is removed after application of the polymeric film layer to the patient.

Abstract: Approaches for monitoring traffic signal preemption at one or more intersections. According to one embodiment, a road map that includes a plurality of roads and intersections is displayed with a computer system. Preemption data periodically received by the computer system from at least one preemption controller at a respective intersection is used to update the road map. In response to the preemption data, the road map is updated to include a traffic signal icon at the respective intersection and a vehicle icon at a location on the map corresponding to a location of a vehicle transmitting a preemption request as indicated by the preemption data.

Abstract: A file operations engine is provided that manages many user interactions with their files via a computer system. The operation engine may provide a user with the option to keep both files that have a file name conflict. It may further permit the user to rename a file involved with a file name conflict. The operations engine may also automatically rename one of the files of a file name conflict by appending a character to a root of the filename. The character may include the lowest integer available for the root in a destination for the files. The operations engine may provide the option to keep both files as part of a pre-calculation of potential errors for a requested operation. The operations engine may place file name conflicts in an error queue and permit the user to select an option to keep both files after the conflict is encountered.

Abstract: An adhesive device used as a wound dressing, ingredient delivery device or IV hold-down in which inadvertent edge release of these devices along the periphery of the polymeric film layer is minimized when the handling layer, which is adhered to the polymeric film layer, is removed after application of the polymeric film layer to the patient.

Abstract: A file operations engine is provided that manages many user interactions with their files via a computer system. The operation engine may provide a user with the option to keep both files that have a file name conflict. It may further permit the user to rename a file involved with a file name conflict. The operations engine may also automatically rename one of the files of a file name conflict by appending a character to a root of the filename. The character may include the lowest integer available for the root in a destination for the files. The operations engine may provide the option to keep both files as part of a pre-calculation of potential errors for a requested operation. The operations engine may place file name conflicts in an error queue and permit the user to select an option to keep both files after the conflict is encountered.

Abstract: A file operations engine is provided that manages many user interactions with their files via a computer system. The operation engine may provide a user with the option to keep both files that have a file name conflict. It may further permit the user to rename a file involved with a file name conflict. The operations engine may also automatically rename one of the files of a file name conflict by appending a character to a root of the filename. The character may include the lowest integer available for the root in a destination for the files. The operations engine may provide the option to keep both files as part of a pre-calculation of potential errors for a requested operation. The operations engine may place file name conflicts in an error queue and permit the user to select an option to keep both files after the conflict is encountered.

Abstract: A file operations engine is provided that manages many user interactions with their files via a computer system. The operation engine may provide a user with the option to keep both files that have a file name conflict. It may further permit the user to rename a file involved with a file name conflict. The operations engine may also automatically rename one of the files of a file name conflict by appending a character to a root of the filename. The character may include the lowest integer available for the root in a destination for the files. The operations engine may provide the option to keep both files as part of a pre-calculation of potential errors for a requested operation. The operations engine may place file name conflicts in an error queue and permit the user to select an option to keep both files after the conflict is encountered.

Abstract: A file operations engine is provided that manages many user interactions with their files via a computer system. The operation engine may place certain classes of errors in an error queue while performing a requested operation without waiting for a user to satisfy the errors prior to continuing with the operation. In addition, the operations engine may pre-calculate potential errors for a requested operation prior to performing the operation. Dialogs may be provided to a user to satisfy errors listed in an error queue and/or identified while pre-calculating potential errors. Methods are provided for handling file operations errors and for interacting with a user interface for file operations. Computer-executable instructions for implementing the disclosed methods are stored on computer-readable media.

Abstract: Adhesive devices used as wound dressings, ingredient delivery devices and IV hold-downs include a handling layer comprised of a layer of conductive material and at least one layer of non-conductive material, adhered to the non-adhesive coated side of an adhesive coated polymeric film layer, by an electrostatic charge, rather than by an adhesive.

Abstract: Adhesive devices used as wound dressings, ingredient delivery devices and IV hold-downs include a handling layer comprised of a layer of conductive material and at least one layer of non-conductive material, adhered to the non-adhesive coated side of an adhesive coated polymeric film layer, by an electrostatic charge, rather than by an adhesive.

Abstract: A file operations engine and other programming mechanisms are provided for handling file operations errors related to permissions. A file operations engine according to an embodiment of the invention manages many user interactions with their files via a computer system including options for taking a permission for a resource, such as a file, a folder or other object. The operations engine may enable another person to provide a user with a necessary permission for a resource. The operations engine or other programming mechanisms can provide dialogs and user interface mechanisms for handling permissions errors.