Abstract: A system, method and non-transitory, computer-readable storage medium are disclosed for implementing dynamic layout rules for attributed text strings having different type styles. In some implementations, developers can use an Application Programming Interface (API) or a design tool to specify dynamic text layout rules for rendering attributed text strings in a user interface (UI). Various text attributes associated with the different type styles (e.g., font metrics) are dynamically adjusted based on the dynamic text layout rules to improve the readability of the text when, for example, font sizes are adjusted. In some implementations, one or more parameters of a text container, text container region, line-fragment or display object are dynamically adjusted based on the dynamic text layout rules to improve the readability of the text.

Abstract: In accordance with some embodiments, a method is performed at a device with one or more processors, non-transitory memory, a display, and an input device. The method includes displaying, on the display, a first column and a second column in an application region. The method includes detecting, via the input device, a first user input that starts at a location at a top of the application region and moves toward an edge of the application region. The method includes, in response to detecting the first user input, changing the number of columns displayed in the application region, wherein changing the number of columns displayed in the application region includes, in accordance with a determination that the first user input was in a first direction, displaying a third column in the application region while maintaining display of the first column and the second column in the application region.

Abstract: A software application includes a plurality of views and an application state. The application includes instructions for displaying one or more views, where a respective view includes a respective gesture recognizer having a corresponding delegate, detecting one or more touches on a touch-sensitive surface, and processing a respective touch. The processing includes obtaining a receive touch value based on the application state by executing the delegate; when the receive touch value meets predefined criteria, processing the respective touch at the respective gesture recognizer; and conditionally sending information corresponding to the respective touch to the software application in accordance with an outcome of the processing by the respective gesture recognizer and in accordance with the receive touch value determined by the delegate. The software application is executed in accordance with the outcome of the processing of the respective touch by the respective gesture recognizer.

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 software application includes a plurality of views and an application state. The method includes displaying one or more views, where a respective view includes a respective gesture recognizer having a corresponding delegate to the respective gesture recognizer. The method includes detecting one or more events and processing a respective event of the one or more events using the respective gesture recognizer. The processing of the respective event includes processing the respective event at the respective gesture recognizer in accordance with a respective gesture definition corresponding to the respective gesture recognizer, executing the corresponding delegate to determine one or more values, and conditionally sending information corresponding to the respective event to the software application in accordance with the one or more values determined by the delegate. The method includes executing the software application in accordance with information, received from the respective gesture recognizer.

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: An electronic device, with a touch-sensitive surface and display, displays a user interface at a first display rate. While displaying the user interface in accordance with the first display rate, the device detects movement of a touch input, including detecting the touch input at a first set of sequential locations on the touch-sensitive surface, including a plurality of locations on the touch-sensitive surface, and predicts for the touch input a first set of one or more predicted locations on the touch-sensitive surface based on multiple locations in the first set of sequential locations. The device updates the user interface in accordance with the first set of one or more predicted locations of the touch input on the touch-sensitive surface.

Abstract: An electronic device, with a touch-sensitive surface and display, displays a user interface at a first display rate. While displaying the user interface, the device detects, at a first detection rate that is greater than the first display rate, movement of a touch input at a sequence of locations on the touch-sensitive surface; and, at each of a sequence of update times, updates the user interface from a respective current state to a respective next state in accordance with a selected subset of the sequence of locations of the touch input. Each selected subset of the sequence of locations includes a plurality of locations of the touch input.

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: 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 system, method and non-transitory, computer-readable storage medium are disclosed for implementing dynamic layout rules for attributed text strings having different type styles. In some implementations, developers can use an Application Programming Interface (API) or a design tool to specify dynamic text layout rules for rendering attributed text strings in a user interface (UI). Various text attributes associated with the different type styles (e.g., font metrics) are dynamically adjusted based on the dynamic text layout rules to improve the readability of the text when, for example, font sizes are adjusted. In some implementations, one or more parameters of a text container, text container region, line-fragment or display object are dynamically adjusted based on the dynamic text layout rules to improve the readability of the text.

Abstract: A system, method and computer-readable medium are disclosed for generating and animating GUI elements.

Abstract: A system, method and computer-readable medium are disclosed for dynamically adjusting font metrics. In some implementations, type styles are specified for text by an application running on an electronic device. If a user setting (e.g., font size) indicates a preferred type style (e.g., different font size), then the preferred type style is retrieved and one or more font metrics (e.g., leading, tracking, kerning) for the preferred type style are dynamically adjusted according to one or more rules. The text is rendered using the preferred type style with the adjusted font metric(s).

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: 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 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: 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: 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: A software application includes a plurality of views and an application state. The method includes displaying one or more views, where a respective view includes a respective gesture recognizer having a corresponding delegate to the respective gesture recognizer. The method includes detecting one or more events and processing a respective event of the one or more events using the respective gesture recognizer. The processing of the respective event includes processing the respective event at the respective gesture recognizer in accordance with a respective gesture definition corresponding to the respective gesture recognizer, executing the corresponding delegate to determine one or more values, and conditionally sending information corresponding to the respective event to the software application in accordance with the one or more values determined by the delegate. The method includes executing the software application in accordance with information, received from the respective gesture recognizer.