View Issue Details

IDProjectCategoryView StatusLast Update
0000632DarkRadiantMap Editingpublic31.12.2009 20:26
ReporterSneaksieDave Assigned ToSneaksieDave  
PrioritynormalSeverityminorReproducibilityalways
Status closedResolutionfixed 
Product Version0.9.6 
Summary0000632: Duplicating part of an entity keeps the duplicate within the entity
Description1. create a multi-brush entity
2. groupcycle to one of the brushes, and duplicate it
3. deselect and reselect the group

Notice that the new, duplicated brush is part of the group.

While this may have some obvious benefit (duplicating a railing, to add to its length), there is currently no way to undo this auto-grouping short of reverting to worldspawn. Since it doesn't happen for full entities, it also represents inconsistent/unexpected behavior. In DoomEd, the default behavior is to assume the new duplicate is a separate entity. From there, the user is free to (1) revert to worldspawn, (2) use it as a separate entity, or (3) reparent to put them in the same group; these are more friendly options.
TagsNo tags attached.

Activities

greebo

greebo

07.04.2008 06:41

administrator   ~0001127

>> 1. create a multi-brush entity
>> 2. groupcycle to one of the brushes, and duplicate it
>> 3. deselect and reselect the group"

This is actually the intended behaviour and the code specifically made it this way (it's not a bug in that sense). I thought this behaviour would be desired, but obviously it's not. :)

So, you're requesting that cloned children should go into a newly created entity?
SneaksieDave

SneaksieDave

07.04.2008 14:48

reporter   ~0001128

Yeah, I assume that would be best, not just because it's how DoomEd does it, but because it gives the user more options on "what to do next" with the clone (numbers 1,2,3 above). With it as part of the new entity, they're pretty much stuck* with it that way.


*That said though... if there was an easy way to multi-select and disassociate parts (0000631, revert to worldspawn partial) of the whole, they'd be able to do it the other way, but I assume we're a way's off from that. :)
greebo

greebo

11.10.2009 17:58

administrator   ~0002678

Reading through your last comment, it seems with 0000631 closed this issue can be set to resolved as well?
greebo

greebo

13.12.2009 07:29

administrator   ~0002760

Bump?
SneaksieDave

SneaksieDave

31.12.2009 20:26

reporter   ~0002812

Yup! Resolved.

Issue History

Date Modified Username Field Change
06.04.2008 21:23 SneaksieDave New Issue
07.04.2008 06:41 greebo Note Added: 0001127
07.04.2008 06:41 greebo Status new => acknowledged
07.04.2008 14:48 SneaksieDave Note Added: 0001128
11.10.2009 17:58 greebo Note Added: 0002678
13.12.2009 07:29 greebo Note Added: 0002760
13.12.2009 07:29 greebo Status acknowledged => feedback
26.12.2009 10:03 greebo Assigned To => SneaksieDave
31.12.2009 20:26 SneaksieDave Note Added: 0002812
31.12.2009 20:26 SneaksieDave Status feedback => closed
31.12.2009 20:26 SneaksieDave Resolution open => fixed