PC SOFT

ONLINE HELP
FOR WINDEV, WEBDEV AND WINDEV MOBILE

Home | Sign in | English US

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
Starts "collecting data" for the performance profiler.
Reminder: To start the performance profiler, press: [Shift] + [Windows] + [F10].
Once this function is called, all the processes performed are saved in a WPF file.
This file can be opened:
  • by the performance profiler.
  • in the editor of WINDEV, WEBDEV or WINDEV Mobile ("File .. Open").in the editor of WINDEV, WEBDEV or WINDEV Mobile: on the "Home" pane, in the "General" group, expand "Open" and select "Open".
Windows Mobile Caution: This function has no effect on the Mobile Device (Pocket PC). This function is taken into account in test mode only (project or window "GO") on the development computer.
Versions 18 and later
Universal Windows 10 App This function is now available in Windows Store apps mode.
New in version 18
Universal Windows 10 App This function is now available in Windows Store apps mode.
Universal Windows 10 App This function is now available in Windows Store apps mode.
Versions 21 and later
Universal Windows 10 App This function is now available in Universal Windows 10 App mode.
New in version 21
Universal Windows 10 App This function is now available in Universal Windows 10 App mode.
Universal Windows 10 App This function is now available in Universal Windows 10 App mode.
Example
ProfilerStart("Test_StartProcedure.wpf")
StartProcedure()
ProfilerEnd()
Syntax
ProfilerStart([<Name of WPF File>])
<Name of WPF File>: Optional character string
Name of the WPF file to generate. This file contains the details of the operations performed since the call to ProfilerStart until the call to ProfilerEnd (or until the end of process). Then, this file can be opened and analyzed by the performance profiler.
If this parameter is not specified, the generated file will have a unique identifier and it will be saved in the current directory.If this parameter is not specified, the file will be named <Project Name>.WPF and it will be saved in the current directory.
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 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 current user.
[%ComputerName%]Name of the computer.
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.
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 later
Caution: If you are using the dynamic construction of strings ("Allow "[% %]" in the strings" option in the "Compilation" tab of 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 22
Caution: If you are using the dynamic construction of strings ("Allow "[% %]" in the strings" option in the "Compilation" tab of 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 are using the dynamic construction of strings ("Allow "[% %]" in the strings" option in the "Compilation" tab of 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 several times in the same process (without calling ProfilerEnd).
  • ProfilerStart has no effect in a 64-bit application.
Components
WINDEVWEBDEV - Server codeReports and Queries wd230vm.dll
Windows Mobile wp230vm.dll
Minimum required version
  • Version 9
This page is also available for…
Comments
Click [Add] to post a comment