WebKitX relies on CEF sub-processes named CEF3XClient.exe and instantiates several of them during its operation. Hover to view descriptions of existing attributes.

Use IntelliSense to learn about possible attributes. Also define a preLaunchTask that is explained further below. If you need to debug two or more controls we recommend adding several configurations with different debug port numbers as illustrated below. We recommend defining breakOnLoad to false and the port parameter must be the same port number used in previous step. You must create a new launch.json file and define the runtimeExecutable parameter to point to your applications executable. Since WebKitX is a Chromium wrapper, you must install Debugger for Chrome plugin in your Visual Studio Code. The process is illustrated in Visual Basic 6 but it is the same for any other programming language. If you are developing a similar application, you must assign different port to each control as well as different cache path. In the example below we use two (2) WebKitX controls and we enable remote debugging on both controls. Configure your ApplicationĬonfigure your WebKitX executable for remote debugging by handling the OnCreate event and defining remote_debugging_port and cache_path. Features include support for debugging, syntax highlighting, intelligent code completion, snippets, code refactoring, and embedded Git. Visual Studio Code is a free source-code editor made by Microsoft for Windows, Linux and macOS. Even though WebKitX has built-in Chromium Developer Tools accessible through ShowDevTools method, there is a far more efficient way to debug your HTML5 / JavaScript applications by using Visual Studio Code.

Visual studio code debugger c