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
create two brushes, A is worldspawn, and make B a func_wall
cmd+click A, then B
right click and choose "move brushes to func_wall"
A will be selected, B is deselected
I'd prefer if the entire func_wall (A and B) were selected at this point (how TB1 behaved).
One reason to select all brushes in the merged func is, since the order of selections matters for determining what is merged into what, if you accidentally merge in the wrong direction (trying to merge a few brushes from entity X into entity Y, but instead you merge entity Y into entity X), you won't see it unless you double click to select all brushes in the merged func.
The text was updated successfully, but these errors were encountered:
Why do you have to select all brushes to see what has been merged into what?
This applies to the use case when you have two existing func_details (say, buildings) and you want to transfer a few brushes from one to the other. Without selecting all brushes in the merged result, the only other visual hint telling you which direction the merge happened is the bounding box, which can be easy to miss. (in this case if you merge in the "wrong" direction, you'll end up with both buildings in a single func_detail)
Current behaviour is:
I'd prefer if the entire func_wall (A and B) were selected at this point (how TB1 behaved).
One reason to select all brushes in the merged func is, since the order of selections matters for determining what is merged into what, if you accidentally merge in the wrong direction (trying to merge a few brushes from entity X into entity Y, but instead you merge entity Y into entity X), you won't see it unless you double click to select all brushes in the merged func.
The text was updated successfully, but these errors were encountered: