pub fn exact_properties_where<S, P>(
model: &Model,
object: EntityId,
select_set: S,
select_property: P,
) -> Result<Vec<ExactPropertyEntry>, ExactPropertyError>Expand description
The properties and simple quantities of object in the sets
select_set picks, whose names select_property picks, resolved
exactly.
Both selectors see names only: select_set the Name of each assigned
property set and quantity set, select_property the Name of each
member of a selected set. With |s| s == set and |p| p == name the
result is [x] exactly when exact_property with that set name
answers Present(x), empty exactly when it answers Absent, and the
same error otherwise.
A predefined property set (IfcDoorLiningProperties and the like) holds
its values in attributes of its own entity (#149). Its members are the
attributes it declares below IfcPropertySetDefinition, by schema name
(LiningDepth), and select_set sees its Name, or its entity name
(IfcDoorLiningProperties) when it states none. Because a set without a
Name cannot be ruled out by a name, such a set that select_set rejects
is still refused with ExactPropertyError::UnsupportedDefinition when
select_property picks one of its attributes (#66).
The result is in assignment order: occurrence sets first, then the sets
inherited from the object’s IfcTypeObject, each set’s members in file
order. An inherited property is left out when an occurrence set of the
same name has a selected property of the same name: the occurrence
value overrides it at property level. An empty result is a proven
absence of every selected property. For a queried IfcTypeObject the
result is its own HasPropertySets, each entry with
ExactSource::Type of object (#193), as for
exact_property.
§Errors
Any ExactPropertyError, as for exact_property. Ambiguity is
refused per source: two selected sets of the same name, a property set
and a quantity set included
(ExactPropertyError::DuplicateMatchingSets), and two selected members
of one set with the same name
(ExactPropertyError::DuplicateMatchingProperties).