Dwarf Fortress Bug Tracker - Dwarf Fortress
View Issue Details
IDProjectCategoryView StatusDate SubmittedLast Update
0001014Dwarf FortressDwarf Mode -- Interface, Squad Schedulepublic2010-04-11 14:492010-06-09 06:45
ReporterNobu 
Assigned ToFootkerchief 
PrioritynormalSeveritycrashReproducibilityalways
StatusclosedResolutionduplicate 
PlatformPCOSWindows VistaOS VersionSP1
Product Version0.31.01 
Target VersionFixed in Version 
Summary0001014: Crash when changing alerts on squad scheduling screen
DescriptionThe 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 InformationIf you don't TAB to highlight the current order, the game doesn't crash, so it's not hard to avoid.
Tagsalert, crash, schedule, squad
Relationships
duplicate of 0000156closed Toady One Schedule grid / inactive causes crash 
Attached Files
Issue History
Date ModifiedUsernameFieldChange
2010-04-11 14:49NobuNew Issue
2010-04-11 14:51NobuTag Attached: alert
2010-04-11 14:51NobuTag Attached: crash
2010-04-11 14:51NobuTag Attached: schedule
2010-04-11 14:51NobuTag Attached: squad
2010-04-11 14:51NobuTag Detached: squad
2010-04-11 14:51NobuTag Attached: squad
2010-04-11 15:19FootkerchiefNote Added: 0002883
2010-04-11 15:21FootkerchiefIssue Monitored: Footkerchief
2010-04-11 15:49FootkerchiefTag Attached: AWAITING UPDATE
2010-04-11 17:39NobuNote Added: 0002918
2010-04-11 17:40NobuNote Edited: 0002918bug_revision_view_page.php?bugnote_id=0002918#r939
2010-04-11 18:25FootkerchiefRelationship addedduplicate of 0000156
2010-04-11 18:25FootkerchiefStatusnew => resolved
2010-04-11 18:25FootkerchiefResolutionopen => duplicate
2010-04-11 18:25FootkerchiefAssigned To => Footkerchief
2010-04-11 18:25FootkerchiefNote Added: 0002932
2010-05-17 18:14Logical2uTag Detached: AWAITING UPDATE
2010-06-09 06:45Toady OneStatusresolved => closed

Notes
(0002883)
Footkerchief   
2010-04-11 15:19   
Is this a duplicate of 0000156?
(0002918)
Nobu   
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   
2010-04-11 18:25   
Cool, thanks!