0 Members and 1 Guest are viewing this topic.
Oh ok but what if someone absolutely needs to use the homescreen while using Coorelation?
Yeah, your program is looking very cool. This will be very useful, I can see that. So is this going to use a parse hook and font hook?
* DJ Omnimaga wonders if this will be useable in Axe
Oh, well there is a neat twist!. So you are going to be making the routine for how Output( and the like act? That is really nice and that will make the routine fast as well.
Quote from: DJ Omnimaga on November 13, 2010, 03:22:45 am* DJ Omnimaga wonders if this will be useable in AxeNot unless we can incorporate it. Sorry --but then since you can display sprites/tilemaps in axe, you really don't need itQuote from: Xeda112358 on November 13, 2010, 03:24:36 amOh, well there is a neat twist!. So you are going to be making the routine for how Output( and the like act? That is really nice and that will make the routine fast as well.Yes. Output will display a custom standard 6x8 font, and Text() will display a custom sized font, the default being the size of small text. The limitation is all characters must be the same size.
You mentioned this on the first page, but I wanted to be sure. Each font set can contain a total of 256 characters? Is there a reason for the limit? I will admit though, it seems very unlikely that anyone would need more that 256 characters.
Since I know that you can have the font set archived, I just have one tip from experience. Store the location of the font set in the archive in ram, don't re-find it every time.
Each font set can contain a total of 256 characters? Is there a reason for the limit? I will admit though, it seems very unlikely that anyone would need more that 256 characters.
But if a font is located in RAM, would deleting and adding variables change its location?
Quote from: Hot_Dog on November 14, 2010, 11:51:05 amBut if a font is located in RAM, would deleting and adding variables change its location?That's true. What I would do is put in a safety check. Make the first two bytes of the file $6969 or $1337 or something. So if that's not what your pointer shows, then re-find it. That would even work for the archive in case the BASIC program happens to pull a garbage collect. (I guess technically it can happen)
As long as the font sets won't take space for 256 chars even when they contain 40 or so, I am fine.