PC SOFT

ONLINE HELP
FOR WINDEV, WEBDEV AND WINDEV MOBILE

Home | Sign in | English US
  • The steps for creating a RAD pattern
  • Creating the different windows of the pattern
  • The files to create
  • Standard to follow
  • The link buttons
WINDEV
WindowsLinuxUniversal Windows 10 AppJavaReports and QueriesUser code (UMC)
WEBDEV
WindowsLinuxPHPWEBDEV - Browser code
WINDEV Mobile
AndroidAndroid Widget iPhone/iPadApple WatchUniversal Windows 10 AppWindows Mobile
Others
Stored procedures
Creating the link buttons in the windows of a WINDEV RAD pattern
The steps for creating a RAD pattern
The steps for creating a WINDEV RAD pattern are as follows:
  1. Creating the "RAD Pattern" project.
  2. Creating the different windows of the pattern.
  3. Generating the RAD pattern.
  4. Using the RAD pattern.
Creating the different windows of the pattern

The files to create

Reminder: To build a RAD pattern used to create a full project, the following files are required:
  • A form for RADFileA.
  • A form for RADFileB. A combo box and a Vision Plus button (or a popup combo box) must allow you to select an element of RADFileA.
  • A form for RADFileC. A combo box and a Vision Plus button (or a popup combo box) must allow you to select an element of RADFileB.
  • A table for RADFileA.
  • A table for RADFileB.
  • A table for RADFileC.
  • A relation window RADFileB/RADFileD.
These different elements must contain link buttons. You also have the ability to provide the main menu of the application.

Standard to follow

This help page presents the different rules that must be applied when creating the pages and windows of the RAD pattern. These rules have been used to create the different patterns supplied with WINDEV 16.
These rules are recommendations. You can implement and use your own standard.
The link buttons
The Form or Table windows can include link buttons. These link buttons are used to display a table, a form or a table + form on linked files for example.
A simple example: viewing the orders of a customer from the form of the customer.
A link button must necessary be named:
  • BTN_TableLink_RADFileX for a link to a table window
  • BTN_FormLink_RADFileX for a link to a form window
  • BTN_RelationLink_RADFileX for a link to a relation window.
Note: BTN_ is the prefix defined in the programming charter: it is not required if no programming charter is used.
Any caption can be used. However, we recommend that you use a simple caption ("RADFileB table" or "RADFileA form" for example).
Code: Example of code that can be used in a link button, allowing you to open a table on the RADFileB file from the form on RADFileA:
// Implement the filter on the link key
HFilter(RADFileB,IDRADFileARel, RADFileA.IDRADFileA)
// Open the table window of RADFileB
Open(WIN_Table_RADFileB)
// Disable the filter
HDeactivateFilter(RADFileB)
Position of the link buttons and additional link buttons
The link buttons can be positioned anywhere in the window. When generating the window, the link buttons will be created at the specified location. Depending on the size of the analysis used by RAD, more than 3 link buttons can be found in a window. Therefore, we recommend that you plan for additional link buttons.
These addition buttons are used to position the link buttons. Indeed, the link buttons can be aligned horizontally, vertically or even in circle.
The additional link buttons must have a specific name: BTN_LINK_n (BTN_ is the prefix defined in the programming charter: it is not required if no programming charter is used), where n is the number of the button (BTN_LINK_1 for example). These buttons must contain no code and they must be associated with no preset action.
Note: When performing the RAD generation, if the number of link buttons is greater than the number specified in the pattern, the additional generated buttons will be overlaid over the position of the last link button positioned in the pattern.
Minimum required version
  • Version 12
Comments
Click [Add] to post a comment