Refactor tb.clear to add layerId
#59
Comments
Closed
jscastro76
added a commit
that referenced
this issue
Oct 25, 2020
…e 3D objects of a layer, apart from removing the layer itself with `map.removeLayer` - [**#56**](#56) Objects cache at `tb.loadObj` - `tb.loadObj` now is 100% async and in the first call to an object load by url, then caches the returned object for the sucessive calls to return a clone of the object through `obj.duplicate()` - Closes [**#51**](#51), [**#55**](#55) - [**#57**](#57) Add a new sample to measure performance - Added new example to demonstrate add thousands of objects and measure performance [Threebox Performance](https://github.com/jscastro76/threebox/blob/master/examples/15-performance.html). - [**#58**](#58) Refactor `tb.remove` - [**#59**](#59) Refactor `tb.clear` to add `layerId`. - [**#60**](#58) Refactor `tb.dispose` - All the examples reviewed and updated and added to the [Examples list](https://github.com/jscastro76/threebox/blob/master/examples/readme.md)
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
tb.clearshould consider also the layerId so it can be reused fortb.removeLayermethod. Then this method should reuse alsotb.remove.Related issues
#58 , #43
The text was updated successfully, but these errors were encountered: