You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I would like to select blocks/regular nodes always, regardless if a block is selected or not. Currently when a block is selected, you can't click on regular nodes and when a regular node is selected, you can't click blocks. I think this is bad and a workflow bottleneck. Instead, if whatever kind of raycast you're doing ends up on a regular node, you should be to select that node instead of the block behind it (if any). Similarly, while having a regular node selected, you should be able to select blocks as well.
Additionally, the Cyclops toolbar should be visible always, so you don't have to select a block if you want to make a prism or cylinder. You might think this would make the Cyclops dock obsolete, but that's wrong. Instead of having "make block" button there, why not use it for global Cyclops settings, including the setting for toolbar visibility.
The text was updated successfully, but these errors were encountered:
I would like to select blocks/regular nodes always, regardless if a block is selected or not. Currently when a block is selected, you can't click on regular nodes and when a regular node is selected, you can't click blocks. I think this is bad and a workflow bottleneck. Instead, if whatever kind of raycast you're doing ends up on a regular node, you should be to select that node instead of the block behind it (if any). Similarly, while having a regular node selected, you should be able to select blocks as well.
Additionally, the Cyclops toolbar should be visible always, so you don't have to select a block if you want to make a prism or cylinder. You might think this would make the Cyclops dock obsolete, but that's wrong. Instead of having "make block" button there, why not use it for global Cyclops settings, including the setting for toolbar visibility.
The text was updated successfully, but these errors were encountered: