| View Issue Details [ Jump to Notes ] | [ Issue History ] [ Print ] |
| ID | Project | Category | View Status | Date Submitted | Last Update |
| 0004471 | Dwarf Fortress | Dwarf Mode -- Interface, Notes/Points/Routes | public | 2011-04-08 02:59 | 2015-06-27 14:52 |
|
| Reporter | CapnRis | |
| Assigned To | Toady One | |
| Priority | normal | Severity | major | Reproducibility | always |
| Status | resolved | Resolution | fixed | |
| Platform | PC | OS | Windows 7 Ultimate 64-Bit | OS Version | |
| Product Version | 0.31.25 | |
| Target Version | | Fixed in Version | 0.40.01 | |
|
| Summary | 0004471: Attempting to name a point in the route menu causes game to lock up |
| Description | In an attempt to make my lever system more clear, I was attempting to place new notes at the lever's controlled systems and make routes out of them. However, when placing a note upon one of the four yet-to-be-built bridges, I accidentally tried to name it before using the 'n' command in the note menu. The keystrokes I used (the note was to be named "Drowning Chamber" brought up the route menu, then attempted to name a route that didn't exist from that point. A blinking text cursor comes up, but no attempt to exit the menu or type a name is successful. Commands that don't use letters or numbers function; the recording feature works, as does zooming with the mouse wheel. The escape, enter, and spacebar keys do not function. I had to forcequit to reproduce. |
| Steps To Reproduce | Save file: http://dffd.wimbli.com/file.php?id=4154 [^]
Place a note at any point; I encountered the issue on the bridges where the save file starts, but reproduction shows it can occur anywhere. Open the routes menu, then attempt to name the route/point before adding a route. Typing should be impossible, as is closing the menu.
Naming the point beforehand seems to have no effect; the bug appears to be in attempting to name a route before using the "Add a route" function. Notes already placed can also be used. |
| Additional Information | I believe this is related to issue 0003382, but the reporter did not bother to find out what s/he'd done to cause it.
I marked it as major due to the way I came across it by accident and the need to terminate the process in order to recover from the bug. |
| Tags | No tags attached. |
|
| Attached Files | |
|
Relationships 
Relationships 