| Anonymous | Login | Signup for a new account | 2024-11-01 03:32 PDT |  |
| Main | My View | View Issues | Change Log | Roadmap |
| View Issue Details [ Jump to Notes ] | [ Issue History ] [ Print ] | |||||
| ID | Project | Category | View Status | Date Submitted | Last Update | |
| 0001014 | Dwarf Fortress | Dwarf Mode -- Interface, Squad Schedule | public | 2010-04-11 14:49 | 2010-06-09 06:45 | |
| Reporter | Nobu | |||||
| Assigned To | Footkerchief | |||||
| Priority | normal | Severity | crash | Reproducibility | always | |
| Status | closed | Resolution | duplicate | |||
| Platform | PC | OS | Windows Vista | OS Version | SP1 | |
| Product Version | 0.31.01 | |||||
| Target Version | Fixed in Version | |||||
| Summary | 0001014: Crash when changing alerts on squad scheduling screen | |||||
| Description | The game crashes when you are scheduling a squad's actions for a specific alert if you have the current order highlighted instead of the schedule grid, and attempt to change to the alert before the first one or after the last one. The intended behavior is probably to wrap around to the other end of the list, which is what happens if the current order is not highlighted. | |||||
| Steps To Reproduce | (Assuming default key binds) 1> Start a fortress or load a save game 2> m key (military screen) Then create one or more squads and one or more alerts if you didn't load a fort with at least one of each. 3> s key (scheduling) Go to squad's schedule screen 4> TAB key (to highlight current order) 5> / or * key (to change the alert to schedule) The game will crash once you attempt to move past the last alert in the list this way. If you have more than one alert you may need to press the / or * key several times. | |||||
| Additional Information | If you don't TAB to highlight the current order, the game doesn't crash, so it's not hard to avoid. | |||||
| Tags | alert, crash, schedule, squad | |||||
| Attached Files | ||||||
 Relationships |
 Notes |
|
|
(0002883) Footkerchief (manager) 2010-04-11 15:19 |
Is this a duplicate of 0000156? |
|
(0002918) Nobu (reporter) 2010-04-11 17:39 edited on: 2010-04-11 17:40 |
Ah, it is a duplicate apparently. Man, I searched for awhile and couldn't find it anywhere, don't know how I missed it. By the way, as they have it written, it doesn't matter what alerts are involved, just that you try to scroll past them. I'll add a note in the original posting of this bug. |
|
(0002932) Footkerchief (manager) 2010-04-11 18:25 |
Cool, thanks! |
|
Notes |
|
Issue History |
|||
| Date Modified | Username | Field | Change |
| 2010-04-11 14:49 | Nobu | New Issue | |
| 2010-04-11 14:51 | Nobu | Tag Attached: alert | |
| 2010-04-11 14:51 | Nobu | Tag Attached: crash | |
| 2010-04-11 14:51 | Nobu | Tag Attached: schedule | |
| 2010-04-11 14:51 | Nobu | Tag Attached: squad | |
| 2010-04-11 14:51 | Nobu | Tag Detached: squad | |
| 2010-04-11 14:51 | Nobu | Tag Attached: squad | |
| 2010-04-11 15:19 | Footkerchief | Note Added: 0002883 | |
| 2010-04-11 15:21 | Footkerchief | Issue Monitored: Footkerchief | |
| 2010-04-11 15:49 | Footkerchief | Tag Attached: AWAITING UPDATE | |
| 2010-04-11 17:39 | Nobu | Note Added: 0002918 | |
| 2010-04-11 17:40 | Nobu | Note Edited: 0002918 | View Revisions |
| 2010-04-11 18:25 | Footkerchief | Relationship added | duplicate of 0000156 |
| 2010-04-11 18:25 | Footkerchief | Status | new => resolved |
| 2010-04-11 18:25 | Footkerchief | Resolution | open => duplicate |
| 2010-04-11 18:25 | Footkerchief | Assigned To | => Footkerchief |
| 2010-04-11 18:25 | Footkerchief | Note Added: 0002932 | |
| 2010-05-17 18:14 | Logical2u | Tag Detached: AWAITING UPDATE | |
| 2010-06-09 06:45 | Toady One | Status | resolved => closed |
|
Issue History |
| Copyright © 2000 - 2010 MantisBT Group |
 |