| 일 | 월 | 화 | 수 | 목 | 금 | 토 |
|---|---|---|---|---|---|---|
| 1 | 2 | 3 | 4 | 5 | 6 | |
| 7 | 8 | 9 | 10 | 11 | 12 | 13 |
| 14 | 15 | 16 | 17 | 18 | 19 | 20 |
| 21 | 22 | 23 | 24 | 25 | 26 | 27 |
| 28 | 29 | 30 |
Tags
- ObjectSpecsModeler
- Feature Initiate
- 여러파일 FTP로 받기
- 푸치니
- 화일갯수
- 팝
- MP3
- 날짜관련함수
- Uno21.com
- Catalog
- Catia V5
- 파가니니
- Mechanical Feature
- CATIA
- 변환
- 카티아
- Mechanical feature inheritance
- XDMCP
- Feature
- CAA
- 가요
- Excel
- CAA Doc
- 클래식
- 모르면 병
- FTP 명령어
- Context
- IdentityCard
- 교향곡
- freeware
Archives
- Today
- Total
data for us
User Catalog management 본문
User Catalog management
* Catalog files are dedicated to store feature definition (StartUp)
* A catalog may store any number of StartUps
* Once created a catalog should never be deleted
- In fact a catalog has a unique ID which is used to identify the
StartUps it contains. When a catalog is deleted and recreated,
existing instances of every feature will still reference the old
catalog ID.
- instead upgrade it
* Catalog implement the interface CATICatalog
* use this interface to add startups to a caltalog
* DS provides the several method to manage user catalogs, they are
defined in CATCatalogFactoryServices.h
- CreateCatalog
- UpgradeCatalog
- AccessCatalog
- SaveCatalog
* To protect the use of your catalog, those methods takes a client ID
* To ensure ascendant data compatibility between subsequent release
of your application you must follow some rules
- On StartUp
. You can add or delete attributes
. You can change an attribute's initial value
. You cannot modify an attibute's type or quality
. You can change its name
- On a catalog
. You can add new StartUps, as long as theri names are unique in
all catalogs.
. You cannot delte a StartUp or move it to another catalog
. You cannot change the name of catalog or recreate it
* Catalog files are dedicated to store feature definition (StartUp)
* A catalog may store any number of StartUps
* Once created a catalog should never be deleted
- In fact a catalog has a unique ID which is used to identify the
StartUps it contains. When a catalog is deleted and recreated,
existing instances of every feature will still reference the old
catalog ID.
- instead upgrade it
* Catalog implement the interface CATICatalog
* use this interface to add startups to a caltalog
* DS provides the several method to manage user catalogs, they are
defined in CATCatalogFactoryServices.h
- CreateCatalog
- UpgradeCatalog
- AccessCatalog
- SaveCatalog
* To protect the use of your catalog, those methods takes a client ID
* To ensure ascendant data compatibility between subsequent release
of your application you must follow some rules
- On StartUp
. You can add or delete attributes
. You can change an attribute's initial value
. You cannot modify an attibute's type or quality
. You can change its name
- On a catalog
. You can add new StartUps, as long as theri names are unique in
all catalogs.
. You cannot delte a StartUp or move it to another catalog
. You cannot change the name of catalog or recreate it