@procore/bim-webviewer-sdk 5.0.0-tutti → 5.1.0-rc.1

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 CHANGED
@@ -5,26 +5,33 @@ 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]
8
+ ## [5.1.0] - 2022-08-22
9
9
 
10
- ### Removed
10
+ ### Added
11
11
 
12
- - [Internal][undocumented breaking change] Removed `enableVertexArrayObject` option.
12
+ - `Isolate` in the Context Menu is now enabled when multiple objects are selected.
13
13
 
14
14
  ### Changed
15
15
 
16
16
  - Decreased load time, especially for larger models, by optimizing the way we construct object bounding boxes.
17
- - [Internal] Adds stats-js to the dev environment to report on FPS, Frame Duration, Memory Usage.
18
- - [Internal] Always use Vertex Array Objects.
19
- - The three.js upgrade made it difficult to continue supporting the non VAO code-path so we are now always using them.
20
17
  - Improves mouse control:
21
- - The contact of the mouse to the model is now sticky when clicking/dragging the model ("panning");
22
- - Eliminates the drift when panning and coming back to the original mouse location;
23
- - Improves the zoom experience;
18
+ - Eliminates the drift when clicking and dragging on the default tool;
24
19
  - Improves handling of the mouse leaving the browser and coming back in, by terminating the interaction.
25
- - [Internal] Refactors Meshnode and Mesh
26
- - Removes the Procore.propertyIdMap, Procore.meshMap and Procore.meshnodeAttach from ProcoreRenderer;
27
- - Switches scene graph implementation from bvhtree to kdtree.
20
+ - Eliminate "space junk" when zooming to global view
21
+ - This change only occurs in some situations depending on whether a `bcfCamera` option was provided. More specifically:
22
+ - When a home viewpoint is defined (i.e. a `bcfCamera` option is passed)
23
+ - The model is loaded with the camera at the home viewpoint
24
+ - Clicking the Home button zooms to the home viewpoint
25
+ - `ProcoreBim.camera.zoomToGlobal()` zooms to the refined global bounding box, which is calculated the first time and cached in JS memory for the remainder of the browser session (i.e. it is lost on page reload).
26
+ - When a home viewpoint is NOT defined (i.e. no `bcfCamera` option is passed)
27
+ - The model loads with the camera with the refined global bounding box in view. The refined global bounding box is calculated here, adding to the load time of the model, and then cached in JS memory for the remainder of the browser session (i.e. it is lost on page reload).
28
+ - Clicking the Home button zooms to have the refined global bounding box in view. The refined global bounding box will be cached from when the model was opened.
29
+ - `ProcoreBim.camera.zoomToGlobal()` zooms to the refined global bounding box, which will be cached from when the model was opened.
30
+ - Performance Note: the execution time for eliminating space junk scales with the number of meshnodes in the model. Mostly this cost is incurred at load time, but will be incurred the first time `ProcoreBim.camera.zoomToGlobal()` is called if a `bcfCamera` option was provided.
31
+
32
+ ### Fixed
33
+
34
+ - The loading tool (`ProcoreBim.Webviewer.tools.LOADING`) now shows an error message when a model is too large instead of crashing silently.
28
35
 
29
36
  ## [5.0.0] - 2022-08-08
30
37