Strange behaviour when dettaching children element about flowy HOT 3 CLOSED

Just fixed it - was a small issue with the blue indicator block getting accidentally deleted and thus triggering a javascript error.

As per the blocks getting removed, I've currently kept it that way for simplicity, with only one tree, although if there's a lot of interest I could allow for multiple trees. Shouldn't be hard to implement, but it would lead to having blocks that overlap, making it harder to snap new blocks or to rearrange them.

from flowy.

Thanks a lot for the quick fix!

from flowy.

As per the blocks getting removed, I've currently kept it that way for simplicity

When a block is detached from all blocks, is it possible to snap it back to the previous parent instead of removing it ?

Because when I click on the header (or on the 3 dots in the block header), my mouse often move just a little bit, and the block is suddenly removed.

Or maybe add a threshold distance value above which the block is removed ?

from flowy.