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


This is where the actual commands for command line arguments are created for the Command Line Argument Development System (CLADS).  The intent of this system is to assist the developer in creating structured software that may be reused in multiple applications and most important is to reduce the development time of custom test and development code that is required for the product development process.  Command Line Arguments are a very useful tool when it comes to adding functionality and flexibility to test and measurement tools if they are initially developed to utilize them.  Many COTS tools are fixed in nature by design.  The IBPD System has a fixed set of internal functions at this time in its first release, however, since we are a dialog based system with room to easily expand we are looking forward to offering many reusable tools for the developer using the CLADS tool.  The objective of the CLA Commands Configuration dialog is to allow the user to create a set of commands to use with a user generated application whether in a Windows or Linux environment.  To organize third party applications that have incorporated a command line mode of operation.  This will allow the recording of these command line commands and easily create an in-line command line argument or a command line recipe based file.

When implementing Command Line Arguments for your program most of the time they are fixed processes and only a few to be controlled.  The CLADS environment allows the user to pick and choose and build on a single application which increases the ROI of software development by continuous reuse.

There are a few steps that have to be incorporated in your actual application to use CLADS.  For convenience we create a header file that incorporated all the commands in a character array for the user to use when parsing the command line.  Included in the header file is a boolean array of flags that is the indexed to the commands.  This allows the user to parser the command line in a loop function and execute internal commands and functions by simply testing a flag. The user has full control over which commands and the sequence of execution of the commands when creating the Command Line Argument File.




The following links located in the main Menu section allow for easier navigation through the many features of the IBPD System.

    Save User CML List - This function allows the user to save the displayed list of CLC files in the listbox.  The user may place this file anywhere the system has access to.  The IBPD System has a set of default directories for each protocol and the default directory for the CLC files is  SaveSets_CLD\CLD_CLC.

    Update User Cmd DB - This is the main function to update the CLC Command File.  IF this function is not performed all editing adding deleting etc. will be lost when the IBPD System Application is terminated.

    Create New User Cmd DB - This function will create a new CLC Command File.  This will create a filled command file with 16 commands for editing.  The current displayed CLC file will not be effected.


2_Active Command List  (CML) File

This is the active CML Command file list previously saved to be viewed or edited.  The user may save this list at any time with the Save User CML List or browse the system directories for a CML file to load.

3_Available CLC Command File  

This is the list of file contained in the CML list file.  Files may be added to the listbox at any time by using the (Add *.clc Files) browse button bottom right of the listbox.  The user may edit the listbox files by removing selected files or completely clearing the listbox.  A single click on a file in the listbox will display the commands in the edit area and start the editing session.  The maximum number of CLC command files per CML list file is 128.  The number of CLC command file in the list is displayed at the lower left of the listbox.

4_Selected CLC Command File

The selected CLC command file is also displayed in the Active CLC Command File field.   The user may also selected a different file that is not in the listbox for editing by using the browse button next to the active CLC file field.  When the file is selected the Creation data and Last modified data along with the Product ID if any is displayed.  The commands and comments are also displayed starting the editing session for the file.

5_Commands File User Comments

This section was added to help identify the command file contents for the user.  It is recommended to add useful identification information for the file for future reference and editing.

6_User Command Creation area

This is the may editing session area. Each command has a comment field explaining that command for future reference.  Each command may be up to 30 characters in length.  It is recommended that the user only use printable characters less than ASCII hex codes less than 0x100 for commands.

The command editing process has the following functions:

      Update Command - This function allows the user to update/replace the selected command in the listbox.

      Add New Command - This function will add the command in the Edit/User Command field to the User Defined CLA Commands Listbox.

      Clear Command Listbox - This function will clear the listbox and the Listbox buffer.

      Delete Selected Command - This function will delete the selected command.  The command is deleted after the Update User Cmd DB button is clicked.

      User Command Comments - This field allows the user to document the use of the command and its functions.  It is a built in users manual for the commands.


7_Save CLC Command File  

This function allows the user to save the current commands in the listbox to the active file or a new CLC file.  The default directory will be displayed however, the user may place the file anywhere the system has access.  When saving and updating a command header file is generated which contains a char array of the commands and a boolean array for each of the commands. Shown below is the layout of the header file. The default header file of commands is always in the SaveSets_CLD\CLD_SYS directory.




8_Help & Status - This is the standard help (this page) and status bars for each dialog.

Copyrightę 1990-2021 BASIL Networks, PLLC. All rights reserved