David Evans

I just realized this was closed, but might actually be my problem. Did you ever find a work-around for this?

@idling-mind That was helpful in keeping the nodes, but the connections don't seem to re-render for some reason.  As you can see, it seems from the console.logged node that...

I am also having this issue when I switch between flume graphs. I used a key to trigger re-renders, as described in https://github.com/chrisjpatty/flume/issues/71 which works great, but all of my...

Ok! I went through and managed to create a new example project and sliced down a lot of the fluff that's in the primary project I'm working on. Still not...

@navanshu Yep, my issues seems to be a bit different, maybe I'm doing something wrong though. The lines aren't appearing at any zoom level, really. But when connect new ones...

I also noticed this problem, we might need something like this again? https://github.com/chrisjpatty/flume/pull/51/files Alternatively, optional chaining in JS `?.` could be used to return false if any of these elements...

Problem vanished when I upgraded my react app to the latest version today. Just thought I would mention it here in case someone else is on an older version and...

This is definitely something that's important and I wanted to poke this again. It's critical for something like water, where you want to have subsurface light scattering based on depth...

Well at least that seems due in r112, that will be a nice Christmas present :D.

> > This work depends on [mrdoob/three.js#15840](https://github.com/mrdoob/three.js/pull/15840) > > @dmarcos it seems that [mrdoob/three.js#15840](https://github.com/mrdoob/three.js/pull/15840) got closed. Now that's what I wanna hear! What an awesome birthday present :D. Gonna have...