Hello NX Specialist,
I'm currently extending our NX Check-Mate environment with a few customized checkers. Up to now I have used an external Text - Editor like Notepad++ to create the related .dfa files. Now I want to switch over to the NX Inetractive Class Editor (ICE) application, which can be launched directly from the NX Knowledge Fusion toolbar. In front of my NX session i have declared the following environment variables:
UGII_KF_USER_CLASS_DIR \\server with write access\ugsshare_pl1\GEAcustom\NX75\winXX\ugii\Common\dfa
UGII_KF_DOC_DIR \\server with write access\ugsshare_pl1\GEAcustom\NX75\winXX\ugii\Common\dfa_doc
UGII_KF_CLASS_DIR C:\ugs\nx75\ugii\dfa
UGCHECKMATE_USER_DIR \\server with write access\ugsshare_pl1\GEAcustom\NX75\winXX\ugii\Common\ugcheckmate
Inside the ICE I can now brows through my custom checkers if I click on the system branch in the class tree dialog. But if I open a specific custom checker file via that dialog the file is locked and I'm not able to edit it even if I have write access to the original windows directroy.
What are the mechanism for locking a .dfa file for edition? Are there any naming conventions, which preventing the ICE to open the file in edit mode?
Regards
Matthias
I'm currently extending our NX Check-Mate environment with a few customized checkers. Up to now I have used an external Text - Editor like Notepad++ to create the related .dfa files. Now I want to switch over to the NX Inetractive Class Editor (ICE) application, which can be launched directly from the NX Knowledge Fusion toolbar. In front of my NX session i have declared the following environment variables:
UGII_KF_USER_CLASS_DIR \\server with write access\ugsshare_pl1\GEAcustom\NX75\winXX\ugii\Common\dfa
UGII_KF_DOC_DIR \\server with write access\ugsshare_pl1\GEAcustom\NX75\winXX\ugii\Common\dfa_doc
UGII_KF_CLASS_DIR C:\ugs\nx75\ugii\dfa
UGCHECKMATE_USER_DIR \\server with write access\ugsshare_pl1\GEAcustom\NX75\winXX\ugii\Common\ugcheckmate
Inside the ICE I can now brows through my custom checkers if I click on the system branch in the class tree dialog. But if I open a specific custom checker file via that dialog the file is locked and I'm not able to edit it even if I have write access to the original windows directroy.
What are the mechanism for locking a .dfa file for edition? Are there any naming conventions, which preventing the ICE to open the file in edit mode?
Regards
Matthias
