Extended Color BASIC high resolution modes part 2, and more GET PUT postulations.

[@acs8-bitzone651]

I've been meaning to say that these videos are really interesting. Your knowledge of the get and put instructions is really deep. I was using them in my latest video but did not realize the thing about divide by 5 to know how many elements to dim. I'm still trying to grasp what that is about. Keep up the awesome stuff. I like these byte sized chunks!

[@allenhuffman]

if I actually planned things out, I would shoot for 5 minute videos, but my rambling gets the best of me when I am falling down the rabbit hole. I still don’t know how they work, yet. I will continue to share as I learn. The single dimensioned array thing was an accidental discovery I was not aware of. It was a "if it’s not using each array entry for a pixel, then it must just be using the memory" and trial and error to see how small it would take, then trying single dimensioned arrays, and that let to understanding the storage better. The ,G and ,PSET stuff will be the next task. I think I have written enough simple test tools that I should get it figured out soon.

[@acs8-bitzone651]

Allen, is the DIM reserving 5x bytes to hold floats, but get/put come along and use the buffer to hold bytes? I *think* the Color Basic manuals taught us to overestimate the DIM size by making it the size of the graphic object if I'm remembering correctly. Did the Rainbow or other publication ever expose the true details to your knowledge?

[@acs8-bitzone651]

@@allenhuffman I have to laugh at myself then. I was actually doing a DIM(14,14) to later do a GET of a 15 by 15 pixel area. I was probably reserving about 1125 bytes to store only 45 bytes!

[@allenhuffman]

@@acs8-bitzone651 I know Rainbow had an article (maybe in 1985) about GET/PUT that showed using byte-boundaries for speed. That's the only thing I can recall reading beyond the manual, so that must have been where I first heard about the DIM size being too much.

[@allenhuffman]

@@acs8-bitzone651 Hmm, not this one, but there's an article describing something I was about to experiment with -- colorcomputerarchive.com/repo/Documents/Magazines/Rainbow,%20The%20(Clearscan)/The%20Rainbow%20Vol.%2004%20No.%2006%20-%20January%201985.pdf

[@GORF_EMPIRE]

Interesting tut.

[@ms-ex8em]

i just wondered how did u get basic on the tandy emulator (xroar) as 4.2???? it only goes upto 1.4 i think!!???? thanks.....

[@allenhuffman]

Thank you for noticing. That is just a PRINT statement for the title screen of my video. :) 4.2 (42) is a reference to Hitchhiker's Guide to the Galaxy, which is where we took the Sub-Etha Software name from.

[@ms-ex8em]

you must have just typed it out as a basic program into the emulator? am i right?......

[@allenhuffman]

@@ms-ex8em Yes, that is a Raspberry Pi 400 running the XROAR emulator.

[@ms-ex8em]

@@allenhuffman yep I also have a raspberry pi but I can’t seem to run xroar on it???? Thanks ……..

[@allenhuffman]

I actually built mine from source code to learn how to do it. If you are interested in CoCo emulation on a Pi, check out the CoCo-Pi project. It is an SD card image ready to load on a Pi with several CoCo emulators set up and ready to go. You just configure it for your WiFi and it can even download updates and add ons. It also comes with tons of programs. coco-pi.com