Philippe Leefsma

To me it looks more like a point of view, showing the splitter and other elements of the layout definitely sounds like layout logic so I would rather have that...

I would need to look at the fragment support but I'm rather busy at the moment, also I'm actively using the lib in several projects and the topic has never...

I've never had the need to retrieve flex values in that way, so yeah there is actually no way but it should be doable to add all elements as part...

Sorry for the delay, quite busy these days... It should be straightforward to expose an `onResize` prop on `ReflexContainer` that contains an array with all the elements and their respective...

Yes I agree with you, the approach of the initial implementation of the lib is getting rusty. I was thinking about a complete rewrite of the internal logic based on...

Did you set `windowResizeAware={true}` on the `ReflexContainer`? I would need to see a concrete example to tell if something is wrong with your layout.

Same here, getting error `ERR_REQUIRE_ESM` which seems to be related to the way lib is being exported: https://github.com/standard-things/esm/issues/868 Reverting to 2.6.0 works thanks.

+1 - It works on my mac book pro but when testing on windows it doesn't work. Also the CTRL+click is firing a contextmenu event on Mac so it's super...

Thanks for the feedback, not using logarithmic depth and set explicitly `depthFunc: THREE.LessEqualDepth` on the selected material, same result unfortunately. I didn't test `sortObjects: false`, the meshes and the PC...

ok so first of all, if you are new to react and that lib my first advice would be that you start with a very basic example so you can...