Just did the update and all is good.
Thanks.
Bill
Smithville, NJ
whuyse wrote: ↑Fri Feb 28, 2020 6:18 pmHi Bill,
Yes I realised there’s no easy way of copying a matrix to another state file, but I wanted to make it easy to take a peek.
You don’t need UFL though, well not for now, I just put the digit fonts into DF, but the problem remains of course. One of my goals is to have UFL hold all 4 fonts, and do away with DF, but that is going to take a while.
UFL is short for Universal Font Library, a term coming from my ‘48 days
The differences with your CHARS matrix are:
- fonts are ordered small to large, so font 1 is 5 high, font 2 6 etc.
- fonts are top-aligned (well that currently holds only for DF)
- every character ends with a blank
- UFL now contains a font per column, your CHARS one per row. I think I’ll adopt the row encoding as well.
I created UFL from CHARS, actually, and have only added digit fonts 6x4
I’ll see that I can create a DF program, I have been working on a Print Matrix program that will do exactly that
( I have added an 8x5 font 4 in the meantime )
Cheers, Werner
I couldn't use [FIND] because I'm EDITing the matrix.Bill (Smithville NJ) wrote: ↑Fri Feb 28, 2020 6:48 pmI've picked up some new coding techniques from reviewing your programs.
One of the best was the use of subtracting the pressed key code from the key code
matrix and doing 1/x on the matrix. If it results in an error (ie, divide by zero) then
you know if a valid key was pressed. Much quicker/easier than using the matrix FIND
function. I would have never thought of doing that.
Code: Select all
RCL "GK"
CLA
XTOA
>LBL 10
Rv
GETKEY
POSA
X<0?
GTO 10
Rv
GTO IND ST L
Okay. What is important to me is that I can make the whole program independent from the font used, as is currently already the case for the indexes. I can make the font top-aligned when I create the "1", "2", "3 and "4" digit font local variables. I can't use bottom-aligned fonts because they will erase part of the cells above in overwrite mode, which I need as I don't do a CLLCD unless I really have to. I tried to make everything as fast as possible, I had no idea how long a screen refresh would take.Bill (Smithville NJ) wrote: ↑Fri Feb 28, 2020 8:28 pm2. I'm not sure about having the UFL matrix "top aligned". By it being Bottom Aligned,
it makes doing upper/lower case words simple - likewise doing subscripts/superscripts.
3. I think it would be best to have the UFL matrix bottom aligned and then just use your
DF program to adjust for a top aligned digit matrix when required.
I tend to think column-wise, but in this case I will adopt the row order, for the simple reason that extracting a font is then a row, which is stored sequentially. Not that anyone would notice the difference, what with the blazing speed of the DM42.I would like to go ahead and modify my "FONTS" program so that it will create the "UFL" matrix.
I could make the UFL matrix 128x4, insert your middle digits 0-9 and then leave the other columns
with missing fonts as "0".
But before I do this, let's come to a decision of 128x4 or 4x128.
Upper/lower case is no issue of course, that’s not what I meant by ‘topaligned’. It’s just that a font of n pixels occupies the top n pixels, not the bottom n.Bill (Smithville NJ) wrote: ↑Fri Feb 28, 2020 8:28 pm2. I'm not sure about having the UFL matrix "top aligned". By it being Bottom Aligned,
it makes doing upper/lower case words simple - likewise doing subscripts/superscripts.