RE: Naming Convention for Text Primitives
2018-12-29, 15:12 (This post was last modified: 2018-12-29, 15:13 by Ulrich Röder.)
2018-12-29, 15:12 (This post was last modified: 2018-12-29, 15:13 by Ulrich Röder.)
...by the way....consistent height
when using txt2dat in LdPartEditor the height of upper and lower Glyphs is absolutly identic....when writing them separatly.
Only when writing them together the relation of the different heights is given.
A nice Trap...and important to keep that in mind for the different cases.
But back to the core about this thread:
Which decision consumes less resources..will mean efficiency..and which one less stress ... means effectiveness?
....out of the belly .... I also tend to divide the glyphs .. for easy handling.
OTOH .... just a file, only where it is necessary to copy and change the color in the editor .... is done quickly ....
.... but then we need a color appendix or prefix in the filename, for the resulting new primitive.
... and would it not be better to label the characters (comma, percent, dot, exclamation ect.) ... with consecutive (each the next free) numbering?
when using txt2dat in LdPartEditor the height of upper and lower Glyphs is absolutly identic....when writing them separatly.
Only when writing them together the relation of the different heights is given.
A nice Trap...and important to keep that in mind for the different cases.
But back to the core about this thread:
Which decision consumes less resources..will mean efficiency..and which one less stress ... means effectiveness?
....out of the belly .... I also tend to divide the glyphs .. for easy handling.
OTOH .... just a file, only where it is necessary to copy and change the color in the editor .... is done quickly ....
.... but then we need a color appendix or prefix in the filename, for the resulting new primitive.
... and would it not be better to label the characters (comma, percent, dot, exclamation ect.) ... with consecutive (each the next free) numbering?