• CAMAPI
  • API Documentation
Show / Hide Table of Contents
  • Supported programming languages
    • C#
    • Delphi
    • C++
  • Tutorial lessons
    • Lesson 1 - general introduction to the extension ideology using the example of a C# project
    • Lesson 2 - connecting the SDK to a Delphi project using the build system
    • Lesson 3 - connecting the SDK to a C++ project using the build system
    • Lesson 4 - demonstration of methods for unloading an extension during main application is running
    • Lesson 5 - Creating a custom operation
    • Lesson 6 - Creating a C# application to interact with geometry in main application
    • Lesson 7 - Creating a C# application to connect to main application for managing it
  • System extensions
    • Extension.Util.Common.Dll
    • Extension.Util.Common.Exe
  • Debugging of extensions
    • Debugging a .NET extension using Visual Studio Code
    • Debugging a Delphi extension using RAD Studio
    • Debugging a C++ extension using Visual Studio
  • Entry points
    • Utilitiy in main form
    • Executor for utility in main form
    • New item to the operation's context menu
  • Machining Tools Import
    • Preparing the environment
    • Working with the tool library
    • Working with cutting tools
      • Milling Tools
      • Turning Tools
      • Custom Axial Shaped Tools
    • Working with the tool holder
  • API Documentation
  • External applications
    • Connecting in a C# application
    • Connecting in a Delphi application
    • Connecting in a C++ application

Entry point in executing utility

This entry point already contains a list of system extensions:

  • Loading DLL files;
  • Loading EXE files.

The extension expands the list of utilities that can be connected to main application. The fact is that system extensions can only run DLL and EXE files. By adding a new extension of type utility_runner, you can specify it in the launch parameters for extensions of type utility. Thus, SprutCAM calls the utility_runner extension, passing it information about the utility to be launched.

  • Identifier: utility_runner;
  • Used interfaces:
    • IExtensionTypeInfoUtilityRunner.
    • IExtensionUtilityRunner.
  • Available configuration settings:
    • filter_types: filter provided to "Choose file" dialog window, when user chooses utility;
    • visible_in_editor: extension is visible in utility editor, so it can be chosen. This allows for the creation of a unique extension that is suitable for launching only a specific utility and should not be displayed elsewhere to the user.

Examples in our GitVerse account:

  • C# - directory ExtensionUtilityRunnerNet;
  • Delphi - directory ExtensionUtilityRunnerDelphi;
  • C++ - directory ExtensionUtilityRunnerCpp.
In this article
Back to top Generated by DocFX