QB64 FAQ
As with everything else, this list will be updated to correspond to new progress of the QB64 language, so make sure that you are using the latest version of QB64 or in our case QB64-PE, which stands for QB64 Phoenix Edition. Please note that it may take a short time to update this list.
Q: What is QB64?
A: QB64 is a BASIC compatible language that creates working Executable files from QBasic BAS files that can be run on 32 or 64 bit PC's using Windows (7 and up), Linux or macOS (Catalina and up). The goal is to be 100% compatible with QuickBASIC 4.5 plus add hundreds of new abilities such as program icons and custom sized windows and a great retro Editor with builtin help.
The new keywords add some new features such as playing music or sound files and instant access to 32 bit graphics file images. Also TCP/IP internet communication is available to download files, email messages over the web or play internet games. DLL Libraries can add more programming options and QB64 can access all of the new USB gaming controllers and printers.
QB is an abbreviation for QBasic or QuickBASIC which is an easy to learn language that grew very popular in the 90's. It uses simple syntax but holds great potential as there are methods to achieve nearly anything. QBasic is more alive than ever with QB64!
Keywords currently not supported by QB64
Q: What's the difference between the various GitHub Forks?
A: Almost nothing, the project development has always been linear, but had different maintainers over time who were using their own GitHub repositories. However, since late April 2022 the development split into 2 new distinct forks, but as one of it stuck very soon after their 1st release, there's still no real choice between different development paths anyways.
Early development was kept private by the original creator of QB64 (Galleon) v0.xxx to v1.0
|
The original Repository Galleon (2013-2019) v1.1 to v1.3
|
The QB64Team Repository QB64Team (2019-2022) v1.4 to v2.0.2
| |
| The QB64Official Repository QB64Official (2022-Today) v2.1 (then stuck)
|
The Phoenix Edition Repository Phoenix Edition (2022-Today) v3.0.0 - v3.12.0++ (and active)
|
As you can see both, the QB64Official and the Phoenix Edition, forked off the QB64Team repository and hence continued development from it's last released v2.0.2 version. The reason for the Phoenix Edition to label its first major release v3.0.0 is just to avoid overlapping with the existing v1.0 to v2.0.2 releases of the former repositories and not (as some bad voices mentioned in the Forum and Discord) to beat out the QB64Official release v2.1, which came in fact two weeks later than Phoenix's v3.0.0 release.
Obviously with eight beta releases and already sixteen major releases in the repository since its start in April 2022 (by the time of this writing), the Phoenix Edition is now far ahead of the QB64Official v2.1, with lots of bug fixes and useful enhancements which you can review in the release notes. All active developers, some from former repositories and some new ones, have gathered in the Phoenix Edition repository now.
So you see, just choosing the word "official" and paying for the domain "QB64.com" doesn't necessarily mean that they're on the way to success, it just attracts more search bots and gives more results on Google. Should QB64Official ever resume to active development in the future, then I doubt they can become a serious competitor to the Phoenix Edition anymore.
Q: Does it have modern features? Do they HAVE to be used?
A: QB64 has plenty of modern features, but they do not have to be used. You may just want to run some of your old favorites.
You could code using the original QuickBASIC syntax all the way through and it should work as you expect it to or even better. QB64 is often faster and has none of the memory limitations that plagued QBasic in the past.
QB64 is not meant to run PDS (7.1) QBX code. Most GW Basic code will run with minor changes.
The modern statements are designed to go along with the BASIC philosophy and expand QBasic into the future!
1) Full graphic functions for images up to 32 bit color. Alpha transparency supported. 2) Instant loading of image files including BMP, PNG, JPEG, GIF and more... 3) Supports stereo sound files like WAV, OGG, MP3, speaker and volume control and more... 4) Animation is easy to do using _DISPLAY instead of page flipping, to achieve flicker-free graphics. 5) Clipboard reading and writing support. 6) Networking over TCP/IP and Email. 7) True type font and Unicode support for many Languages. 8) Integrated mouse and game controller input including scroll wheel support. 9) Support for C++, OpenGL, Windows API and other custom Dynamic Link Libraries. |
Q: How do I install QB64 on Windows, Linux, macOS?
A: QB64 supports the following Operating Systems:
- 1) Download the appropriate package according to your system from our GitHub repository
- 2) Unpack the contents to any location on your computer. Avoid unpacking to Program Files or other system folders that may require administrative privileges. QB64 needs to have full write permissions to its own folder.
- Executable programs are portable between like systems by copying the stand-alone executable file.
- 1) Download the appropriate package according to your system from our GitHub repository
- 2) After extracting the downloaded package, run the installation batch/script called ./setup_lnx.sh in the main qb64 folder to setup QB64.
- 3) Most dependencies should be automatically downloaded by the setup script, but these are the ones you should look for if compilation fails: OpenGL developement libraries, ALSA development libraries, GNU C++ Compiler (g++)
- 1) You must install Apple's Xcode command line tools for C++ compilation from their website. The simplest way to do so is opening a terminal window and typing the following command: xcode-select --install (more info here: Xcode download)
- (you won't be using the Xcode interface, QB64 just needs to have access to the C++ compiler and libraries it installs)
- 3) Download the appropriate package according to your system from our GitHub repository
- Extract the downloaded package and run ./setup_osx.command, found within the QB64 folder to install the QB64 compiler.
- Executable programs are portable between macOS systems by copying the executable file.
- To help launch executables without a console, a file called programname_start.command is created along with the program.
Q: Why won't QB64 work on my computer?
QB64 currently supports Windows versions from 7 to the latest version. Most Linux versions and macOS Catalina and newer are also supported.
- Don't move QB64 executable out of the QB64 folder. The various sub-folders hold the C++ compiler files and libraries.
- QB64 does not change any settings on your machine. All required files are in the QB64 folder.
Q: Are there any known incompatibilities?
A: There are some things that QB64 cannot do, like direct hardware access, which makes older more advanced programs that make use of ABSOLUTE, INTERRUPT, PEEK, POKE and OUT not work properly. Although some older functionality is emulated, if your program doesn't use such statements you probably won't notice any difference between QB 4.5 and QB64 (and if you do, report it as a bug in the forums). You can expect the most common addresses for interrupts, etc. to be functioning.
See: Keywords currently not supported by QB64
You should be careful with CPU usage. QB64 is a lot faster than QBasic was and it does not have many of the size limitations that confined QBasic programming abilities. Having said that, care must be taken to assure that programs do not hog resources. To do that, use speed limits when possible to keep the resources used to a minimum. Also, Monitor Task Manager when your programs are running, as it can tell you how much or system resources are being used in different parts of a program. The following keywords can lower the impact of your programs on those resources by releasing them to other programs:
- _LIMIT: Limits the loops per second in any loop and thus lowers the overall CPU usage.
- _DELAY: Pauses a procedure and releases unused resources for other programs.
- SLEEP: Stops or delays program procedures and shares resources.
QB64 can be fast when you need it to be, but take the time to consider the impact of your program on other programs as people seldom have only one program running and the OS has tasks it must do too.
Q: How do I update the information in QB64's help system?
A: The help provided in the QB64 IDE Help System fetches the pages from this wiki. Use the Update current page in the IDE Help menu selection to update a page. Use the Update all pages choice to update them all, but this may take longer.
Q: Can I use the same libraries with QB64 that I used with QB 4.5?
A: If the libraries are pure QB 4.5 code then yes, otherwise no. QLB files are not supported but you can easily copy your favorite SUBs or FUNCTIONs to a text BI file and $INCLUDE them at the end of any program. Include them after all SUB and FUNCTION code in the BAS file.
DECLARE LIBRARY allows users to reference C, Windows, OpenGL and other DLL libraries. If you find some functions that you like please share them with us at the forum! The following pages list working functions our members have found and tested:
Q: I can't get my QB 4.5 source code to work in QB64! Why?
A: QB64 is 99% compatible with QB4.5 programs. The commands that haven't been implemented are either obsolete or are too obscure and have been replaced by modern functionality.
See: Keywords currently not supported by QB64
Q: What files are required to run my QB64 compiled program in my Operating System?
A: Programs compiled by QB64(PE) (version 1.000 and up) are stand-alone, so no external files are required to be with your program's EXE file. However, if your program requires additional assets, such as level graphics or sound effects for games, then you need to provide these assets unless you used the $EMBED metacommand to incorporate those directly into the compiled EXE.
Q: Is the QB64 IDE capable to open multiple files?
A: No, the IDE does not support the opening or retrieval of more than one file at a time, but multiple instances of the IDE can be used simultaneously.
Q: Is there a way to use QB64 from the command line?
A: Yes! Just type QB64pe -? at the command prompt to see a list of available options. The following overview shows options available since QB64-PE v3.14.0 and up.
- Note
- The -c and -x options do not load the given BAS source file into the IDE for editing but just compile the program (without automatically running it after compilation). The default output name can be overwritten with the -o option.
- The -y option can be used to format the given source file without using the IDE. Formatting is done according to the current IDE formatting settings or temporary overrides given with the -f option. The -o option is mandatory to specify the name for the (re)formatted source output file, no executable file will be generated.
- The -z option does not open the IDE and does not create an executable file, it performs the first compile pass only (syntax checking and generate C code), so it can be used to scan your program for errors.
Usage: qb64pe [switches] <file>
Options:
<file> Source file to load
-v Print version
-c Compile instead of edit
-o <output file> Write output executable to <output file>
-x Compile instead of edit and output the result to the
console
-w Show warnings
-q Quiet mode (does not inhibit warnings or errors)
-m Do not colorize compiler output (monochrome mode)
-e Enable OPTION _EXPLICIT, making variable declaration
mandatory (per-compilation; doesn't affect the
source file or global settings)
-s[:switch=true/false] View/edit compiler settings
-l:<line number> Start the IDE at the specified line number
-p Purge all pre-compiled content first
-y Output formatted source file
-z Generate C code without compiling to executable
-f[:setting=value] compiler settings to use
Note: Defaults can be changed by IDE settings
Valid switches:
-s Show the current state of all switches
-s:DebugInfo=[true|false] Embed C++ debug info into .EXE
-s:ExeWithSource=[true|false] Save .EXE in the source folder
Valid settings:
-f Print this list of available settings
-f:OptimizeCppProgram=[true|false] Use C++ Optimization flag, default false
-f:StripDebugSymbols=[true|false] Strip C++ debug symbols, default true
-f:ExtraCppFlags=[string] Extra flags to pass to the C++ compiler
-f:ExtraLinkerFlags=[string] Extra flags to pass at link time
-f:MaxCompilerProcesses=[integer] Max C++ compiler processes to start in parallel
-f:GenerateLicenseFile=[true|false] Produce a license.txt file for the program
-f:AutoLayout=[true|false] Toggle code spacing and capitalisation
-f:KeywordCapitals=[true|false] Toggle formatting keywords in ALL CAPITALS
-f:AutoIndent=[true|false] Toggle code indentation
-f:AutoIndentSize=[integer] Spaces per indent level
-f:IndentSubs=[true|false] Toggle indenting SUBs & FUNCTIONs
|
Q: How do I link modules or include SUB procedures in QB64?
A: QB64 allows you to $INCLUDE code or BAS modules into one module when it is compiled. Text .BI files containing SUB or FUNCTION code or entire BAS modules can be included in one module that will be compiled.
After the EXE is compiled, you do not have to even use the added code anymore. The EXE will contain ALL of the program code as ONE stand-alone program. This also allows you to add SUB code to any program that you desire.
See: $INCLUDE
Q: Some screens look small. Can I enlarge them or make them fullscreen?
- You can use the _FULLSCREEN statement to make your programs run fullscreen.
- $RESIZE can be added to a program so you can track window resize events.
- You can also create custom sized screens with page flipping and up to 32 bit colors using _NEWIMAGE.
- Page flipping is available in most screens and the new _DISPLAY feature allows the images to be displayed when YOU desire.
- Picture or image files such as BMP, PNG, JPEG and GIF are EASY to load using _LOADIMAGE.
- Once images are loaded, all you have to do is use the image handle with any of the new statements and functions.
- _PUTIMAGE GETs and PUTs images fast in ONE call. It can even stretch or compress the image sizes.
Q: Can I have background music as well as SOUND, PLAY and BEEP?
A: Yes, they are emulated to use the soundcard.
There also are a bunch of new sound capabilities that allow the use of WAV, OGG, MP3 files and more.
Capabilities include:
- Multiple sound tracks
- Volume and speaker control
- Background music
Get started with music:
- _SNDCLOSE (statement), _SNDCOPY (function), _SNDGETPOS (function), _SNDLEN (function), _SNDLIMIT (statement)
- _SNDLOOP (statement), _SNDOPEN (function), _SNDPAUSE (statement), _SNDPAUSED (function), _SNDPLAY (statement)
- _SNDPLAYCOPY (statement), _SNDPLAYFILE (statement), _SNDPLAYING (function), _SNDSETPOS (statement)
Q: If QB64 creates Basic programs why is there no Immediate Window?
A: Because there is no QB64 interpreter. All C code has to be compiled before it can be run.
QB64 uses the Immediate window area to suggest syntax for keyword entries and give the compiler status when compiling.
Q: Does it work on Windows 98 or any OS older than Windows 2000?
A: No, it doesn't. QB64 is made to run on new systems (Windows 7 and newer, Linux and macOS Catalina and newer).
Q: Does QB64 support CURRENCY values from PDS or VB programs?
A: Not directly, but _FLOAT currency values up to 4 decimal places can be multiplied by 10000(10 ^ 4) and converted to MKC$ string values using _MK$ with an _INTEGER64 value. _CV with an _INTEGER64 value divided by 10000 converts it back to _FLOAT values.
PUT can write a PDS or VB, 8 byte currency string by multiplying the currency amount by 10000 and using an _INTEGER64 variable.
GET can read a _FLOAT CURRENCY value as an INTEGER64 variable value divided by 10000.
Q: Do you provide changelogs?
A: We do, you can lookup the latest changes in the release notes of every new release at GitHub
Q: Where I can view the C++ code of my compiled program?
A: Look in the QB64 internal\temp folder for main.txt to see the C code used to compile the latest program.