Frequently Asked Questions
General
Customization
Do I need to create a special customization UI file for ARES Commander or could I use the existing one?
ARES Commander supports a number of customization files like CUI, CUIX, MNU, MNI. So you can use existing cutomization files as needed.
Please see also https://graebert.atlassian.net/wiki/spaces/ACPD/pages/1396834315
Customization via SDK
How to create UI items like menus, toolbars and ribbon using CFx SDK?
There are two samples included in the CFx SDK AddMenuSample and RibbonMenuSample explaining how to create new elements.
How to create Dockable widgets with CFx SDK?
This is explained in the CFx sample DockWidget that can be found in the CFx SDK.
APIs
Where can I find details about the samples without going into sample source code?
Source code can be found only in samples. A review of samples you can find here: https://graebert.atlassian.net/wiki/spaces/ACPD/pages/1469907008
How to load plugins on startup?
Please check this page https://graebert.atlassian.net/wiki/spaces/ACPD/pages/729841899
LISP
How to debug LISP code? Is there any debugger?
Since XtraTools have been included, the debugging of user LISP routines is blocked. The XtraTools contain protect lisp files, this lead to a general protection of LISP and all debugging functions don't prompt anything to the command line window anymore.
The easiest way to debug LISP in ARES Commander, you rename the C:\Program Files\Graebert GmbH\ARES Commander 20XX\XtraTools\ temporarily to e.g.
C:\Program Files\Graebert GmbH\ARES Commander 20XX\_XtraTools\ and restart the ARES again.
Then you get an error message at the startup:
Startup...
Loading main.lsp... OK.
Loading LoadXtraTools.lsp... Error: Folder "XtraTools" not found! Now you can use the tracing command below to debug LISP:
(*settrace* variant [seconds])The *settrace* function sets the mode for tracing of LISP routines and functions.
The integer value variant may be combined (as follows):
Value | Description |
|---|---|
0 | No trace |
1 | Display allocated memory. |
8 | Display function that caused an error. |
16 | Display in case of an error all expressions up to function that caused the error. |
32 | Display any LISP expression evaluated. |
32+64 | Display any LISP expression evaluated (each line of code) needs to be confirmed by pressing any key. |
32+128 | Display any LISP expression evaluated. Halts at the end of a line for a certain time specified by the argument seconds. The default value is 5 seconds. |
Note: As soon as protected LISP files are loaded, the *settrace* function does not work (by intention). When writing your own programs or when porting you should avoid loading protected LISP files.
Related Functions ( )
trace, untrace
Are pre-compiled LISP files (*.fas,*.vlx ) supported?
No, this is at the moment not supported.
How to ship a LISP program without exposing the program code?
We can provide a tool to crypt the LISP files. Please ask partnersupport@graebert.com