Abstract: At least certain embodiments of the present disclosure include an environment with user interface software interacting with a software application. A method for operating through an application programming interface (API) in this environment includes transferring a set bounce call. The method further includes setting at least one of maximum and minimum bounce values. The set bounce call causes a bounce of a scrolled region in an opposite direction of a scroll based on a region past an edge of the scrolled region being visible in a display region at the end of the scroll.

Abstract: A device with a touch-sensitive surface detects a touch on the touch-sensitive surface, determines that the touch is cancelled, and in accordance with a determination that the touch is cancelled, sends a touch cancel event to at least one of the one or more applications. Also disclosed is a device configured to determine that a respective touch has been cancelled by the device. If the respective touch has been cancelled, the device ignores the respective touch. If the respective touch has not been cancelled, the device processes the respective touch. In addition, a device configured to detect one or more touches and process at least a subset of the touches with at least one application is described. While processing at least a subset of the touches, the device receives a touch cancel event, and, in response to receiving the touch cancel event, ignores the touches.

Abstract: Embodiments of the present invention are directed to methods, software, devices and APIs for defining touch events for application level software. Furthermore, some embodiments are directed to simplifying the recognition of single and multiple touch events for applications running in multi-touch enabled devices. To simplify the recognition of single and multiple touch events, each view within a particular window can be configured as either a multi-touch view or a single touch view. Furthermore, each view can be configured as either an exclusive or a non-exclusive view. Depending on the configuration of a view, touch events in that and other views can be either ignored or recognized. Ignored touches need not be sent to the application. Selectively ignoring touches can allow for simpler software elements that do not take advantage of advanced multi touch features to be executed at the same device and time as more complex software elements.

Abstract: A device with a touch-sensitive surface detects one or more touches that start within a view on the touch-sensitive surface, and processes the one or more touches on the touch-sensitive surface with a software element associated with the view. The device receives, at the software element associated with the view, a touch event that includes data structure including a phase value indicating that a respective touch on the touch-sensitive surface has been canceled by the device. The device responds to receiving the touch event by ignoring the respective touch on the touch-sensitive surface.

Abstract: At least certain embodiments of the present disclosure include an environment with user interface software interacting with a software application. A method for operating through an application programming interface (API) in this environment includes transferring a set bounce call. The method further includes setting at least one of maximum and minimum bounce values. The set bounce call causes a bounce of a scrolled region in an opposite direction of a scroll based on a region past an edge of the scrolled region being visible in a display region at the end of the scroll.

Abstract: At least certain embodiments of the present disclosure include a method for memory management of a view of an application displayed on a display of a device. The method includes constructing a data structure having a hierarchy of layers with at least one layer being associated with the view. The method further includes storing the data structure in memory. The method further includes maintaining a retained count of the number of references to the view from other objects. The method further includes deallocating the view from memory if the retained count is zero. As discussed above, the retained count of the view will be decremented if the layer is removed from the data structure. Removing the layer from the data structure may occur based on the view associated with the layer being removed from the display of the device.

Abstract: At least certain embodiments of the present disclosure include a method for animating a display region, windows, or views displayed on a display of a device. The method includes starting at least two animations. The method further includes determining the progress of each animation. The method further includes completing each animation based on a single timer.

Abstract: Embodiments of the present invention are directed to methods, software, devices and APIs for defining touch events for application level software. Furthermore, some embodiments are directed to simplifying the recognition of single and multiple touch events for applications running in multi-touch enabled devices. To simplify the recognition of single and multiple touch events, each view within a particular window can be configured as either a multi-touch view or a single touch view. Furthermore, each view can be configured as either an exclusive or a non-exclusive view. Depending on the configuration of a view, touch events in that and other views can be either ignored or recognized. Ignored touches need not be sent to the application. Selectively ignoring touches can allow for simpler software elements that do not take advantage of advanced multi touch features to be executed at the same device and time as more complex software elements.

Abstract: Described are devices, methods and storage media for receiving an input and issuing at least one scroll call or gesture call based on a determination whether the input consists of a single input point that moves a distance across the display or consists of a plurality of input points on the display. A scroll call, for example, causes scrolling of a window in a vertical or horizontal direction at a fixed or varying speed. A gesture call, for example, initiates various operations such as scaling of a window, rotating a window, etc.

Abstract: Embodiments of the present invention are directed to methods, software, devices and APIs for defining touch events for application level software. Furthermore, some embodiments are directed to simplifying the recognition of single and multiple touch events for applications running in multi-touch enabled devices. To simplify the recognition of single and multiple touch events, each view within a particular window can be configured as either a multi-touch view or a single touch view. Furthermore, each view can be configured as either an exclusive or a non-exclusive view. Depending on the configuration of a view, touch events in that and other views can be either ignored or recognized. Ignored touches need not be sent to the application. Selectively ignoring touches can allow for simpler software elements that do not take advantage of advanced multi touch features to be executed at the same device and time as more complex software elements.

Abstract: At least certain embodiments of the present disclosure include a method for animating a display region, windows, or views displayed on a display of a device. The method includes starting at least two animations. The method further includes determining the progress of each animation. The method further includes completing each animation based on a single timer.

Abstract: The application programming interface operates in an environment with user interface software interacting with multiple software applications or processes in order to synchronize animations associated with multiple views or windows of a display of a device. The method for synchronizing the animations includes setting attributes of views independently with each view being associated with a process. The method further includes transferring a synchronization call to synchronize animations for the multiple views of the display. In one embodiment, the synchronization call includes the identification and the number of processes that are requesting animation. The method further includes transferring a synchronization confirmation message when a synchronization flag is enabled. The method further includes updating the attributes of the views from a first state to a second state independently.

Abstract: Described are devices, methods and storage media for receiving an input and issuing at least one scroll call or gesture call based on a determination whether the input consists of a single input point that moves a distance across the display or consists of a plurality of input points on the display. A scroll call, for example, causes scrolling of a window in a vertical or horizontal direction at a fixed or varying speed. A gesture call, for example, initiates various operations such as scaling of a window, rotating a window, etc.

Abstract: A method that may be performed at an electronic device that has one or more processors, memory, and a touch-sensitive display. The method includes receiving a user input, the user input is one or more input points applied to a touch-sensitive display that is integrated with the data processing system. The method further includes creating an event object in response to the user input and determining whether the event object invokes a scroll or gesture operation by distinguishing between the user input being a single input point applied to the touch-sensitive display that is interpreted as the scroll operation and the user input being more than one input point applied to the touch-sensitive display that are interpreted as the gesture operation.

Abstract: At least certain embodiments of the present disclosure include a method for memory management of a view of an application displayed on a display of a device. The method includes constructing a data structure having a hierarchy of layers with at least one layer being associated with the view. The method further includes storing the data structure in memory. The method further includes maintaining a retained count of the number of references to the view from other objects. The method further includes deallocating the view from memory if the retained count is zero. As discussed above, the retained count of the view will be decremented if the layer is removed from the data structure. Removing the layer from the data structure may occur based on the view associated with the layer being removed from the display of the device.

Abstract: At least certain embodiments of the present disclosure include a method for animating a display region, windows, or views displayed on a display of a device. The method includes starting at least two animations. The method further includes determining the progress of each animation. The method further includes completing each animation based on a single timer.

Abstract: At least certain embodiments of the present disclosure include a method for animating a display region, windows, or views displayed on a display of a device. The method includes starting at least two animations. The method further includes determining the progress of each animation. The method further includes completing each animation based on a single timer.

Abstract: At least certain embodiments of the present disclosure include a method for memory management of a view of an application displayed on a display of a device. The method includes constructing a data structure having a hierarchy of layers with at least one layer being associated with the view. The method further includes storing the data structure in memory. The method further includes maintaining a retained count of the number of references to the view from other objects. The method further includes deallocating the view from memory if the retained count is zero. As discussed above, the retained count of the view will be decremented if the layer is removed from the data structure. Removing the layer from the data structure may occur based on the view associated with the layer being removed from the display of the device.

Abstract: A method performed at an electronic device that has one or more processors, memory, and a touch-sensitive display includes transferring a set bounce call to provide a bounce operation. Transferring the set bounce call causes a bounce of a scrolled content region in an opposite direction of a scroll. The scrolled region includes an information object that bounces in the opposite direction of the scroll when the information object reaches or intersects a terminus, and the scrolled content region has a first velocity before the bounce and a second velocity, distinct from the first velocity, after the bounce.

Abstract: Embodiments of the present invention are directed to methods, software, devices and APIs for defining touch events for application level software. Furthermore, some embodiments are directed to simplifying the recognition of single and multiple touch events for applications running in multi-touch enabled devices. To simplify the recognition of single and multiple touch events, each view within a particular window can be configured as either a multi-touch view or a single touch view. Furthermore, each view can be configured as either an exclusive or a non-exclusive view. Depending on the configuration of a view, touch events in that and other views can be either ignored or recognized. Ignored touches need not be sent to the application. Selectively ignoring touches can allow for simpler software elements that do not take advantage of advanced multi touch features to be executed at the same device and time as more complex software elements.