Additions & Changes with V.0.9.9 (BricsCAD V17)

• BricsCAD V17 has extended the Automatic and DemandLoad Loading Feature for Lisp and VBA files - before, this smart functionality was only available for BRX/NET modules (matching the AutoCAD + ARX logic);
  this feature has been extended to provide same functionality for Lisp and VBA application modules, which can now be loaded automatically during BricsCAD startup (resp. for each opened drawing, for Lisp), or alternatively loaded when application-defined commands are entered by user (or other application code).
  
  Additionally, this extended feature (not present in AutoCAD) provides application developers more opportunities to register / install their application(s) with BricsCAD, and ensure the application code is automatically (or on-command) loaded by BricsCAD.
  
  For more details, see topic Automatic LISP + VBA Loading.
  
  
• For MCAD's SheetMetal functionality, the new SheetMetal LISP-API (was introduced with V16.2) has been improved and extended.
  
  
• extended Lisp's capabilities to read + write UTF / Unicode text files (UTF-8, UTF-16LE, UNICODE [=UTF-16LE]), adding a ",ccs=<translation>" to (open <filename> "r|w,ccs=...")
  functions which respects the file mode are : (read-line), (write-line), (princ), (print), (prin1)
  (see topic Extended AutoLISP functions for "read + write text files")
  
  
• extended standard AutoLISP functions (getcfg "Name") and (setcfg "Name" "Value") to read and write any Settings value, as shown in BricsCAD's Settings dialog - covering all system variables, registry variables, and session-only settings and variables;
  output is always a string, and input parameter value is also a string always
  (see topic Extended AutoLISP functions for "setcfg + getcfg")

• added missing standard AutoLISP functions :
  
  

• added missing standard COM methods for BricsCAD LISP :
  
  

• added new VLE functions :
  
  

• added new BricsCAD-specific Lisp functions :
  
  

• added more Fast-COM implementations for Properties + Methods :
  
  

• most  Lisp COM functions (vlax-get/put-property ...), (vla-get-xxx ...), (vla-put-xxx ...) now also accept "plain" Lisp data types as input, not only COM-specific Variants/SafeArrays, to improve compatibility with AutoCAD AutoLISP

• several corrections + additions for ExpressTools API functions