Thread Rating:
  • 0 Vote(s) - 0 Average
  • 1
  • 2
  • 3
  • 4
  • 5
SCREEN() function doesn't make nice with _FONT in graphic modes
#3
I guess I will have to imitate many other programming languages, especially those "related" to C or "quite similar" to C, and import "printf()" and "sprintf()" and definitely forget about PRINT USING. I don't think PRINT USING was used very often for histograms, pie charts and three-dimensional graphic plots. I looked at the source code of QB64 v0.954 and focused on the "USING" scheme. It looks more involved than trying to capture a "qbs" object out of the output to create a new string variable out of it.

LOL I was supposed to be ranting about something else, such as the lack of search using regular expressions. That should be a specialty for QBJS.

I have allowed years pass that I would have done a virtual machine for Lua so we could use the groovy table functionality, and the regular expressions that work even though they are weirder than what is known by Perl, GREP and other programs. I wasn't able to go beyond a replication of the "direntry.h" offered on this forum. Created also as a "dot-SO" file was a routine that read in a binary file into an array-like table of integers. It was faster than doing it only with interpreted code for loading WAV files but was unreliable, and only worked for a specific format. The code to manipulate WAV files overall was still very slow but I wasn't confident doing it in QB64 and I couldn't use QB64, Freebasic, Purebasic or anything like that while totally offline and only with 32-bit Ubuntu Studio.

LOL I said dealing with WAV files with my Lua scripts was very slow but it was slightly better than using Openshot Video Editor with all the Python going on to do almost the entire program. Sleepy
Reply


Messages In This Thread
RE: SCREEN() function doesn't make nice with _FONT in graphic modes - by mnrvovrfc - 05-24-2023, 10:47 AM



Users browsing this thread: 2 Guest(s)