@procore/bim-webviewer-sdk 11.1.0 → 12.0.0-BIM-3837.0
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 +41 -0
- package/dist/Procore.Bim.Webviewer.js +1 -1
- package/package.json +1 -1
package/CHANGELOG.md
CHANGED
|
@@ -5,6 +5,39 @@ 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
|
+
## [12.0.0] - 2024-02-20
|
|
9
|
+
|
|
10
|
+
### Changed
|
|
11
|
+
|
|
12
|
+
- [Breaking Change] Several methods that returned model objects with a `bbox` property were in local coordinates. The following methods now return the `bbox` property in world coordinates:
|
|
13
|
+
- `model.getObject`
|
|
14
|
+
- `model.getObjects`
|
|
15
|
+
- `model.getRootObject`
|
|
16
|
+
- [Breaking Change] Several events that returned model objects as part of the event payload had `bbox` properties in local coordinates. The following events now the `bbox` property in world coordinates:
|
|
17
|
+
- 'objectSingleClick`
|
|
18
|
+
- `objectSelect`
|
|
19
|
+
- Changes the Loading Screen by switching to a single progress bar that goes from 0 to 100 once, before opening the fully rendered modeled.
|
|
20
|
+
- `model.configureSectionBoxDisplay` now takes a new new option `overrideSectionBoxSetup` that determines whether or not `model.toggleSectionBoxDisplay` will apply or clear the section box applied to the model. This configuration affects all following calls to `model.toggleSectionBoxDisplay`.
|
|
21
|
+
- `model.configureSectionBoxDisplay({ overrideSectionBoxSetup: true })` will prevent `model.toggleSectionBoxDisplay` from applying or clearing the section box, requiring callers to set the section box themselves.
|
|
22
|
+
- `model.configureSectionBoxDisplay({ overrideSectionBoxSetup: false })` will allow `model.toggleSectionBoxDisplay` to apply or clear the section box. This is the default behavior.
|
|
23
|
+
- `model.toggleSectionBoxDisplay` now conditionally applies or clears the section box based on an `overrideSectionBoxSetup` value.
|
|
24
|
+
- `overrideSectionBoxSetup` can be set globally from `model.configureSectionBoxDisplay`
|
|
25
|
+
- `overrideSectionBoxSetup` can be applied to a specific call: `model.toggleSectionBoxDisplay(true, { overrideSectionBoxSetup: true })`. This will take precedence over any values set by `model.configureSectionBoxDisplay`.
|
|
26
|
+
- [Breaking Change] The default behavior of `model.toggleSectionBoxDisplay` has changed to set up the section box following the same logic as the "Section Box" toolbar button. The previous default behavior would throw an error when called without a section box set.
|
|
27
|
+
- To get the old behavior of `model.toggleSectionBoxDisplay(true/false)` you must now call `model.toggleSectionBoxDisplay(true/false, { overrideSectionBoxSetup: true })`
|
|
28
|
+
|
|
29
|
+
### Fixed
|
|
30
|
+
|
|
31
|
+
- Fix issue where camera would jump around dramatically when it was looking straight up or down and was moved.
|
|
32
|
+
- Fix issue where resizes of the Web Viewer's `parentElement` (passed in as an option to `Webviewer` constructor) that were not the result of a `window` resize would not cause the Web Viewer to be resized.
|
|
33
|
+
- Fix issue where the Sectioning Coachmark would show up if the Home Viewpoint did not have sections but a default section was applied from the `min_boundary` and `max_boundary` options.
|
|
34
|
+
|
|
35
|
+
### Added
|
|
36
|
+
|
|
37
|
+
- Added `model.getNumObjectsHidden` which returns number of hidden objects.
|
|
38
|
+
- Added new SDK method `model.resetSectionBox`, which sets section box to either the user-defined bounding box (passed in through `Webviewer` options), the refined global bounding box (the global bounding box with "space junk" removed), or the global bounding box in that order of precedence based on what's available.
|
|
39
|
+
- Added new SDK method `model.getSectionBoxDisplay`, which returns meta data about the section box display (i.e. the orange box widget for adjusting the section box). It includes the current `enabled` status, the `bbox`, and the `configuration` of the current section box display.
|
|
40
|
+
|
|
8
41
|
## [11.1.0] - 2024-02-05
|
|
9
42
|
|
|
10
43
|
### Added
|
|
@@ -15,6 +48,14 @@ and this project adheres to [Semantic Versioning](https://semver.org/spec/v2.0.0
|
|
|
15
48
|
- `gui.setToolbarHidden(true)` will hide the toolbar if the toolbar is not already hidden.
|
|
16
49
|
- `gui.setToolbarHidden(false)` will show the toolbar if the toolbar is not already shown.
|
|
17
50
|
- `gui.setToolbarHidden` will throw an error if the bottom toolbar is not enabled.
|
|
51
|
+
|
|
52
|
+
### Changed
|
|
53
|
+
|
|
54
|
+
- [Internal] `npm run benchmark:branchCompare` now detects release vs feature mode from current branch and has new messaging describing this. Also remove the now obsolete `npm run benchmark:branchCompare:release`.
|
|
55
|
+
- Changes the Loading screen:
|
|
56
|
+
- Relies on messages posted from the new Bootstrapper class;
|
|
57
|
+
- Goes from 0 to 100 in a single run, instead of resetting itself multiple times for various phases of the initialization process;
|
|
58
|
+
- This new behavior applies to both standard and large models.
|
|
18
59
|
- Added new SDK method `gui.setHotkeysEnabled` that allows you to enable or disable hotkeys.
|
|
19
60
|
- `gui.setHotkeysEnabled(true)` will enable hotkeys if they are not already enabled.
|
|
20
61
|
- `gui.setHotkeysEnabled(false)` will disable hotkeys if they are not already disabled.
|