useTabs specifies the application behavior after pressing the Tab key at runtime. |
|
in Lycia Form Designer |
|
in Lycia Theme Designer |
|
Form XML code:
<element_name useTabs="true">
By default, the property is set to false and is absent from the form XML code. The property value will appear in the form XML code only once the property value is set to true.
Theme property filter XML code:
<DoStyleAction>
<SetProperty>
<PropertyPath>
<PropertyName>UseTabs</PropertyName>
</PropertyPath>
</SetProperty>
</DoStyleAction>
Possible values: true, false
Default value: false
Associated containers, widgets and theme elements: TextArea
Associated 4gl syntax:
Associated ui methods:
setUseTabs ↓
getUseTabs ↓
Influence and behavior:
With INPUT, if useTabs is set to false, then after the Tab key is pressed, the application will move to another TextArea at runtime. Otherwise, a tab symbol will be created inside the current field:
lycia form designer |
For the first textArea (identifier=f1), useTabs=true:
|
For the first textArea (identifier=f1), useTabs=false:
|
4gl code |
MAIN DEFINE f1, f2 STRING
OPEN WINDOW w WITH FORM "useTabs" ATTRIBUTE(BORDER)
MENU COMMAND "input" INPUT BY NAME f1 WITHOUT DEFAULTS INPUT BY NAME f2 WITHOUT DEFAULTS COMMAND "exit" EXIT MENU END MENU
END MAIN
|
|
runtime appearance before pressing Tab |
||
runtime appearance after pressing Tab |
At runtime, you can use ui methods to specify the application behavior at runtime:
LET widget_var = ui.<widget>.ForName("widget_id1")
CALL widget_var.setUseTabs(...)
DISPLAY widget_var.getUseTabs()
4gl code sample |
DEFINE ta_1, ta_2 ui.TextArea ... LET ta_1 = ui.TextArea.ForName("f1") LET ta_2 = ui.TextArea.ForName("f2") ... CALL ta_1.setUseTabs(0) CALL ta_2.setUseTabs(1) DISPLAY ta_1.getUseTabs() DISPLAY ta_2.getUsetabs()
|
runtime appearance |
The example above were taken from the example program.
Example programs:
CVS server: client.querix.com
CVS repository: /lycia_doc_examples
User: client
Project: form_properties
Program: useTabs