toml_12953 said  

  Geoffg said  

  toml_12953 said  

What this will do is to allow the comma in a PRINT statement to act like other BASICs and move the cursor to the next print zone rather than just print a single space.

Something is not right here... the comma should advance the output to the next tab stop (default 8 char).

Geoff

You're right about the comma outputting tabs. My bad. The default is 2. I'd like to decouple it from the tab key, though so I could have print zones wider than 8 characters. Maybe allowing a larger range for the tab key would be OK.

I just added 10 and 12 to the allowed values of OPTION TAB and recompiled. Setting it to 10 seems to be the best compromise on a 40 column screen. I left the default at 2, though.
I'd still like the print zones to be independent of the tab stops as in other BASICs since I like to use the TAB key to indent when coding and 10 characters is way too much.

For lizby

PSRAM will allow you to create a framebuffer at any resolution. The only limitations are on layer buffers that must be in main memory so if you wanted a layer then you should create that before anything else but framebuffers will use any ram available

@lizby

My program runs in 1024x768 Mode3 with framebuffer on PicoMiteHDMI MMBasic USB RP2350B Edition V6.02.01b7 without PSRAM:

Maybe there is some other problem with your code?!

Edit: You could try without option modbuff 192
Edited 2026-03-02 19:02 by dddns

The issue is that he is using lots of ram for his application. ram memory is a finite resource, you can't use it twice! The size of the modbufffer has no relevance to ram. If he defined the framebuffer before his other ram use then, of course it would work, but then he would get the message when his application was initialising and using ram.

Ok..was just a thought as his memory report shows lower values than mine
Thanks for clarifying modbuff