noEntry

noEntry prevents data input during input dialogs.

By default, noEntry is not specified and, thus, is absent from the form XML code. The property value will appear in the form XML code only once it is specified.

Form XML Code:

<CheckBox title="New check box" visible="true" notNull="true" identifier="f1" gridItemLocation="0,0,1,1" noEntry="true">

Possible values:

false, true

Default value:

false

Associated containers, widgets and theme elements:

Table

Calendar

CheckBox

ComboBox

FunctionField

ListBox

Spinner

TextArea

TextField

TimeEditField

Influence and behavior:

When set to true, the noEntry property inhibits data input during the INPUT and INPUT ARRAY statements.

Widgets with noEntry set to true are disabled, and they cannot get the focus. At runtime, they are greyed:

MAIN
DEFINE f1, f2 DATE
OPEN WINDOW w WITH FORM "noEntry"
MENU
  COMMAND "INPUT"
    INPUT BY NAME f1, f2
  COMMAND "EXIT"
    EXIT MENU
END MENU
END MAIN

With a Table container, text fields and areas with noEntry=true are not greyed at runtime though they still are prevented from input:

noEntry does not inhibit data input during a CONSTRUCT statement:

MAIN
DEFINE f1, f2 char(30)
DEFINE tCon STRING
OPEN WINDOW w WITH FORM "noEntry_construct"
CONSTRUCT BY NAME tCon ON f1, f2
DISPLAY tCon
END MAIN

With the WITHOUT DEFAULTS dialog option, the content of the corresponding program variable is displayed in the field:

MAIN
DEFINE f1, f2 CHAR(20)
LET f1 = 55
LET f2 = 77
OPEN WINDOW w1 WITH FORM "noEntry_without_defaults"
INPUT BY NAME f1, f2 WITHOUT DEFAULTS
INPUT f2, f1 WITHOUT DEFAULTS FROM f1, f2
END MAIN

 

 

Contact Us

Privacy Policy

Copyright © 2024 Querix, (UK) Ltd.