In most cases, we recommended that developers not override the default sizing. In the new, simplified approach, the default column sizing is based on 75 percent of the base input control sizing. By using personalization, each user can change the width of grid columns, and the client keeps track of that user's preference. Instead, the end user decides which columns are most important to view and the ideal viewing width for each of those columns. The new approach disregards the contents of the first page of data. Sizing grid columnsĬolumn sizing in a grid control differs slightly from the legacy algorithm, which tried to provide an initial appealing presentation for each grid, based partly on the contents of the first page of data. These sizes are determined by inspecting the explicitly specified width in the DisplayLength property of the control or the corresponding extended data type (EDT). As part of an attempt to provide consistent and uniform layout of forms, each input control is sized to one of four sizes: extra-small (XS), small (S), medium (M), or large (L).
The control framework attempts to provide a fresh, clean user experience that provides simplicity and consistency. The introduction of discrete sizing is a significant change to the basic input controls. To provide streamlined, easy-to-read interfaces, discrete sizing helps guarantee consistent presentation of data. For example, the customer name in one form might show 10 characters of information, whereas the customer name in another form might show 20 characters of information. However, that level of freedom can lead to inconsistent presentation of data and a non-uniform layout for similar forms. Many frameworks offer complete freedom over the width of input controls.
Different kinds of sizes smedium how to#
This article describes how to create a consistent look and feel for forms by controlling the size of controls and grids.
0 kommentar(er)
