nTop, nLeft, nBottom, nRightNumericRequired
Window coordinates. With PIXEL, they represent the pixel area used by SmartClient.
CLASSPublished
TDialog
TDialog():New( <nTop>, <nLeft>, <nBottom>, <nRight>, <cTitle>, ... )Creates a dialog window to host visual components in AdvPL routines.
Overview
TDialog is a visual class used to create dialog windows in SmartClient. It works as a container for components such as SAY, GET, BUTTON, CHECKBOX, BITMAP, BROWSE, FOLDER and panels. In a typical screen, the routine creates the dialog, adds components by informing their parent object and finally calls Activate() to display the window and hand control to the interface.
Syntax
TDialog():New( <nTop>, <nLeft>, <nBottom>, <nRight>, <cTitle>, ... )Parameters
cTitleCharacterRequired
Title displayed in the window bar.
Text/background colorsNumericOptional
Colors used in the window, usually supplied through color constants available in include files.
lPixelsLogicalOptional
Indicates that the provided measures should be interpreted as pixels.
Activate()MethodRequired
Displays the dialog. Depending on the LIB version, it may receive options such as centering and an activation block.
Simple TDialog window
#Include "TOTVS.ch"
User Function ExTDialog()
Local oDlg
Local nHeight := 180
Local nWidth := 360
Local lUsePixels := .T.
Local lCentered := .T.
Local bOnStart := {|| ConOut("Dialog activated") }
oDlg := TDialog():New(0, 0, nHeight, nWidth, ;
"Screen using TDialog", , , , , , , , , lUsePixels)
oDlg:Activate(, , , lCentered, , , bOnStart)
ReturnExpected result
The dialog is created in memory and displayed centered. bOnStart is executed during activation.
TDialog as a component container
#Include "TOTVS.ch"
User Function ExTDialogCampos()
Local oDlg
Local cNome := Space(40)
oDlg := TDialog():New(0, 0, 160, 380, "Cadastro rápido", , , , , , , , , .T.)
@ 20, 20 Say "Nome:" Size 40, 10 Of oDlg Pixel
@ 18, 65 Get cNome Size 140, 10 Of oDlg Pixel
@ 50, 65 Button "Confirmar" Size 65, 14 ;
Action MsgInfo("Olá, " + AllTrim(cNome)) Of oDlg Pixel
oDlg:Activate(, , , .T.)
ReturnExpected result
SAY, GET and BUTTON are created as children of oDlg. When the button is clicked, the ACTION block uses the typed value.
Declarative form with DEFINE DIALOG
#Include "TOTVS.ch"
User Function ExDefineDialog()
Local oDlg
Define Dialog oDlg Title "Exemplo declarativo" ;
From 0, 0 To 160, 380 Pixel
@ 25, 25 Say "Interface criada por comando" ;
Size 150, 12 Of oDlg Pixel
Activate Dialog oDlg Centered
ReturnExpected result
DEFINE/ACTIVATE syntax is more declarative and is translated by the compiler into calls to the corresponding visual classes.
- Use TDialog when you need a modal custom window for data entry, confirmation or information display.
- Pass the dialog object as the parent of visual components, usually through the OF oDlg clause.
- Keep screen construction in three clear steps: create the dialog, place the components and activate the window.
- Prefer variable names that express the visual role of the object, such as oDlg, oGetName, oBtnConfirm and oSayStatus.
- For complex screens, consider FWDefSize, FWLayer, MVC or framework components that help with organization and resizing.
- A modal dialog blocks interaction with the parent window while it is open; this is expected behavior.
- Components without the correct parent may not appear or may be attached to the wrong active window.
- Mixing pixel coordinates with another unit may cause alignment differences between environments.
- Large ACTION blocks make maintenance harder; call helper functions instead.
- Do not use TDialog as a substitute for MVC when the screen requires a data model, structured validations and integration with maintenance routines.
Comments
There are no approved comments yet.
Sign in with Google or Microsoft to comment.