Main MenuAuto Create HexModify Hex BlockCLA ConfigureCreate ShortcutCLA Commands CfgUser ButtonsDefault DirectoriesRTF Editor


The Command Line Argument File is the core of using the IBPD System in Command Line Mode.  It is also the core of using any EXE file in Command Line Mode that has a CLA command structure. There are many ways of implementing Command Line Modes of operation for general applications as well as specific to requirements for the IBPD System.  Being able to offer a simple way of incorporating Command Line Mode operations into an application is a useful tool for decreasing development time.  One of the major considerations of a command Line mode in applications is the reuse factor.  Tool requirements grow at a rapid rate and Command Line Arguments in a simple single line became very cumbersome to handle and would easily exceed the line length of no return for parsing CLA data.  To address this limitation we use a single file multiple commands methodology that allows the user to implement any number of commands as well as direct the application software for maximum flexibility.  Now that the single file mode is addressed the remaining issue is to effectively manage the various files associated with different applications and projects implementing CLA files.  This is addressed with BASIL Networks Command Line Argument Development System (CLADS).  CLADS for the IBPD System is a self contained system for each protocol and has all its directories organized for that specific protocol.   For general user applications implementing CLA modes the organization is under full user control.

The universal Command Line Argument Development System (CLADS) incorporates three dialogs that link both to the IBPD System as well as other user developed applications that has implemented support for command line mode operations.

  1. Create A Command Line Arguments Command File - This is the dialog used to create Command Line Argument "Commands" to be used in the CLA file application.  Up to 128 separate commands may be created each of a maximum 20 case sensitive characters in length.  This Dialog also creates a headed file that contains a char array of all the commands, a bool array of flags for the user to set when testing to see if the commands are required in the application, a command count which is the number of commands in the CLA Commands (*.CLC) file.
  2. Create A Command Line Argument File - This Dialog shown below is the file that is attached to the IBPD[1][2]xx.EXE file for operation in Command Line Mode.  The IBPD System default CLA commands are already available by default for each protocol.  There is also a user defined CLA set of command the user created previously that may be loaded for CLA file creation.  Of course the user has to write the code inside the application that the user created commands will respond to.  Following this brief introduction will be a detail the use of the Create/Edit  CLA file dialog.
  3. Create a Shortcut for the Command Line Argument File - This is a general shortcut creation utility that has been tuned for Command Line Mode operations and the IBPD System .  It allows the user to select the EXE file and the specific CLA file for the shortcut along with features to select a specific shortcut icon,  incorporate a Command Configuration File, incorporate encryption for security and create folders to place the short in.





Create a Command Line Argument File Main Menu that incorporates the necessary functions to maintain and organize CLA files. The functions are:

    Save CLL List File - Save the list of CLA file in the CLA Listbox.

    Set User Cmds Default - Set the current loaded User Commands file as the default user command file.  This commands file will load automatically along with the IBPD System default commands for the selected protocol when the dialog is called.

    Load CLADS Main Cmds - This allows the user to load a CLADS command set and make changes to any CLA file outside the Protocol area.  It is the same as the CLADS system from the Main IBPD System Startup menu except that when the user sets the default is will always load the IBPD-SYS Commands.  This is to eliminate any confusion in the CLA file development.  What is allows is that this file will address any protocol in the system and allow the setup of each protocol uniquely from the IBPD-SYS startup.  All Command Line Argument files have to be loaded from the MAIN Startup and will automatically assign the proper protocol and CLA file commands within the protocol CLA file called.   When in the CLADS MAIN dialogs the user is completely outside the protocols environment and may create any CLA file and default startup commands.  When creating CLA Commands for user designed API's this is the section that is recommended.   If the user wants to intercept the IBPD-SYS.exe this is where a intermediate CLA file would be implemented.

    Edit User CLA Commands - This is the Create/Edit CLA Command files dialog.

    Create Shortcut [CLADS] - Create a shortcut for the current CLA file within the CLADS environment.  The Shortcut within the CLADS requires the user to select the EXE file to link the CLA file to.  The CLADS shortcut is very similar to the standard system shortcut except is links the CLA files directory and other directories for ease of navigation to accommodate the entire system environment and not limit the user.  The CLADS environment is for user designed API's that accommodate the Command Line Operation.


2_CLL Active List File

This file contains the list of CLA file displayed in the Listbox (3) just below it.

3_Active CLA file List

This is the active list of CLA file available to the user via a single click on the file.  CLA file may be added to the list at any time by using the Add *.cls Files Browse button.  The user is reminded to save the list before closing the IBPD-SYS Startup Menu.  The CLA file List has several maintenance features allowing the user to delete the selected file from the list , Add files to the List and clear the list.  The number of CLA files in the list is displayed at the bottom left of the listbox.

4_CLA FILE Active

This is the current CLA file that is being edited. If this is left blank then when the user click on the New/Update CLA File (14) a system browser will popup with the default CLA directory set in the Default Directories to enter the filename for the CLA file to.  The user may browse for a specific CLA file by using the browse button next to the active CLA file field.  When a CLA file is selected the Creation date, Last Modified date  and the Product ID information is displayed.   The Product ID is allowed to be edited however the creation and modified dated are generated by the system.

5_Load User Commands

This is the universal feature for the CLADS which allows the user to load a custom user CLA commands file created by the Create CLA Commands Dialog.  The user may also select this file as the default user command file to be load at entrance to the dialog.

6_User Defined CLA Commands

This is the drop menu selection of the user commands that are to be placed in a command line of the CLA file.  The user has the option to place this selected command in the argument section or the command section of the CLA command line .  The command and argument of the CLA command is separated by a command separator "=" that may be removed via the checkbox. This allows more flexibility to the CLA command processing. Examples are shown in the CLA listbox .  All command lines are in quotation marks "command line"to accommodate spaces in the commands.

7_IBPD-SYS CLA Commands

These are the default IBPD System CLA commands for the protocol.  Each Protocol has its own set of CLA Commands.  The user may ignore these commands when building a custom user CLA file by checking the Ignore Command Arguments checkbox. This will disable the drop menu for the IBPD System.  In return the user may also disable the Custom User Commands by clearing the check boxes under the User Defined CLA Commands drop menu.

8_Command Arguments

This is the argument side of the CLA Command.   There is a file browser for the file if the command requires a file reference.  Selected commands may be added to this from the CLA Commands drop menu by checking the Add to Cmd checkbox under the CLA Commands drop menu.  The Command Line Argument is comprised of three sections:

      Command - Commands may be stand alone or require an argument, with or without a separator. Such as shown in the CLA listbox.

      Separators  - There are two separators the first is the forward SLASH that is the standard Command line switch identifier that may be used for a single command like "HIDEDIALOGS" which does not require any further identities. , The second is the default "=" character that is used to identify commands that require additional information like parameter data or filenames.  Each separator is controlled by a [x] checkbox above the separators.  A single entity command like "HIDEDIALOGS" in the example may removed the "=" separator by un-checking the box above it.

      Argument - The argument usually is preceded by the "=" character that identified the "Command" if it is not a single entity type command.  The IBPD System uses the naming convention as CMD??? = for commands.
      Example: "CMDI2C=filename.cmd  /user cmds /other commands"


9_Add Cmd Arg To List

This is where the command is added to the CAL file.   Once added the user may also go back and edit the line, remove the line, or clear the entire listbox of CLA commands

10_Replace Command Line

This command allows the user to replace the current command line with the CLA edit fields.

11_CLA Command Lines

This is the line by line contents of the CLA file being created.

12_Remove Selected Command

This allows the user to remove a selected command line from the list of commands. The command is not removed until the New/Update CLA File (14) is executed.

13_Move Command Line Order

The Up/Down arrows allow the user to set the command sequence order in the CLA file.  The IBPD-SYS executes these commands in sequential order from top to bottom.

14_Clear CLA Command List

This will clear the CLA list and reset the CLA command list buffer to NULL.

15_New/Update CLA File

This command allows the user to create or update the CLA file with the current Dialog Data.

16_CLA File User Comments

This is a User comment area for information about the file that the user controls.  It is not part of the command line argument commands.


This is the common dialog status field for the last function executed on the dialog.

18_Help - This page



The Command Line Argument List File (Filename.CLL) is the organizational part of the CLADS, that allows the user to save multiple CLA file anywhere the user system has access to.  This allows easy tracking of the files and editing of the files for reuse in other applications.  Each *.CLL file may contain up to 128 CLA files.  The block diagram below shows how this interacts with the Create/Edit CLA File Dialog.


The File1.cla  is the actual command Line argument file that is attached to the EXE file for command line mode operation.  The file is user created in the above dialog.  The basic structure of the Command Line Argument File is to make it easier to parser the commands by breaking the command line into its components then storing them in a structure per command line allowing key character identifiers to separate various types of commands such as file, parameter, function etc. allowing users the flexibility required to execute a multiple number of commands.  The last field in the structure still puts it all together and is the complete Command Line used for displaying the commands as they are executed in the application.  The header file with all the structures for the Command Line Mode are included with the installation.

typedef  struct  _CLA_COMMANDS_FILE








//- Number of Files in list




//- User Comments for CLA File




//- File Product ID




//- Delete Flag




//- Equal Sign in command




//- Files Command




//- Files Command Arg




//- Complete Command Line argument








Copyright 1990-2018 BASIL Networks, PLLC. All rights reserved