ONLINE HELP
 WINDEVWEBDEV AND WINDEV MOBILE

Help / Developing an application or website / Component / External component
  • Overview
  • How to?
  • Debugging a component
  • Multi-product component for WEBDEV
  • Limitation
WINDEV
WindowsLinuxUniversal Windows 10 AppJavaReports and QueriesUser code (UMC)
WEBDEV
WindowsLinuxPHPWEBDEV - Browser code
WINDEV Mobile
AndroidAndroid Widget iPhone/iPadIOS WidgetApple WatchMac CatalystUniversal Windows 10 App
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?

Debugging a component

To debug a component:
  1. Open the project corresponding to the external component.
  2. In the "Project explorer" pane, select and enable the project configuration corresponding to the external component ("Enable this configuration" in the context menu).
  3. To configure the debug mode of the current component, go to the "Project" tab, "Test mode" group, expand "Test mode" and select "Configure test mode".
    Debugging options of a component in WINDEV
  4. Select the desired option. You can:
    • WINDEVAndroidiPhone/iPad Run the test of the component from the project (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.
    • WINDEVWEBDEV - Server code 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.
      Remark: the project that calls the component must have been opened at least once and recompiled from the current computer.
    • WINDEV Run the test of the component from an executable (WINDEV only):
      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.
  5. In your project, include the breakpoints required to debug your component.
  6. When the project test is started, the selected debug configuration will be used. When a breakpoint (or the STOP keyword) is encountered, the debugger will start automatically.

Multi-product component for WEBDEV

To debug the WEBDEV part of a cross-platform component (for example, a component for WINDEV and WEBDEV), you must generate the component that has the same name as the actual cross-platform component generated from WINDEV.

Limitation

You cannot debug components that use the runtime context of the "client" project (i.e. the project that uses the component).
Reminder: You can choose whether or not to use the runtime context of the "client" project in the component options:
  1. Open the description window of the "Component" configuration:
    • If the component configuration is currently open: on the "Project" tab, in the "Project configuration" group, click "Current configuration".
    • In the "Project explorer" pane, open the context menu of the component configuration and select "Description".
  2. In the window that appears, in the "General" tab, click "Component options".
  3. In the "Access rights" tab, choose how the component accesses the data of the client project. To use the context of the client project, select "The component will access the data files, windows, pages and reports of the client project.".
  4. Validate.
Minimum version required
  • Version 10
This page is also available for…
Comments
Click [Add] to post a comment

Last update: 10/27/2022

Send a report | Local help