Dialog Box

• Open dialog box, select macro of interest, and edit it in the dialog box.
• Submit a run request.
• If errors are reported, display them one at a time, correct each in turn.
• Resubmit the run request.

Pro Build

• Configure project for .MAC files (only needed once)
  • Tools tab
    • Build
      !MacroMakeErrorFile
      No command shell - checked
      Save current file - checked
    • Build (Debug) - blank
    • Rebuild
      !MacroMakeErrorFile
      No command shell - checked
      Save current file - checked
    • Rebuild (Debug) - blank
    • Debug - blank
    • Execute - blank
    • Build Tags - blank
  • Errors tab (if you don't use another error parsers for non-.MAC files in the project)
    • Error Filename - proj.err
    • Error Parser 1 - _APIMacroInfo
    • Error Parser 2 - blank
    • Error Parser 3 - blank
  • Error tab (if you use another error parser for non-.MAC files in the project project)
    • Error Filename - proj.err
    • Error Parser 1 - another error parser
    • Error Parser 2 - _APIMacroInfo
    • Error Parser 3 - blank
• Operation
  • Load "cwright.mac" into a CodeWright buffer and edit the buffer in the traditional manner.
  • Submit a build or rebuild request.
  • If compile errors exist they all appear in the CodeWright Output window Build pane.
    • Double-click on an error and the cursor will move in the edit window to the statement in error.
  • Correct the error(s).
  • Resubmit the build or rebuild request.

Entire Library

• Load "cwright.mac" into a CodeWright buffer and edit the buffer in the traditional manner.
• Save "cwright.mac" to disk.
• Submit a MacroMakeErrorFile request.
• Refresh the Output window Build pane to determine if compile errors exist.
• If compile errors exist they all appear in the CodeWright Output window Build pane.
  • If you have the API Error Filter (_Apiarist) enabled for the current project you can double-click on an error and the cursor will move in the edit window to the statement in error.
• Correct the error(s).
• Save "cwright.mac" to disk.
• Resubmit the MacroMakeErrorFile request.

tlaMDE

• Load the file containing the macro(s) of interest into a CodeWright buffer and edit the buffer in the traditional manner.
• Submit an execute request for the macro(s) of interest.
• If compile errors exist they all appear in the CodeWright Output window Build pane.
  • If you have the API Error Filter (_Apiarist) enabled for the current project you can double-click on an error and the cursor will move in the edit window to the statement in error.
• Correct the error(s).
• Resubmit the execute request.

CodeWright for .NET Development Options

Dialog Box

• Not supported in CodeWright for .NET.

Pro Build

• Not supported in CodeWright for .NET.

Entire Library

• Load "cwvsnet.mac" into a CodeWright for .NET buffer and edit the buffer in the traditional manner.
• Save "cwvsnet.mac" to disk.
• Submit a MacroMakeErrorFile request.
• Load a buffer with the file ...
  c:\dir\Microsoft VisualStudio.NET\Common7\IDE\proj.err
  ... where c:\dir is the location of your VisualStudoo.NET system.
• If compile errors exist they all appear in the error buffer.
  • Select all the error in the error buffer.
  • Issue Ctl-C (copy to the Clipboard).
  • Close the error buffer.
• Display the Output window, ClipView pane, Clipboard showing all the errors.
• Correct the error(s).
• Save "cwvsnet.mac" to disk.
• Resubmit the MacroMakeErrorFile request.

tlaMDE

• Load the file containing the macro(s) of interest into a CodeWright for .NET buffer and edit the buffer in the traditional manner.
• Submit an execute request for the macro(s) of interest.
  • If compile errors exist they all appear in the CodeWright Output window ClipView pane Clipboard.
• Correct the error(s).
• Resubmit the execute request.

Option Recommendation Matrix

tlaMDE will be beneficial to almost anyone working with API macros. Our recommendation for the "best solution" for you is ...

Purchase