Bay 12 Games Forum

When I run qfconvert on linux i get this.
Traceback (most recent call last):
  File "/home/rain/.apps/quickfort/src/qfconvert/qfconvert.py", line 83, in run
    output = blueprint.process_blueprint_file(infile, options)
  File "/home/rain/.apps/quickfort/src/qfconvert/blueprint.py", line 90, in process_blueprint_file
    output = convert_keys(keys, options.mode, options.title)
  File "/home/rain/.apps/quickfort/src/qfconvert/keystroker.py", line 360, in convert_keys
    return '\n'.join(convert_to_macro(keys, title)) + '\n'
  File "/home/rain/.apps/quickfort/src/qfconvert/keystroker.py", line 393, in convert_to_macro
    "Key '%s' not bound in interface.txt" % key
Exception: Key '0:3' not bound in interface.txt

Note this is from running a simple #dig file with two squares marked nothing else.

Another bug:

When the template has a line containing "#<" or "#>" it adds an extraneous "End Of Macro" where there should be none. Leaving the "End of Macro" line causes the macro to stop prematurely, if you delete the "End Of Macro" line from the files they work as anticipated.

Thanks again for all the hard work! It really is a great script!

I found another bug, The annotation for defining the starting point of the script is broken. In quickfort files the first line can look like this.
#dig start(10;15; insert comment here)

#query files also default to the last instance of the hotkey in the statefulQF file It might be better to implement quieries using the lines
'a' : ('HOTKEY_LOOM_WEAVE_METAL', 'Query'),
'a' : ('HOTKEY_KITCHEN_COOK_2', 'Query'),
as this
'a' : ('CUSTOM_A', 'Query'),

That is just one solution, The built-in macro command lumps all possible commands for that keypress into the same field ie.
                OPTION1
CUSTOM_A
WORLD_PARAM_ADD
WORLD_PARAM_REJECT_ABORT
WORLD_GEN_ABORT
A_COMBAT_ATTACK
A_ANNOUNCEMENTS
A_BARTER_CURRENCY_1
BUILDJOB_ADD
        ....
End of group

Each solution would work

I also have a quick question: Do aliases work? I did some testing and they seem to be broken, It may have been a result of the aforementioned problem though 

here's the line i use in the terminal
python ~/.apps/LinDesignator/LinDesignator.py /home/rain/.apps/templates/mytemplates/dorms_build.csv > /home/rain/.apps/df_linux/data/init/macros/dorms_build.mak

the plain text contents of the origiinal file
#build,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,
,b,t,c,,,,,,,,,,,,,,,,,,,,,,,,,,,,
,h,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,
and lastly the error I getL


python ~/.apps/LinDesignator/LinDesignator.py /home/rain/.apps/templates/mytemplates/dorms_build.csv > /home/rain/.apps/df_linux/data/init/macros/dorms_build.mak
Traceback (most recent call last):
  File "/home/rain/.apps/LinDesignator/LinDesignator.py", line 167, in <module>
    dmacro.StartMacro(sys.argv[1],delay)
  File "/home/rain/.apps/LinDesignator/LinDesignator.py", line 102, in StartMacro
    self.RunMacro()
  File "/home/rain/.apps/LinDesignator/LinDesignator.py", line 145, in RunMacro
    self.mtype.handleBlock(self.cursor,macro[j][i],block)
  File "/home/rain/.apps/LinDesignator/MacroType.py", line 99, in handleBlock
    sendQFSequence(keyseq)
NameError: global name 'sendQFSequence' is not defined


The macros that this outputs don't seem to work with 0.31.12 The game coughs up an i/o error.