Starts "collecting data" for the
performance profiler.
Reminder: To start the performance profiler, press: Shift + Windows + F10.
Once this function is called, all the executed processes/events are saved in a WPF file.
This file can be opened:
- by the performance profiler.
- in the editor of WINDEV, WEBDEV or WINDEV Mobile: on the "Home" tab, in the "General" group, expand "Open" and select "Open".
Versions 18 and later
New in version 18Versions 21 and later New in version 21
ProfilerStart("Test_StartProcedure.wpf")
StartProcedure()
ProfilerEnd()
Syntax
ProfilerStart([<Name of WPF file>])
<Name of WPF file>: Optional character string
Location and name of the WPF file to create. The name of the WPF file can be built from the following elements: | |
| [%ExeDir%] | Directory of the executable, always filled with the "\" character. This directory is equivalent to the result of fExeDir. |
| [%ExeName%] | Name of the executable. |
| [%Date%] | Start date for collecting information (YYYYMMDD format). |
| [%Time%] | Start time for collecting information (HHMMSS format) |
| [%UserName%] | Name of the current user. |
| [%ComputerName%] | Name of the computer. |
Versions 18 and later[%DataDir%] New in version 18[%DataDir%] [%DataDir%] | Directory of the 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. |
By default: - the extension of the WPF file is ".wpf".
- the name of the WPF file corresponds to: "[%UserDataDir%][%ExeName%]_[%Date%]_[%Time%]".
For example: "C:\Users\Doc\AppData\Roaming\WINDEV applications\MyApp\MyApp_20161023_130812.wpf".
Versions 22 and laterCaution: If you use the dynamic string construction ("Allow "[% %]" in the strings" in the "Compilation" tab of the project description), a compilation error occurs (unknown identifier). In this case, each string must be preceded by '-%'. Example:
ProfilerStart("[%DirUserData%][%exeName%]_[%Date%]_[%Time%]")
becomes
ProfilerStart(-%"[%DirUserData%][%ExeName%]_[%Date%]_[%Time%]")
New in version 22Caution: If you use the dynamic string construction ("Allow "[% %]" in the strings" in the "Compilation" tab of the project description), a compilation error occurs (unknown identifier). In this case, each string must be preceded by '-%'. Example:
ProfilerStart("[%DirUserData%][%exeName%]_[%Date%]_[%Time%]")
becomes
ProfilerStart(-%"[%DirUserData%][%ExeName%]_[%Date%]_[%Time%]")
Caution: If you use the dynamic string construction ("Allow "[% %]" in the strings" in the "Compilation" tab of the project description), a compilation error occurs (unknown identifier). In this case, each string must be preceded by '-%'. Example:
ProfilerStart("[%DirUserData%][%exeName%]_[%Date%]_[%Time%]")
becomes
ProfilerStart(-%"[%DirUserData%][%ExeName%]_[%Date%]_[%Time%]")
Remarks
A WLanguage error occurs if
ProfilerStart is used multiple times in the same process or event (without calling
ProfilerEnd).
Business / UI classification: Neutral code