Have you tried something like this?
Code:Myword2.5 = Mybyte1.2 'move bit 2 of Mybyte1 to bit 5 Myword2 Myword2.6 = Mybyte1.3 Myword2.7 = Mybyte1.4 Myword2.8 = Mybyte1.5
Have you tried something like this?
Code:Myword2.5 = Mybyte1.2 'move bit 2 of Mybyte1 to bit 5 Myword2 Myword2.6 = Mybyte1.3 Myword2.7 = Mybyte1.4 Myword2.8 = Mybyte1.5
Last edited by mark_s; - 18th May 2022 at 19:40.
The issue is that these boundaries should be changeable, since different chars will have different pixel width.
There are two ways of doing this - all capitals have same width and all non-capital letters have another, smaller width. This indeed reduces some visual gaps, but not exactly what I want.
So my idea is to have a spare, "mask" byte for each character, which will define it's width and entry and exit points.
Say, there's "t", it is 4 pixels wide, and "mask" for it will look like this 00011110. zeros will be trimmed, and bits #5,4,3,2,1 from the letter shape will be added to output image.
Another, more complex idea, is to do it "ZX Spectrum way", via complex STR/MID/LEN/ASC and other statements, currently not implemented, but still doable, in PBP....
FOR X=1 to 5
Y=Z.X
NEXT
As I understand, such operation is not possible in PBP, I mean, it is not possible to substitute variable as a bit part identifier for another variable?
where did you get that idea, it is very possible with the correct syntaxAs I understand, such operation is not possible in PBP, I mean, it is not possible to substitute variable as a bit part identifier for another variable?
suggest a read of the manual re
Applying Offsets to Bits within a Variable or Register
Warning I'm not a teacher
I didn't get the idea, I just tried it and it gives syntax error......
Bookmarks