View Issue Details

Jump to NotesJump to History
IDProjectCategoryView StatusDate SubmittedLast Update
0001939Dwarf FortressGeneralpublic2010-05-17 23:402010-12-11 09:03
ReporterKamil Assigned ToBaughn  
PrioritylowSeverityminorReproducibilityalways
Status closedResolutionfixed 
Product Version0.31.04 
Fixed in Version0.31.05 
Summary0001939: Double execution of recorded macros
DescriptionUsing the build-in macro recorder/player, after recording a designation to put some furniture in a room, replaying the recorded macro causes it to run twice.
Steps To Reproduce1) choose furniture to put, place the cursor in desired spot
2) begin recording macro (ctrl + r)
3) place some furniture for a room (e.g. door, bed, cabinet)
4) end recording (ctrl + r)
5) choose the same first furniture to put and place the cursor in another room
6) run the macro (ctrl + p)
Additional InformationMacros for digging designations seem not to be affected.
A workaround is to finish the macro in the same spot it was started (i.e. moving the cursor to the beginning, choosing the first furniture)
TagsNo tags attached.

Relationships

child of 0001920 closedBaughn Stocks screen hangs on "stone" and then skips to next category 

Activities

user6

2010-05-18 14:04

  ~0006974

Can anyone confirm this problem?

Kamil

2010-05-20 09:05

reporter   ~0007072

Last edited: 2010-05-20 10:07

 Correction, it seems to be connected to more complex and/or time consuming designations (digging also). It seems that, while the game processes the macro it "holds" the macro button leading to repeated command (increasing the init KEY_HOLD_MS value solved this problem, but that's just a workaround).
Increasing init's MACRO_MS value doesn't help though.

Edit:
It might be related to the z-stocks stone cursor jump-over.

0x517A5D

2010-05-28 22:23

reporter   ~0007458

I confirm this problem. I experienced exactly this with a floor-building macro, and worked around it by temporarily increasing KEY_HOLD_MS.

Kamil

2010-06-06 08:41

reporter   ~0007793

I no longer experience this problem in 0.31.05 version.

user6

2010-06-06 09:12

  ~0007794

Excellent. Marking as fixed.

Issue History

Date Modified Username Field Change
2010-05-17 23:40 Kamil New Issue
2010-05-18 14:04 user6 Note Added: 0006974
2010-05-20 09:05 Kamil Note Added: 0007072
2010-05-20 09:29 Kamil Note Edited: 0007072
2010-05-20 09:56 user6 Relationship added parent of 0001990
2010-05-20 10:07 Kamil Note Edited: 0007072
2010-05-20 12:08 user6 Relationship deleted parent of 0001990
2010-05-20 12:08 user6 Relationship added child of 0001920
2010-05-28 22:23 0x517A5D Note Added: 0007458
2010-06-04 10:38 user6 Tag Attached: Fixed in 31.05?
2010-06-06 08:41 Kamil Note Added: 0007793
2010-06-06 09:12 user6 Note Added: 0007794
2010-06-06 09:12 user6 Status new => resolved
2010-06-06 09:12 user6 Fixed in Version => 0.31.05
2010-06-06 09:12 user6 Resolution open => fixed
2010-06-06 09:12 user6 Assigned To => Baughn
2010-06-09 06:45 Toady One Status resolved => closed
2010-12-11 09:03 user11 Tag Detached: Fixed in 31.05?