Closed joelpt closed 11 years ago
Original author: joe...@gmail.com (May 29, 2010 20:23:04)
Currently a blueprint with just d(3x3) in the top left cell will render out as a 1x1 'd'.
A workaround is to put a ` or ~ char in the opposing corner cell, which will force qfconvert to treat the blueprint as that large.
Using # around the perimeter does not work as expected because these are stripped off early in conversion; they have no particular function in qf2.
The fix should properly expand and fixup the width and height of the parent grid in cases such as the initial example.
Original issue: http://code.google.com/p/quickfort/issues/detail?id=14
From joe...@gmail.com on April 08, 2011 00:58:18 Moving back to 2.0 because we want it for Alt+T, dig x(100x100)
From joe...@gmail.com on April 23, 2011 14:13:18 Implemented with a little help from bakergo.
Original author: joe...@gmail.com (May 29, 2010 20:23:04)
Currently a blueprint with just d(3x3) in the top left cell will render out as a 1x1 'd'.
A workaround is to put a ` or ~ char in the opposing corner cell, which will force qfconvert to treat the blueprint as that large.
Using # around the perimeter does not work as expected because these are stripped off early in conversion; they have no particular function in qf2.
The fix should properly expand and fixup the width and height of the parent grid in cases such as the initial example.
Original issue: http://code.google.com/p/quickfort/issues/detail?id=14