Version-Specific Compatibility Changes

This chapter documents changes in Lisp API behaviour, relevant for Lisp application, for specific BricsCAD versions.

since V20 : LEGACYCODESEARCH + SECURELOAD + TRUSTEDPATHS

• BricsCAD V19 added LEGACYCODESEARCH system variable, but it was not effectively used.
  With V20, BricsCAD also added SECURELOAD + TRUSTEDPATHS system variables, and these now become effectively used, and therefore can affect Lisp applications.
  
  Other than under AutoCAD, these system variables are read-only, and can therefore not be changed from within BricsCAD !
  
  The idea behind is, that a "CAD AAdministrator" configures these settings to restrict the default BricsCAD behaviour ... which is likely not always given, and the CAD operators might not have the required knowledge about these Registry settings in question here.
  
  The default values are :
  
  SECURELOAD=0
  LEGACYCODESEARCH=0
  TRUSTEDPATHS=""
  
  As a way to configure these 3 settings, and to simplify application installation, we added version-specific Registry files (in "./Security" sub-folder of LDSP) :
  BcadAdminPolicy-V19.reg
  BcadAdminPolicy-V20.reg
  BcadAdminPolicy-V21.reg
  BcadAdminPolicy-V22.reg
  BcadAdminPolicy-V23.reg
• BcadAdminPolicy-V24.reg
  
  which add these presets to the Registry :
  
  SECURELOAD=0
  LEGACYCODESEARCH=1
  TRUSTEDPATHS=<to be adjusted to the client computer + application paths>
  
  (with SECURELOAD=0 and LEGACYCODESEARCH=1, the TRUSTEDPATHS setting does no longer matter)
  
  These settings then provides the "old" behaviour; when running with administrator account, doubleclick the 2 .reg files to import these settings into Windows' Registry; the paths need to be adjusted, if required
  
  Please also see the folder "./Security" in your LDSP location on disk for more details, and for the provided Registry files "BcadAdminPolicy-Vnn.reg".