Navigation Menu

Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Brushes created by CSG merging faces should go in the parent of the first selected brush #2384

Closed
ericwa opened this issue Oct 28, 2018 · 1 comment
Closed

Brushes created by CSG merging faces should go in the parent of the first selected brush #2384

ericwa opened this issue Oct 28, 2018 · 1 comment
Assignees
@kduske
Labels
Prio:3 Low priority: Minor problems and nice to have features Type:Enhancement New features
Milestone
2.1.0

Comments

@ericwa
Copy link
Collaborator

ericwa commented Oct 28, 2018 •
edited by kduske

Currently brushes created this way go into worldspawn.

It'd be more consistent if they went in the parent of the first selected brush; this is related current behaviour:

  • CSG merging two brushes, the result goes in the parent of the first selected brush
  • Shift+Ctrl+drag extruding faces, the new brush goes in the same parent as the source brush
@ericwa ericwa added Type:Enhancement New features Prio:3 Low priority: Minor problems and nice to have features labels Oct 28, 2018
@ericwa ericwa added this to the 2.2.0 milestone Oct 28, 2018
@kduske
Copy link
Collaborator

kduske commented Oct 28, 2018

Those are bugs, I'll fix them today.

@kduske kduske modified the milestones: 2.2.0, 2.1.0 Oct 28, 2018
@kduske kduske self-assigned this Oct 28, 2018
@kduske kduske mentioned this issue Oct 28, 2018
Merged
@kduske kduske closed this as completed Oct 29, 2018
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@kduske kduske

Labels
Prio:3 Low priority: Minor problems and nice to have features Type:Enhancement New features
Projects
None yet
Milestone
2.1.0
Development

No branches or pull requests
2 participants
@kduske @ericwa