View Issue Details
| ID | Project | Category | View Status | Date Submitted | Last Update |
|---|---|---|---|---|---|
| 0001896 | Dwarf Fortress | Dwarf Mode -- Buildings, General | public | 2010-05-16 07:33 | 2016-01-18 08:59 |
| Reporter | Wyrm | Assigned To | Toady One | ||
| Priority | normal | Severity | minor | Reproducibility | always |
| Status | resolved | Resolution | fixed | ||
| OS | Windows XP | ||||
| Product Version | 0.31.03 | ||||
| Fixed in Version | 0.31.20 | ||||
| Summary | 0001896: Custom workshops get assigned (a) key by default | ||||
| Description | In a custom building, if you do not specify a build key with the [BUILD_KEY:] tag, or specify NONE, then it gets assigned the 'a' key. All of them. | ||||
| Steps To Reproduce | Make a custom building. Do not include a [BUILD_KEY:] tag, or specify [BUILD_KEY:NONE]. Voila. | ||||
| Additional Information | I see no reason why every workshop build should have a hotkey, as some can be rarely used and that hotkey only clutters the interface. Even if there were, the program should bark at us when not specified, and/or assign each a unique hotkey that doesn't collide with other workshops. | ||||
| Tags | Intentional/Expected? | ||||
|
|
Probably fixed? I made few copies of SCREW_PRESS and changed BUILD_KEY in each: [BUILD_KEY:CUSTOM_SHIFT_B] works as expected ("B") [BUILD_KEY:NONE] these three also work as expected (no key) [BUILD_KEY:] BUILD_KEY: |
|
|
Fixed in 31.20. Bug is present in 31.19, but is not in 31.21. |
| Date Modified | Username | Field | Change |
|---|---|---|---|
| 2010-05-16 07:33 | Wyrm | New Issue | |
| 2014-01-27 14:39 |
|
Tag Attached: Intentional/Expected? | |
| 2015-12-13 07:30 | Hedede | Note Added: 0033835 | |
| 2015-12-13 08:21 | Hedede | Note Added: 0033837 | |
| 2015-12-13 08:25 | Hedede | Note Edited: 0033837 | |
| 2016-01-18 08:59 |
|
Status | new => resolved |
| 2016-01-18 08:59 |
|
Fixed in Version | => 0.31.20 |
| 2016-01-18 08:59 |
|
Resolution | open => fixed |
| 2016-01-18 08:59 |
|
Assigned To | => Toady One |
