| PinchClose |
|
Perform a shrinking "zoom out" operation on a touchscreen device supporting the feature. | |
| PinchOpen |
|
Perform an expanding "zoom in" operation on a touchscreen device supporting the feature. |
| IOS |
Effectively shrinks a user-defined rectangular area on the screen.
IOS expects the Window/Component to be the main active Window of the application.
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:
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.
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:
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.
| IOS |
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.
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:
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.
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:
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.