To meet your needs, we constantly work to improve Querix products.
This means that Lycia documentation is developing as well.
In case you have found a certain dissonance between the provided information and the actual behavior of Lycia 3 and/or your applications, please, let us know about this via documentation@querix.com so that we can introduce the necessary changes to our documentation.
Thank you for your attention and cooperation.
This function takes three arguments and is used as below:
fgl_getproperty(["gui"], type.name, value)
In the above syntax, "gui" refers to the subsystem that the property belongs to. This optional parameter defaults to "gui", so it can be omitted. The type is the element of the subsystem that the property affects; the name is the actual name of the property.
GUI properties are script-like properties that can be used to determine the overall look and functionality of a 4GL program. Unlike script options, the GUI properties are dynamic and so can be used to alter a program’s appearance during its execution, allowing for greater customization.
Other kinds of properties that you can get are:
· Read registry settings
· Env variables
· System parameters, IP address, system name, host name
· Script options currently set
· Any arbitrary user properties
|
Property Type |
Property Name |
Example |
|
System.registry |
Registry key to be read |
fgl_getproperty("system.registry" "HKEY_LOCAL_MACHINE\\SOFTWARE\\ QUERIX\\Q4GL\\QUERIXDIR") |
|
System.environment |
Environment variable name |
fgl_getproperty("system.environment", "TEMP") |
|
System.network |
"Ipaddress" |
|
|
System.network |
"hostname" |
|
|
system |
"username" |
|
|
user |
User property name |
fgl_getproperty("user.hello","myoption") |
These are the properties from the client system (not from the server).