PC SOFT

ONLINE HELP
FOR WINDEV, WEBDEV AND WINDEV MOBILE

Home | Sign in | English US

  • Overview
  • Disabling the JITc technology
  • Managing the automatic user tests
  • Enabling the dynamic audit
  • Enabling the runtime log
  • Connections used by the application
  • Disabling the telemetry on an application
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
Overview
The <Executable Name>.WX file is used to manage some features directly, even if these features have not been included in the application. This file is found beside the executable.
This file is a text file containing different sections that correspond to the requested features.
You have the ability to manage:
Disabling the JITc technology
The principle of JITc technology (Just In Time Compilation) is straightforward: the 5GL code of WINDEV is changed on the runtime computer into "native assembler code" when it is run. See JITc technology for more details.
If you have suspicions about problems that may be caused by the JIT technology, this technology can be disabled for a specific application, by modifying (or by adding) the <Executable Name>.WX file. This file is found beside the executable. To disable the JITc technology, add the following lines:
[WD_EXECUTION]
OPTIM_EXECUTION=0
Managing the automatic user tests
WINDEV allows the user to record a test scenario in order to send it to the quality service or to the developer. Therefore, the user can easily transmit a reproduction protocol that is difficult to explain.
The developer will be able to import the tests directly into his project. These tests can be run to reproduce the problem encountered by the user and they can be added to the automatic tests of the application.
See Automatic test created by the user for more details.
The creation of a test scenario can be done without modifying the application, via the <Executable Name>.WX file. This file must contain the following lines:
[Scenario]
Enabled = <0/1>
File = <Name of WSCT file>
DLLPath = <DLL path for test>
Let's take a look at these lines:
  • Enabled: This parameter must correspond to 0 to avoid recording the scenario and to 1 to record the scenario
  • File: Name of the scenario file ("wsct" extension). This name can be built from the following elements:
    [%ExeDir%]Directory of executable, always filled with the "\" character. This directory is equivalent to the result of fExeDir.
    [%ExeName%]Executable name.
    [%Date%]Start date of scenario file.
    [%Time%]Start time of scenario file.
    [%UserName%]Name of current user.
    [%ComputerName%]Computer name.
    Versions 18 and later
    [%DataDir%]
    New in version 18
    [%DataDir%]
    [%DataDir%]
    Directory of HFSQL data files specified by the user when installing the application. This directory is equivalent to the result of fDataDir.
    Versions 18 and later
    [%DirUserData%]
    New in version 18
    [%DirUserData%]
    [%DirUserData%]
    Directory for the data of the current user of the current application. This directory is equivalent to the result of fDataDirUser.
  • DLLPath: path used to access the wdxxxtest.dll library. This DLL is required to create the scenario.
Enabling the dynamic audit
The dynamic audit of an application is used to study its performances at run time. A dynamic audit can be performed in a test environment or on a live application. The audit is used to detect problems such as:
  • Excessive memory consumption
  • Slowness of algorithms used
  • Errors "hidden" at run time
See Dynamic audit for more details.
You have the ability to audit an application in its production environment without modifying the executable: All you have to do is create, in the directory of the executable, a file named like the executable and whose extension is ".WX".
This file will have the following format:
[AUDIT]
ACTIVE = 1 (or 0 to disable the audit)
FILE = <path of the .waudit file to generate>
OPTION = <combination of the options of dbgEnableAudit>
Enabling the runtime log
The runtime log is a runtime trace. This log is a simple file (wlog extension) that contains the details of all the operations performed by a user in a WINDEV application:
  • details about the processes called,
  • WLanguage functions with their parameters,
  • user procedures with their parameters,
  • threads,
  • components.
This file allows you to:
  • find out which operations are the most frequently used in the application.
  • find out which processes take the most time.
  • follow the code run during a process that triggers problems (hard to isolate in test mode).
See Runtime log for more details.
The activation of runtime log can be done without modifying the application via a specific file. To do so, create a file named <Executable Name>.WX beside the executable of the application. This file must contain the following lines:
[LOG]
Active=<0/1>
File=<Name of WXLOG file>
Option=<Value of options>
Let's study these lines:
  • Active: This parameter must correspond to 0 to disable the log and to 1 to enable it.
  • File: Name of the log file ("wlog" extension). This name can be built from the following elements:
    [%ExeDir%]Directory of executable, always filled with the "\" character. This directory is equivalent to the result of fExeDir.
    [%ExeName%]Executable name.
    [%Date%]Start date of Log file.
    [%Time%]Start time of Log file.
    [%UserName%]Name of current user.
    [%ComputerName%]Computer name.
    Versions 18 and later
    [%DataDir%]
    New in version 18
    [%DataDir%]
    [%DataDir%]
    Directory of HFSQL data files specified by the user when installing the application. This directory is equivalent to the result of fDataDir.
    Versions 18 and later
    [%DirUserData%]
    New in version 18
    [%DirUserData%]
    [%DirUserData%]
    Directory for the data of the current user of the current application. This directory is equivalent to the result of fDataDirUser.
  • Option: Options of the log file.
    • If the options are not specified in the WX file (the OPTION line is missing), the log file is created with the default options: only the WLanguage functions are found in the log file.
    • "" (empty string): Only the processes are stored in the log.
    • "*": the log contains the full information.
    • a combination of values:
      - "+F" to enable the trace for the functions,
      - "+P" to enable the trace for the parameters.
Connections used by the application
When the application is installed on the end-user computer, depending on the selected options, the wizard allows the user to install a HFSQL Client/Server server on a Windows or Linux computer and to configure the connection used.
At the end of setup, a ".wx" file is created beside the executable.
The structure of this file is given for information. This structure can be modified in a forthcoming version. This file should not be modified manually.
This file contains the following information:
[CONNECT]
NBCX = Number of defined connections
NOM_x = Name of the connection number x
BASE_x = Type of database used (always corresponds to hAccessHFClientServer)
ADRESSE_x = Address of server used (name or IP address of the server)
PORT_x = Connection port
DATABASE_x = Name of the database used
LOGIN_x = Connection login
PWD_x = Encrypted password
ACCESS_x = Type of access (hOReadWrite or hORead)
EXTINFO_x = Extended information
Note: From version 19, HFSQL is the new name of HyperFileSQL.
Versions 21 and later
Disabling the telemetry on an application
The telemetry allows you to collect information about the use of an application by the end users. See Telemetry: Overview for more details.
You have the ability to disable the telemetry in an application:
  • by using TelemetryDisable.
  • by re-installing the application and by unchecking "Participate to the improvement...".
  • via the <Executable Name>.WX file. This file must contain the following lines:
    [WDANALYTICS]
    COLLECTE=0

    Note: This entry is not found in the <Executable Name>.WX file if the telemetry is enabled.
New in version 21
Disabling the telemetry on an application
The telemetry allows you to collect information about the use of an application by the end users. See Telemetry: Overview for more details.
You have the ability to disable the telemetry in an application:
  • by using TelemetryDisable.
  • by re-installing the application and by unchecking "Participate to the improvement...".
  • via the <Executable Name>.WX file. This file must contain the following lines:
    [WDANALYTICS]
    COLLECTE=0

    Note: This entry is not found in the <Executable Name>.WX file if the telemetry is enabled.
Disabling the telemetry on an application
The telemetry allows you to collect information about the use of an application by the end users. See Telemetry: Overview for more details.
You have the ability to disable the telemetry in an application:
  • by using TelemetryDisable.
  • by re-installing the application and by unchecking "Participate to the improvement...".
  • via the <Executable Name>.WX file. This file must contain the following lines:
    [WDANALYTICS]
    COLLECTE=0

    Note: This entry is not found in the <Executable Name>.WX file if the telemetry is enabled.
Minimum required version
  • Version 17
This page is also available for…
Comments
Click [Add] to post a comment