//////////////////////////////////////////////////////////////////////////////////
// ========================
// PARTsolutions.setup file
// ========================
// With the PARTsolutions.setup file, the adminstrator can define the setup of
// the PARTsolutions/CATIA V5 interface.
// All parameters, which are shown in the SETUP-command of the PARTsolutinos
// toolbar can be aligned via the global PARTsolution.setup file.
// The global PARTsolution.setup file is located in
//   $CADENAS/iface/catia/PARTsolution.setup
// This file describes the differen settings, which are possible.
// If a parameter shouldn't be modified by the CATIA user, the administrator
// can lock any parameter.
// To lock a parameter can be performed by adding the strin ":LOCKED" at the 
// end of the parameter-line.
// Example:
// *PATH_PARTS:P:\pool_directory:LOCKED
// In this case a CATIA user cannot modify the target directory, where the 
// PARTsolutions standard parts are stored.
//////////////////////////////////////////////////////////////////////////////////
//
// Explanations of keywords from PARTsolution.setup configuration file
// 
//////////////////////////////////////////////////////////////////////////////////
// *PATH_PARTS:P:\pool_directory
//	- Path for POOL directory where the CATParts and CATProducts will be saved
//      - The path for the POOL directory can contain variables as well.
//      - Example: *PATH_PARTS:$CADENAS_DATA/catia.pool
//--------------------------------------------------------------------------------
// *CATPART_TEMPLATE:P:\template_directory\Template.CATPart
//	- The name of the CATPart from the disc which will be loaded in CATIA V5
//	when we have to create a CATPart (UUID request). If the CATPART_TEMPLATE
//	is not specified or is empty, a New CATPart will be created in CATIA V5
//--------------------------------------------------------------------------------
// *CATPART_NAME:<$IDNR><_><%NB%><_PSOL_><$L>
//	- Template Name for Name of the CATPart. The variables from MIDENT can be 
//	specified in Windows Format and UNIX format. The syntax allows to specify
//	more MIDENT variables, more strings. If the *CATPART_NAME is not specified 
//	or is empty , the Name of the CATPart will be the Name from Metafile
//--------------------------------------------------------------------------------
//*PROCEDURE_PREFIX:CASPARV5
//	- Procedures Prefix for all Procedures. The name of Procedures will be :
//	the standard string "PSOLUser", the Procedure Prefix, the Procedure Name
//	itself and the extension "cmd". Between the substrings mentioned above,
//	the Underscore_Sign ("_") is used as a separator. The extension is
//	separated by a Point-Sign (".") from the rest of the Procedure File Name.
//	Example : PSOLUser_CASPARV5_QueryPart.cmd . If the *PROCEDURE_PREFIX is
//	not specified or is empty, the Name of the procedure will be :
//	PSOLUser_QueryPart.cmd .
//--------------------------------------------------------------------------------
// *NCSCAN_FILE:C:\Documents and Settings\Administrator\PARTsolution.metanc
//	- File Name where the NCScan info will be saved
//--------------------------------------------------------------------------------
// *CLOSE_PARTS:1
//	- = 1 - Close the created CATParts in CATIA V5
//	  = 0 - Do not Close the created CATParts in CATIA V5
//--------------------------------------------------------------------------------
// *MINIMIZE_PARTS:1
//	- = 1 - Minimize the created CATParts in CATIA V5
//	  = 0 - Do not Minimize the created CATParts in CATIA V5
//--------------------------------------------------------------------------------
//*SKIP_ERRORS:1
//	- = 1 - Ignore Errors during the Update mechanism
//	  = 0 - Do not Ignore Errors during the Update mechanism
//--------------------------------------------------------------------------------
// *CREATE_THREADS:0
//	- = 1 - Create Threads in CATIA V5
//	  = 0 - Do not Create Threads in CATIA V5
//--------------------------------------------------------------------------------
//*CREATE_CONSTRAINTS:1
//	- = 1 - Create Constraints in CATIA V5
//	  = 0 - Do not Create Constraints in CATIA V5
//--------------------------------------------------------------------------------
//*FORCE_CREATION_PARTS:1
//	- Force Creation of CATParts in CATIA V5. if the flag is set to 1, the old
//	CATPart from POOL Directory will be deleted and a New one will be created.
//	If the flag is set to 0,the CATPart will be loaded from the POOL directory
//	if it exists in POOL Directory
//--------------------------------------------------------------------------------
// *CREATE_COMPONENTS:0
//	- Create Components or Product
//	  = 1 - Prodducts will be created in CATIA V5
//	  = 0 - Components will be created in CATIA V5
//--------------------------------------------------------------------------------
// *CREATE_PARAMETERS:1
//	- = 1 - Create Parameters from MIDENT in CATIA V5 for each CATPart
//	- = 0 - Do not Create Parameters from MIDENT in CATIA V5 for each CATPart
//--------------------------------------------------------------------------------
// *CREATE_SOLIDS:0
//	- = 1 - Create History in CATIA V5 for each CATPart
//	- = 0 - Create Solids  in CATIA V5 for each CATPart
//--------------------------------------------------------------------------------
// *DOCUMENT_ENV:0
//	- Environment for POOL Directory
//	  = 1 - Environment for POOL Directory is DLName
//	  = 0 - Environment for POOL Directory is Folder
//--------------------------------------------------------------------------------
// *DEBUG:3
//	- Init the trace mechanism. The messages will be written in the trace file 
//	from home directory (PARTsolution.trace) or to the standard output, 
//	depends which value has DEBUG variable from cfg file :
//	  = 0 - No Debug
//	  = 1 - write in the trace file only the functions
//	  = 3 - write in the trace file all the messages
//	  = 4 - write to the standard output only the functions
//        = 6 - write to the standard output all the messages
//--------------------------------------------------------------------------------
// *PDM:NO
//	- = YES - PDM Connection is active
//	  = NO  - PDM Connection is not active
//--------------------------------------------------------------------------------
// *PART_VIEWER:3D
//	- Type of PARTviewer : 2D or 3D
//--------------------------------------------------------------------------------
// *PART_CONNECT:3D
//	- Type of PARTconnect : 2D or 3D
//--------------------------------------------------------------------------------
// *PART_COLOR_RGB:256,256,256
//	- RGB Color for created CATProducts in CATIA V5. (256,256,256 means
//	No Color)
//--------------------------------------------------------------------------------
// *NCSCAN_COLOR:0,255,255
//	- RGB Color for scanned Holes in NC-SCAN Command . (256,256,256 means
//	No Color)
//--------------------------------------------------------------------------------
// *ADD_PARTSOLUTIONS_IN_MENU:1 - insert PARTsolutions in CATIA Menu	
//	*ADD_PARTSOLUTIONS_IN_MENU:0 - Do not add PARTsolutions in CATIA Main Menu
//	*ADD_PARTSOLUTIONS_IN_MENU:1 - Add PARTsolutions in CATIA Main Menu
//	*ADD_PARTSOLUTIONS_IN_MENU:2 - Add PARTsolutions under the Tools Menu
//////////////////////////////////////////////////////////////////////////////////
*PATH_PARTS:P:\pool_directory
*CATPART_TEMPLATE:
*CATPART_NAME:
*PROCEDURE_PREFIX:
*NCSCAN_FILE:C:\Documents and Settings\Administrator\PARTsolution.metanc
*CLOSE_PARTS:1
*MINIMIZE_PARTS:1
*SKIP_ERRORS:1
*CREATE_THREADS:0
*CREATE_CONSTRAINTS:1
*FORCE_CREATION_PARTS:1
*CREATE_COMPONENTS:0
*CREATE_PARAMETERS:1
*CREATE_SOLIDS:0
*DOCUMENT_ENV:0
*DEBUG:3
*PDM:NO
*PART_VIEWER:3D
*PART_CONNECT:3D
*PART_COLOR_RGB:256,256,256
*NCSCAN_COLOR:0,255,255
*ADD_PARTSOLUTIONS_IN_MENU:1