Commander X16

BSOUT allows echoing the output to the terminal. If the rom is not flexible to reposition its map base and layer for character (and bitmap) output, thus, focusing on basic or default level only, then rom is of less use for assembler coders. Conio type of routines are constructed to do the same, but faster and more flexible, as they write directly to vera memory. This however takes memory space in the ram ... and this approach cannot get echoing output working to the terminal (I think, maybe there is another trick).

This is the background of the request. Now that the R39 rom has already mapped the map base to $1B000 and layer 1, an improvement was done comparing with release R38, but still...

Just reflecting my thoughts.

what is BSOUT anyway? I don't recognise it

On 4/3/2022 at 5:25 PM, desertfish said:

what is BSOUT anyway? I don't recognise it

BSOUT and CHROUT is the same function, just called different things in different documentation and source...

SCREEN has a new, undocumented side effect in R39: it also changes background color to blue and foreground color to white. This didn't happen before in e.g. R38. R39 behavior breaks compatibility with many of my R38 programs, but I can fix that. I still think it would be better if the colors were preserved as before, because then you can test different screen modes without having to change the colors.

SCREEN 6 (20x15) works for me in my game Aritm (see Downloads) in R39 to make a more children friendly font, but "Try it now" is still R38.

I could make a version that works in both R38 an R39, by using SCREEN $FF (toggle), but if you RUN it several times it toggles instead of always setting it to 40x30 as it should. When "Try it now" becomes R39 I will probably change it again to SCREEN 3 or SCREEN 6.

the SCREEN color reset behavior bit me too....

Can't take anything for granted...

SCREEN 0:COLOR 1,0:CLS

On 3/30/2022 at 12:18 AM, TomXP411 said:

The text frame buffer is now $1:B000



If your C programs use direct access, rather than KERNAL printing, then you need to modify the library code to use the new address. This will definitely have to be updated in cc65 and Kick C

 

The source for cputc says:

Quote

screen_addr := $1B000 ; VRAM address of text screen

https://github.com/cc65/cc65/blob/master/libsrc/cx16/cputc.s

 

That LOOKS right, but clearly something's wrong.

On 5/15/2022 at 8:53 PM, rje said:

 



The source for cputc says:



https://github.com/cc65/cc65/blob/master/libsrc/cx16/cputc.s



 



That LOOKS right, but clearly something's wrong.

To wit: my brain is wrong.  This change was made since my last build of cc65.

I just have to update.  Duh.

Problem solved.

 

Now I have to read up on what address to load a font file.

 

On 5/16/2022 at 6:35 AM, rje said:

To wit: my brain is wrong.  This change was made since my last build of cc65.



I just have to update.  Duh.

I was going to suggest that, but I thought "Oh, I'm sure he already did that..."  

?