PC SOFT

ONLINE HELP
FOR WINDEV, WEBDEV AND WINDEV MOBILE

  • Overview
  • How to proceed?
  • Debugging a component
  • Multi-product component
  • Limitation
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
You have developed an external component and you want to debug it? The user of an external component sends an executable indicating that your external component does not operate? You are using your external component in another project and you want to debug it?
Nothing's easier. WINDEV, WEBDEV and WINDEV Mobile allow you to easily debug your external components.
How to proceed?

Debugging a component

To debug a component:
  1. Open the project corresponding to the external component.
  2. Select the project configuration corresponding to the external component.
  3. In this project configuration, the current element must be the WDK file corresponding to the component. To do so, open the manager of project configuration ("Project .. Project configurations .. Manage the configurations") and modify the current element if necessary. Then, close the manager of project configuration. In this project configuration, the current element must be the WDK file corresponding to the component. To do so, open the manager of project configuration: on the "Project" pane, in the "Project configuration" group, click "Manage the configurations" and modify the current element if necessary. Then, close the manager of project configuration.
  4. To configure the debug mode of the current component, select "Workshop .. External component .. Test mode of components".To configure the debug mode of the current component, on the "Project" pane, in the "Test mode" group, expand "Test mode" and select "Configure the test mode".
  5. Select the requested option. You can:
    • Run the test of the component from the project (by default):
      This option is used to run the test of the component from its own project. You have the ability to specify a command line.
    • Run the test of the component by running another project:
      This option is used to run the test of the component by first running the project that calls the component. The component must have been included in the project. This option is useful if you have created a component and if you want to use it in another project.
      To use this option, you must specify the name and the full path of the project where the component was included. You also have the ability to specify a command line to start the project.
      Note: the project that calls the component must have been opened at least once and recompiled from the current computer.
    • Run the test of the component from an executable:
      This option is used to run the test of the component by first running an executable. The component must have been included in this executable. This option is useful if one of your customers has a problem with a component and if he only sends you the executable for example.
      To use this option, you must specify the name and full path of executable in which the component was included. You can also specify a command line to start the executable.
    • WEBDEV - Server code Run the test of the component from a site (WEBDEV only):
      This option is used to run the test of the component by starting a WEBDEV site. This site must be found in the development computer and it must have been started at least once (to be referenced in the WEBDEV development administrator). The component must have been included in this site.
      To use this option, you must specify the name of the site. This name corresponds to the name that appears in the WEBDEV administrator. You also have the ability to specify a command line to start the site.
  6. In your project, include the breakpoints required to debug your component.
  7. When running the test of the project, the selected debug configuration will be used. The debugger will be automatically run when a breakpoint (or the STOP keyword) is found.

Multi-product component

To debug the WEBDEV part of a multi-product component, you must generate a "fake" component from WEBDEV with the same name as the real multi-product component generated from WINDEV.

Limitation

No debugging is available for the components that share the runtime context of the project.
Reminder: The share of the runtime context is configured in the description of the component:
  • Select "Workshop .. External component .. List of components generated from this project".
  • Select the relevant component.
  • Click the "Options" button.
  • Select "The component will access the data files, windows, reports, ... of the client project".
Reminder: The share of the runtime context is configured in the description of the component:
  • On the "Project" pane, in the "Project" group, expand "List of elements" and select "List of generated components".
  • Select the relevant component.
  • Click the "Options" button.
  • Select "The component will access the data files, windows, reports, ... of the client project".
Minimum required version
  • Version 10
This page is also available for…
Comments
Click [Add] to post a comment