Dwarf Fortress Bug Tracker - Dwarf Fortress |
View Issue Details |
|
ID | Project | Category | View Status | Date Submitted | Last Update |
0000156 | Dwarf Fortress | Dwarf Mode -- Interface, Military Screen | public | 2010-04-02 10:54 | 2010-06-09 06:46 |
|
Reporter | DoctorZuber | |
Assigned To | Toady One | |
Priority | high | Severity | crash | Reproducibility | always |
Status | closed | Resolution | fixed | |
Platform | PC | OS | Windows Vista | OS Version | |
Product Version | | |
Target Version | | Fixed in Version | 0.31.03 | |
|
Summary | 0000156: Schedule grid / inactive causes crash |
Description | The STR pretty much says it all here. It's very easy to reproduce. It's an immediate crash. |
Steps To Reproduce | 1. (m)ilitary
2. (s)chedule
3. (tab) to the schedule grid
4. (*) repeat as necessary until...
5. Crash! |
Additional Information | |
Tags | crash, military screen |
Relationships | has duplicate | 0000209 | closed | Footkerchief | Crash on squad schedules screen | has duplicate | 0001014 | closed | Footkerchief | Crash when changing alerts on squad scheduling screen |
|
Attached Files | |
|
Issue History |
Date Modified | Username | Field | Change |
2010-04-02 10:54 | DoctorZuber | New Issue | |
2010-04-02 11:59 | arcaner | Tag Attached: crash | |
2010-04-02 11:59 | arcaner | Tag Attached: military screen | |
2010-04-03 09:04 | Footkerchief | Relationship added | has duplicate 0000209 |
2010-04-03 15:26 | Footkerchief | Category | General => Dwarf Mode -- Military |
2010-04-03 15:28 | Footkerchief | Category | Dwarf Mode -- Military => Dwarf Mode -- Interface, Military Screen |
2010-04-07 14:11 | DoctorZuber | Note Added: 0001850 | |
2010-04-07 14:52 | Kumquat | Note Added: 0001859 | |
2010-04-07 15:09 | Phydaux | Issue Monitored: Phydaux | |
2010-04-07 15:35 | Draco18s | Note Added: 0001869 | |
2010-04-11 17:42 | Nobu | Note Added: 0002920 | |
2010-04-11 17:43 | Nobu | Issue Monitored: Nobu | |
2010-04-11 18:25 | Footkerchief | Relationship added | has duplicate 0001014 |
2010-04-11 18:25 | Footkerchief | Issue Monitored: Footkerchief | |
2010-04-12 07:11 | Toady One | Note Added: 0003039 | |
2010-04-12 07:11 | Toady One | Status | new => resolved |
2010-04-12 07:11 | Toady One | Fixed in Version | => 0.31.03 |
2010-04-12 07:11 | Toady One | Resolution | open => fixed |
2010-04-12 07:11 | Toady One | Assigned To | => Toady One |
2010-04-12 15:25 | Nobu | Issue End Monitor: Nobu | |
2010-04-14 09:26 | Phydaux | Issue End Monitor: Phydaux | |
2010-06-09 06:46 | Toady One | Status | resolved => closed |
Notes |
|
|
should sticky this or something to make sure toady sees it since it is an easily reproducible crash. |
|
|
|
Another very easy way to reproduce this crash is to make a month with 'no scheduled order', copy it, and then paste it on top of a 'train' order. |
|
|
|
|
|
(0002920)
|
Nobu
|
2010-04-11 17:42
|
|
It doesn't matter what alerts are involved; you just need to highlight the order instead of the schedule grid, then press * or / (default binding to move to the next alert) one or more times. When you try to move past the last alert or before the first alert, you get an instant crash.
It's probably not wrapping around to the other end of the alerts list correctly, and is trying to load an nonexistant alert. Just a guess from my programming experience. |
|
|
|
Okay, this is fixed for 0.31.03. |
|