Class TIfcCartesianPointList_Spec
Unit
Declaration
type TIfcCartesianPointList_Spec = class abstract(TIfcGeometricRepresentationItem)
Description
Abstract supertype of list of points.
Note: The name in Pascal has suffix "Spec" (as for "specification class") to differentiate from TIfcCartesianPointList which is a list of TIfcCartesianPoint using TObjectList<TIfcCartesianPoint>. We need both list types. Luckily, we can name this class however we want, as it's abstract and thus not used in IFC files.
Spec: https://standards.buildingsmart.org/IFC/RELEASE/IFC4_3/HTML/lexical/IfcCartesianPointList.htm
Source: scene/load/ifc/castleifc_ifc_standard_types.inc (line 559).
Hierarchy
- TObject
- TPersistent
- TComponent
- TIfcPersistent
- TIfcRepresentationItem
- TIfcGeometricRepresentationItem
- TIfcCartesianPointList_Spec
Overview
Methods
| Protected | function WantsGlobalId: Boolean; virtual; |
| Protected | class function IfcClassName: String; virtual; |
| Public | function BuildNode(const Mapping: TCastleIfcMapping; const ParentProduct: TIfcProduct; const LitAppearance, UnlitAppearance: TAppearanceNode): TAbstractChildNode; virtual; |
| Public | procedure UpdateCoordinate(const Coord: TCoordinateNode); virtual; abstract; |
Properties
| Published | property GlobalId: String read FGlobalId write FGlobalId; |
| Published | property LayerAssignment: TIfcPresentationLayerAssignment read FLayerAssignment write FLayerAssignment; |
| Published | property StyledByItem: TIfcStyledItem read FStyledByItem write FStyledByItem; |
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. | |
| Public | function BuildNode(const Mapping: TCastleIfcMapping; const ParentProduct: TIfcProduct; const LitAppearance, UnlitAppearance: TAppearanceNode): TAbstractChildNode; virtual; |
|
Build a node to display this using Castle Game Engine. Returns
Parameters
Source: scene/load/ifc/castleifc_ifc_standard_types.inc (line 368). | |
| Public | procedure UpdateCoordinate(const Coord: TCoordinateNode); virtual; abstract; |
|
This item has no description. Source: scene/load/ifc/castleifc_ifc_standard_types.inc (line 561). | |
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 | |
| Published | property LayerAssignment: TIfcPresentationLayerAssignment read FLayerAssignment write FLayerAssignment; |
|
Assignment of the representation item to a single or multiple layer(s). Source: scene/load/ifc/castleifc_ifc_standard_types.inc (line 374). | |
| Published | property StyledByItem: TIfcStyledItem read FStyledByItem write FStyledByItem; |
|
Reference to the IfcStyledItem that provides presentation information to the representation, e.g. a curve style, including colour and thickness to a geometric curve. Source: scene/load/ifc/castleifc_ifc_standard_types.inc (line 380). | |
Generated by PasDoc 0.17.0.snapshot.