IOS WindowFunctions

Last Updated:

Actions for working with Window objects


[How To Read This Reference]
PinchClose
IOS
Perform a shrinking "zoom out" operation on a touchscreen device supporting the feature.
PinchOpen
IOS
Perform an expanding "zoom in" operation on a touchscreen device supporting the feature.

IOS WindowFunctions::PinchClose
IOS

Perform a shrinking "zoom out" operation on a touchscreen device supporting the feature.

Perform a shrinking "zoom out" operation on a touchscreen device supporting the feature.

Effectively shrinks a user-defined rectangular area on the screen.

IOS expects the Window/Component to be the main active Window of the application.



Fields: [ ]=Optional with Default Value
  1. OriginSubKey
    The AppMapSubkey that contains the onscreen rectangle for the pinch operation.

    Name of the AppMap subkey to lookup and use for OriginRect or the actual literal text for the values.

    We expect the rectangle stored in the App Map or the literal text to be specified as integer rectangle coordinates and size in pixels: X,Y,Width,Height.

                   [AppWindow]
                   ...
                   Origin1="50,200,25,25"      OR
                   Origin2="Coords=100,75,125,125"
                   ...
                   

    Engines should attempt to support coordinates separated by alternate separators. The most common separators that should be supported would be:

    • "," (comma) Example: "50,200,25,25"
    • ";" (semi-colon) Example: "50;200;25;25"
    • " " (space) Example: "50 200 25 25"

    If the App Map does not contain the subkey item then the engines should assume the value is the literal text of the rectangle coordinate and size values.



  2. ResizeSubKey
    Name of the AppMap subkey to lookup for the resize value or the literal text of the resize values.

    Name of the AppMap subkey to lookup for the resize value or the literal text of the resize values.

    We expect the resize value stored in the App Map or the literal text to be specified as integer values (in pixels): +/-Width, +/-Height.

                   [AppWindow]
                   ...
                   Resize1="0,-50"   (no width change, but shrink the height by 50 pixels)  
                   Resize2="Coords=-40,0" (shrink width by 40 pixels, with no change in height.)
                   ...
                   

    These resize offsets can be positive or negative integer values and will be added to the existing width and/or height of OrigRect.

    Engines should attempt to support values separated by alternate separators. The most common separators that should be supported would be:

    • "," (comma) Example: "0,50"
    • ";" (semi-colon) Example: "0;50"
    • " " (space) Example: "0 50"

    If the App Map does not contain the subkey item then the engines should assume the value is the literal text of the resize values.



  3. [ Duration = 1 ]
    The number of seconds to take for the operation.

    Where supported, the engine should attempt to make the operation take up to N seconds in duration. The default is 1 second.

Examples:
  • T, AppWindow, AppWindow, PinchClose, Origin1, Resize2
    Pinch close the window by shrinking the Origin1 rectangle by the amounts specified in Resize2.

    Origin1 and Resize2 values are expected to be stored in the [AppWindow] section of the App Map since they are not proper literal text values. The operation will take the default 1 second.

  • T, AppWindow, AppWindow, PinchClose, Origin1, "-40;-40", 3
    Pinch close the window by shrinking the Origin1 rectangle 40 pixels in both width and height.

    Origin1 is expected to be stored in the [AppWindow] section of the App Map since it is not a proper literal text value. The operation will occur over 3 seconds.

[How To Read This Reference]

IOS WindowFunctions::PinchOpen
IOS

Perform an expanding "zoom in" operation on a touchscreen device supporting the feature.

Perform an expanding "zoom in" operation on a touchscreen device supporting the feature.

Effectively expands or stretches a user-defined rectangular area on the screen.

IOS expects the Window/Component to be the main active Window of the application.



Fields: [ ]=Optional with Default Value
  1. OriginSubKey
    The AppMapSubkey that contains the onscreen rectangle for the pinch operation.

    Name of the AppMap subkey to lookup and use for OriginRect or the actual literal text for the values.

    We expect the rectangle stored in the App Map or the literal text to be specified as integer rectangle coordinates and size in pixels: X,Y,Width,Height.

                    [AppWindow]
                    ...
                    Origin1="50,200,25,25"      OR
                    Origin2="Coords=100,75,125,125"
                    ...
                    

    Engines should attempt to support coordinates separated by alternate separators. The most common separators that should be supported would be:

    • "," (comma) Example: "50,200,25,25"
    • ";" (semi-colon) Example: "50;200;25;25"
    • " " (space) Example: "50 200 25 25"

    If the App Map does not contain the subkey item then the engines should assume the value is the literal text of the rectangle coordinate and size values.



  2. ResizeSubKey
    Name of the AppMap subkey to lookup for the resize value or the literal text of the resize values.

    Name of the AppMap subkey to lookup for the resize value or the literal text of the resize values.

    We expect the resize value stored in the App Map or the literal text to be specified as integer values (in pixels): +/-Width, +/-Height.

                    [AppWindow]
                    ...
                    Resize1="0,50"   (no width change, but grow in height by 50 pixels)  
                    Resize2="Coords=50,0" (grow width by 50 pixels, with no change in height.)
                    ...
                    

    These resize offsets can be positive or negative integer values and will be added to the existing width and/or height of OrigRect.

    Engines should attempt to support values separated by alternate separators. The most common separators that should be supported would be:

    • "," (comma) Example: "0,50"
    • ";" (semi-colon) Example: "0;50"
    • " " (space) Example: "0 50"

    If the App Map does not contain the subkey item then the engines should assume the value is the literal text of the resize values.



  3. [ Duration = 1 ]
    The number of seconds to take for the operation.

    Where supported, the engine should attempt to make the operation take up to N seconds in duration. The default is 1 second.

Examples:
  • T, AppWindow, AppWindow, PinchOpen, Origin1, Resize1
    Pinch open (zoom) the window by stretching the Origin1 rectangle by the amounts specified in Resize1.

    Origin1 and Resize1 values are expected to be stored in the [AppWindow] section of the App Map since they are not proper literal text values. The operation will take the default 1 second.

  • T, AppWindow, AppWindow, PinchOpen, Origin1, "40;40", 3
    Pinch open (zoom) the window by stretching the Origin1 rectangle 40 pixels in both width and height.

    Origin1 is expected to be stored in the [AppWindow] section of the App Map since it is not a proper literal text value. The operation will occur over 3 seconds.

[How To Read This Reference]