This was done by making use of multiple strokes of the nominal dcode to realize thicker text strokes when the weight of a line in the ODB font file definition is "heavier" than the nominal.īecause text is handled by first compiling the ODB font file before any translations begins, text strings that more often than not are inserted with different X and Y scaling will not appear as they are rendered in a true ODB++ viewer, i.e. Limited support for ODB font files that contain multi-weight strokes was introduced in v3.17. Odb2gbr is limited to making use of a single dcode when stroking out ODB text in Gerber format. The underlying Boolean library used by this program has been updated to use the most recent version. This version: if the attribute value is blank, the dynamic text resolves to the next available attribute value pair using the following order: layer step miscellaneous job scope. This has now been fixed with memory being assigned dynamically.Įarlier versions: A text feature with dynamic text of an attribute that is referenced by its feature attribute value pair for which the value is blank would not convert/render this dynamic text.
Attribute names or attribute text strings exceeding that limit caused a memory crash. The size for each of these two lists was statically set to 16384. V3.18c () Fixed Feature attribute text string and name issue This page contains the summary of odb2gbr release dates, versions and changes/fixes made for that release.
0 kommentar(er)
