View Issue Details
ID | Project | Category | View Status | Date Submitted | Last Update |
---|---|---|---|---|---|
0000530 | DarkRadiant | Map Editing | public | 17.01.2008 12:16 | 13.03.2009 12:32 |
Reporter | STiFU | Assigned To | orbweaver | ||
Priority | normal | Severity | minor | Reproducibility | N/A |
Status | closed | Resolution | fixed | ||
Product Version | 0.9.4 | ||||
Target Version | 0.9.8 | Fixed in Version | 0.9.8 | ||
Summary | 0000530: Editing properties of multiple entities of the same type | ||||
Description | When selecting mutliple entities of the same type the entityeditor does not work anymore, so no properties can be changed on all of them directly. Making this possible or (even better) giving the user the opportunity to create instances of entities would be highly apreciated. The last suggestion would be more work though I guess, so better just stick to the basic solution, if at all! | ||||
Tags | No tags attached. | ||||
I was about to track this myself. I am doing some AI load tests in a map that is basically a box with 100 AI in it. As such, I need to edit the properties of all 100 AI each time I want to test a new setting. I was surprised to find out (guess I never tried it in DR before!) that you cannot. In DoomEd, you select the entities (they don't need to be the same type) and then add or remove or change fields to all at once. In DR, the fields become disabled, preventing this action (eep, I ended up using Notepad to accomplish the task). While the DoomEd method isn't protected for the user, if the user is going the "power-mode" route (typing values in by hand) we can probably hope/assume they know what they're doing, and give them carte blanche. This is similar to 0000599, but not as specialized (that is about light inspector controls specifically). |
|
Yep, we may not forget about the powerusers. In the end, nearly everyone will end up as one of them, so quick and direct access on the properties of multiple entities is very important. In this context, this issue and 0000599 should be generalized in the way, that the entities mustn't even be of the same type. Just leave the text-field enabled. And if the are of the same type, you can keep the normal controlls and just leave "blanks" where the entityproperties don't match up. |
|
Confirmed, this should be possible (at least for the key/value text boxes, even if menu-based selection is not possible for multiple entities). | |
Status changed in error | |
Resolved in revision 3808 | |
Date Modified | Username | Field | Change |
---|---|---|---|
17.01.2008 12:16 | STiFU | New Issue | |
17.03.2008 23:22 | SneaksieDave | Note Added: 0001090 | |
17.03.2008 23:23 | SneaksieDave | Note Edited: 0001090 | |
18.03.2008 16:00 | greebo | Status | new => acknowledged |
20.03.2008 19:43 | STiFU | Note Added: 0001096 | |
18.10.2008 12:01 | orbweaver | Note Added: 0002091 | |
18.10.2008 12:01 | orbweaver | Status | acknowledged => confirmed |
18.10.2008 12:02 | orbweaver | Severity | tweak => minor |
18.10.2008 12:54 | orbweaver | Status | confirmed => resolved |
18.10.2008 12:54 | orbweaver | Fixed in Version | => 0.9.8 |
18.10.2008 12:54 | orbweaver | Resolution | open => fixed |
18.10.2008 12:54 | orbweaver | Assigned To | => orbweaver |
18.10.2008 12:55 | orbweaver | Note Added: 0002094 | |
18.10.2008 12:55 | orbweaver | Status | resolved => confirmed |
18.10.2008 13:32 | orbweaver | Note Added: 0002096 | |
18.10.2008 13:32 | orbweaver | Status | confirmed => resolved |
18.10.2008 13:33 | orbweaver | Target Version | => 0.9.8 |
13.03.2009 12:32 | greebo | Status | resolved => closed |