Posted By
Torque222
on 2018-06-25
06:41:12
 |  Re: A New Resolution!
@MMS I do have some strict ideas and rules about what exactly is the mode we are talking about.
For instants the regular text mode has a global background color.
At the same time it is the most economical for storing screen data.
I really wanted more depth so I was wondering if we could change the background color 40 times during FLI or in the Plus 4 case a DFLI. But no as the machine just isn't fast enough for that.
The mode Graphic 1 utilises 10k but using character data we store our picture data somewhere else and we should have around 47k to utilize for font picture data. My data is placed Luminance Data, Color Data, Char data.
I am not using a bitmap therefore I am not loading 10k and therefore this memory is not counted as the cost of the screen data but rather 3000 bytes is counted per screen even if the computer uses 1024 bytes for luminance data area 24 bytes unused I am storing my 1000 bytes higher in memory and I am not counting the extra wasted 24 bytes either. So, again we have around 48128 bytes to use for our screen. We don't have to use it all but we could if we wanted to. Enough for 16 pages of screen data.
Has anyone ever made a mosaic using all plus 4 fonts and the answer would be no. You know why? Bubis said that all color combinations are 121 X 120 which is 14520 and that is per CHR$. and if you take 14520 X 128 = 1858560 which is exactly subtracting most of the duplicates compared to my earlier estimate and my math holds true I said it needed a subtraction. But the earlier numbers are still valid. You can can place black numbers on a black background with independant luminance values for foreground and background you just won't see anything but is doesn't cause any errors either.
The ability to change the font pointer to access all 256 fonts is only good if it can be changed during a DFLI 40 times per line. Unless mistaken I think this can't be done and you will only have access to 128 but if you want to do a slow placement from basic then this would be fine. With that said you can point the system to any custom font at any time from basic. I am more interested in later leaving it possible to be used with a DFLI or other ML application.
The New Resolution is not just the possibility of different resolution but determination if you didn't get that.
So, the way that I am using this bitmap is not as a bitmap.
I am using it as a text screen or custom font screen.
HCTM = High Color Text Mode.
MHCTM = Multi-High Color Text Mode if used later.
At least anyone interested will know what I am talking about.
|
