Class TIfcDraughtingPreDefinedColour
Unit
Declaration
type TIfcDraughtingPreDefinedColour = class(TIfcPreDefinedColour)
Description
IFC class IfcDraughtingPreDefinedColour.
Source: scene/load/ifc/castleifc_ifc_standard_types_autogenerated.inc (line 3166).
Hierarchy
- TObject
- TPersistent
- TComponent
- TIfcPersistent
- TIfcPresentationItem
- TIfcPreDefinedItem
- TIfcPreDefinedColour
- TIfcDraughtingPreDefinedColour
Overview
Methods
| Protected | function WantsGlobalId: Boolean; virtual; |
| Protected | class function IfcClassName: String; virtual; |
Properties
| Published | property GlobalId: String read FGlobalId write FGlobalId; |
Description
Methods
| Protected | function WantsGlobalId: Boolean; virtual; |
|
If Strictly following the spec, this should be only defined for TIfcRoot, because only IfcRoot has GlobalId. In reality, we need GlobalId at TIfcPersistent to load some files, and we sometimes need | |
| Protected | class function IfcClassName: String; virtual; |
|
Name for the IFC standard, used in IFC files. By default, this is just ClassName with prefix 'T' removed. | |
Properties
| Published | property GlobalId: String read FGlobalId write FGlobalId; |
|
Globally unique identifier for the object instance. Note: Not declared as TGUID, because TGUID cannot be published, but also we don't really need it: for our purposes, this identifier is just an arbitrary string. Note: IFC 4.3 specification puts this only at IfcRoot, not at every IFC class. But testcase https://github.com/buildingsmart-community/Community-Sample-Test-Files/blob/main/IFC%204.0.2.1%20(IFC%204)/ISO%20Spec%20archive/wall-with-opening-and-window.json (from IFC 4.0) shows this can be present at any IFC class, in particular TIfcGeometricRepresentationContext. In fact, TIfcGeometricRepresentationContext needs to have IFC JSON documentation says this, which seems to (unfortunately it is not unambiguous enough...) allow this at any IFC class: "Whereas the | |
Generated by PasDoc 0.17.0.snapshot.