@procore/bim-webviewer-sdk 5.2.0-rc.1 → 5.3.0-rc0
This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
- package/CHANGELOG.md +25 -0
- package/dist/Procore.Bim.Webviewer.js +1 -1
- package/package.json +1 -1
package/CHANGELOG.md
CHANGED
|
@@ -5,6 +5,31 @@ All notable changes to this project will be documented in this file.
|
|
|
5
5
|
The format is based on [Keep a Changelog](https://keepachangelog.com/en/1.0.0/),
|
|
6
6
|
and this project adheres to [Semantic Versioning](https://semver.org/spec/v2.0.0.html)
|
|
7
7
|
|
|
8
|
+
## [Unreleased]
|
|
9
|
+
|
|
10
|
+
## [5.3.0] - 2022-09-19
|
|
11
|
+
|
|
12
|
+
### Changed
|
|
13
|
+
|
|
14
|
+
- [BREAKING CHANGE] Methods in the model namespace have been renamed to better match what they return and what type of parameters they expect. Primarily this has meant clarifying that the particular type of "id" that these methods expect is a "meshnode index". To be clear: there is no behavior change of these methods, they have only been renamed and will continue to work as they have been.
|
|
15
|
+
- Renamed methods:
|
|
16
|
+
- model.getObject => model.getMeshnode
|
|
17
|
+
- model.getObjectFromPropertyId => model.getMeshnodeFromObjectId
|
|
18
|
+
- model.getHiddenGeoIds => model.getHiddenMeshnodeIndices
|
|
19
|
+
- model.addHiddenGeoIds => model.addHiddenMeshnodeIndices
|
|
20
|
+
- model.hasHiddenGeoIds => model.hasHiddenMeshnodeIndices
|
|
21
|
+
- model.clearHiddenIds => model.clearHiddenMeshnodeIndices
|
|
22
|
+
- model.getSelectedGeoIds => model.getSelectedMeshnodeIndices
|
|
23
|
+
- model.addSelectedIds => model.addSelectedMeshnodeIndices
|
|
24
|
+
- model.hasSelectedIds => model.hasSelectedMeshnodeIndices
|
|
25
|
+
- model.clearSelectedIds => model.clearSelectedMeshnodeIndices
|
|
26
|
+
- model.setObjectColor => model.setMeshnodeColor
|
|
27
|
+
- Deleted methods:
|
|
28
|
+
- model.getModelItemBoundary(meshnodeIndex). You can instead call model.getMeshnode(meshnodeIndex).bbox
|
|
29
|
+
- Reasoning: These methods referred to object, objectId, propertyId, geoId, and simply id. There are two issues with this: (1) There are multiple names for the same thing. As it currently stands, most things are actually referring to a meshnodeIndex or a meshnode. (2) What we referred to as an object, e.g. what’s returned from the old getObject, is not what the BIM Rest API refers to as an object. We believe these method renames will bring more clarity to how to use them in your own code.
|
|
30
|
+
- Future plans: We intend to release another set of methods that operate on objects (of which meshnodes are a subtype) and object ids rather than directly on meshnodes and meshnode indices. These object methods will be released in a non-breaking way and the meshnode methods will continue to work. However, the meshnode methods may eventually be deprecated and become considered internal and possibly not adhering to semver.
|
|
31
|
+
- Make camera movement with Fly Tool independent of framerate. Less “getting bogged down” when in a model and less “blasting off” when moving outside of it.
|
|
32
|
+
|
|
8
33
|
## [5.2.0] - 2022-09-06
|
|
9
34
|
|
|
10
35
|
### Fixed
|