Synchronized scrolling applies to all screens having two or more scrollable fields. With this scrolling style, all scrollable fields are scrolled at the same time and in the same direction, based on the scroll command the user enters.
When the viewports of the scrollable fields are different sizes, the smaller viewport is used when determining how many rows to scroll forward or backward.
For example, if one viewport contains five rows and another viewport contains seven rows, then five is the viewport size CA Gen uses to scroll both fields.
When the data view boundaries are different for all fields, the largest data view extent is used to determine the boundaries for all fields. It does not matter whether the fields are protected or unprotected.
For example, when there are two repeating group views, one with an extent of 50 and the other with an extent of 100, then the extent size of 100 is used as the data view boundaries for both repeating groups for the purpose of scrolling. Also, if there are two data views, one protected and a population of 90, and another unprotected with an extent of 200, then the scroll boundary for both is 200. The protected data view is extended (logically) by 110 to make up the missing rows. In this case, the viewport for the protected data view is scrolled past the boundary and the viewport is spaced and protected to prevent entry even if the fields are not defined as protected.
When there are mismatches between the boundary sizes of the repeating group views, then the unpopulated areas of each view can be modified by the user if the screen property for unused occurrences is set to Unprotected to Allow Updates. The unpopulated areas of each view cannot be modified by the user if the screen property for unused occurrences is set to Protected to Prevent Update. In either case, the viewport is protected for undefined areas of any data views that are smaller than the data view extent.
|
Copyright © 2013 CA.
All rights reserved.
|
|