Use Subfile recognition rules to configure global datagrid settings and add markers that are used to indicate the presence of subfiles in host application screens. Subfile markers are used to delimit the end of the subfile data and to determine which vertical scrolling actions (up or down) are available.
Stored within the Dynamic Design Repository, Newlook uses this information when converting host application screens into graphically rich GUI-based screens. As part of the dynamic translation process, Newlook searches through all host screen elements looking for any predefined subfile markers. If a subfile marker is identified and the surrounding host screen elements are consistent with a subfile, Newlook generates a grid control.
You can access Subfile recognition rules by selecting Rules | Subfiles from the developer bar. Subfiles markers will be applied in the same order as they are listed in the Subfiles description window. To view an individual subfile marker's properties, select it from the Subfiles search string description list and expand the property windows on the right.
Common examples of subfile markers include "+" and "More…".
(This is the Drop-down text)
Use the Subfile Search options to define the search parameters.
Option |
Description |
Search for |
This is the string that the recognition will search for and identify as a subfile marker. Refer to wildcards box below. |
Case sensitive |
When selected, only find text that has the exact same pattern of upper and lower case characters as the search string. |
Match |
|
Match field exactly |
Find only host screen text that exactly matches the pattern of characters specified in the search string. |
Match leading portion of a field |
Find only host screen text that starts with the same pattern of characters specified in the search string. |
Match trailing portion of a field |
Find only host screen text that ends with the same pattern of characters specified in the search string. |
Match any portion of a field * |
Find host screens text that contains the letters you specify anywhere within in a string. |
Paging |
|
Enable page up |
Enables the page up scroll bar button for grids using the subfile marker. |
Enable page down |
Enables the page down scroll bar button for grids using the subfile marker. |
The Search for string may include wildcards. Use the '?' character to match any single character. For example; the Search for string "CMD ? to " will match "CMD 1 to Exit", "CMD 4 to Prompt", "CMD 6 to Add" etc. To search for the '?' character, you must include a ' \ ' character as the '?' character is used as a wildcard character. To treat the '?' character as part of the search string, include the '?' with a ' \ ’: character (‘ \? ’).
Use Range options to specify the row and column search range. Specifying a specific row and column range increases search efficiency by reducing the amount of time Newlook takes to locate a subfile marker.
Option |
Description |
All rows |
Search all of the rows on the host screen. |
Start row/End row |
Enter a range specifying the starting and ending screen rows to search. Select from top edge or from bottom edge to specify where to start the search, relative to the screen. |
All columns |
Search all of the columns on the host screen. |
Start column/End column |
Enter a range specifying the starting and ending screen columns to search. Select from left edge or from right edge to establish where to start the search, relative to the screen. |
Use Locale information to customize subfile marker recognition rules for specific regional requirements. If a locale is specified here, then the selected filter will only be applied if the locale specified is the same as the locale of the connection .
For example, if the selected locale for a subfile marker is German (All), the subfile recognition filter will be applied to all German screens, including variations such as German (Austria).
Any combination of locales can be selected so as subfile markers can be applied to German (Luxembourg) and German (Liechtenstein), but no other variations of German.
Option |
Description |
All locales |
Subfile marker recognition filters can be applied universally be checking the option All Locales. |
Option |
Description |
Default subfile option |
Normally, all host screen subfiles that allow users to input a value for a given row have corresponding subfile options (for example 7 = Display Message, or 6 = Release). In Newlook, users can input these options by either right-clicking on a row within the subfile grid and selecting an option from the resulting menu, typing a value using the keyboard or by double-clicking on a row. Where valid options are listed for a given subfile Newlook will associate the first listed option as the default subfile option for that grid. If users choose to double-click on a given row within the subfile the first option in that list will be sent to the host. If a row has more than one subfile input field Newlook will place the subfile option within the first subfile entry field. If Newlook is unable to determine what the valid options are for a given subfile it will display its own default option as specified under rules/subfiles. When Newlook is first installed this value is 1 but this can be customized according to your host application settings, e.g. this could be a specific number or question mark (?). It is also possible to have no default subfile option defined under rules/subfiles in which case the right-click menu in Newlook will appear with no selection options (not an optimal solution). |
Automatically detect grid columns |
If this option is selected, the Newlook recognition engine attempts to organize data in data grid control into columns. If columns are easily identified then the grid's ShowColumns property defaults to True. Where the newlook recognition engine cannot identify any logical columns in the data grid then the property defaults to False and columns are not displayed. Items that may affect the recognition engine's ability to detect columns include: column headers that do not line up logically with column data, differing number of columns per row and attribute byte placement. It is possible to turn on column recognition if columns have not been automatically detected by setting this property to True in Designer or at Runtime via a script or macro. In doing this, the recognition engine will organize the grid data into columns, adding additional columns where necessary to display the data logically. Set this option to False if you do not want columns generated for grids in Newlook. By default this option is set to True. |
Introduced in 11.0.9. If this option is enabled, Newlook will search for any host fields that are present in the row directly above a detected subfile header and, provided the following criteria is met, will set their default AlignToGridColumn property to the most suitable column name:
This option can be turned off for individual forms via the AlignControlsToGridColumns property. |
|
Automatically fit columns to full grid width |
Determines whether columns in all grid controls are automatically sized to accommodate the widest cell contents in the column. By default this option is set to False. Setting this property to True will automatically size all columns in all grid controls so that they accommodate the widest cell contents in the column. |
Introduced in 11.0.5. This global setting allows you to hide the Option column of all host-generated grids in your application. To determine which column to hide, Newlook uses the column specified in the DataGrid.OptionColumn property. If this property has not been set, it will hide the first entry-capable column (from left-to-right) in the grid. Note that even though this column is hidden, all grid option selection functionality will operate as normal; the user will be able to right-click to open the drop-down listing all grid options or double-click a row to issue the default option against that row. This setting is ignored for ADO/DDM bound and OA-enabled grids. |
|
Introduced in 11.0.6. This global setting allows you to hide the vertical scrollbar in all host-generated grids in your application. It is possible to override this setting for individual grids by setting the ShowVertScrollBar property of the grid to ShowScrollAlways, allowing you to turn on scrollbars for specific grids. This setting is ignored for ADO/DDM bound and OA-enabled grids. |
|
Introduced in 11.0.5. This option allows you to specify the default value for the AllowSort property for all datagrid columns in your application. It is still possible to enable or disable the AllowSort property for individual datagrid columns, this option will only affect the default value of this property. |
|
Introduced in 11.0.0. This setting only applies to DataGrid controls bound to an external data source (it does not apply to DataGrid controls generated from host screen subfiles). It allows you to specify whether or not new columns should be automatically added to grids when new fields are added to the bound database, after the grid control has been created. In older versions of Newlook, once a grid was saved, the columns in the grid would remain static, even if new fields were added to the underlying data source changed. This behavior was changed in Newlook 10. From version 10 onwards, new columns are automatically added to bound DataGrid controls when new fields are added to the data source. The Add new database fields as new columns option provides compatibility for both scenarios. This setting defaults to True, which means that new fields in your bound data source will appear as new columns in the grid. This setting does not have any effect on host screen subfiles, which will always display new columns if new data appears on screen. |
|
Default OpenLook subfile block size |
This setting specifies the default number of records to request per block when requesting records from OpenLook. This rule can be overridden for individual grid controls by setting the BlockSize property of the relevant grid in Designer. Block size determines both the initial number of records that will be downloaded but also the additional download size whenever there is a subsequent request to the host (i.e. the user scrolls down). A large BlockSize number may have an impact on the speed of grid scrolling. If the Load all records in OpenLook subfile option is checked, then newlook will still request the number of records specified in this setting, however, it will load all records in batches of that size. |
Load all records in OpenLook subfile |
This option, if checked, loads all records in an OpenLook subfile when loading the screen. By default this option is unchecked to prevent delays in loading for those screens containing subfiles with large numbers of records. If you know that your subfile only has a small number of records then you may wish to set check this option. |
This process can be used to create a global Rule to identify common host subfiles in your application.
If you want to insert an manual subfile marker for an individual screen using Identify, see the section "Creating a Subfile Marker Using Identify".
Datagrid control | Manually recognizing subfiles in Identify
© 2004-2021 looksoftware. All rights reserved.