xeolabs

Thanks @stefHin - I won't merge this PR, instead I'll make these fixes in the codebase "manually", using your PR as a guide. I just fixed ````xeogl.clear()```` in master: https://github.com/xeolabs/xeogl/commit/7ec555f2ef770e106c389c4b15142eda50551290...

Yes I was wondering whether I should be doing that - only reason I used the non-array form was for consistency with other scalar properties, for example on XEO.PlaneGeometry, which...

Hello Stephen! Yeah I know, it's huge and I do plan to extract the examples out into a separate repo, pretty much as you've described.

Would it be possible to encapsulate this within ````Viewer```` so that it's transparent to the user?

Hi, We don't currently support showing only objects with specific UUIDs in storey maps unfortunately, but you can filter what types are shown. For that, this should do the trick:...

No probs - here's where the plugin lives: https://github.com/xeokit/xeokit-sdk/tree/master/src/plugins/StoreyViewsPlugin

Nope, won't be a problem. When xeokit does its existing pick operations, it renders to a **hidden** framebuffer, which we then read pixels from, which does not disrupt normal rendering...

Hi, yes please share, would be super interesting. BTW this kind of selection is on our roadmap, but we haven't got to it yet. Since we've switched to WebGL2, we've...

This error is from a dependency, ````loaders.gl````, which seems to build with warnings within our process. I'm not sure what we can fix on our end, if anything, but the...

Sounds like a ReactJS issue (which unfortunately we can't help much with, since it's a 3rd-party lib outside the responsibility of xeokit). On our end, the best we can do...