Thread Rating:
  • 0 Vote(s) - 0 Average
  • 1
  • 2
  • 3
  • 4
  • 5
QB64 and QB64PE together?
#1
Hi All

It's been a while since I had time to do anything with QB64. I've been bogged down with work Dodgy I'm still using QB64 v2.1build 9f81ba1.  Can I have Phoenix and QB64 installed on the same PC without any conflicts? Is there a list of differences between QB64 and the current edition of Phoenix? Will all QB64 progs run on Phoenix?
Oh look. A sig line :-)
Reply
#2
(02-15-2025, 03:07 PM)Mad Axeman Wrote: Hi All
It's been a while since I had time to do anything with QB64. I've been bogged down with work Dodgy I'm still using QB64 v2.1build 9f81ba1.  Can I have Phoenix and QB64 installed on the same PC without any conflicts? Is there a list of differences between QB64 and the current edition of Phoenix? Will all QB64 progs run on Phoenix?
Of course you can! Both versions are self-contained, so to speak.

Example:
Install both under Programs, and then put a link to the exe file on the desktop. Now you can call up both as you wish.
Reply
#3
(02-15-2025, 03:07 PM)Mad Axeman Wrote: Hi All

It's been a while since I had time to do anything with QB64. I've been bogged down with work Dodgy I'm still using QB64 v2.1build 9f81ba1.  Can I have Phoenix and QB64 installed on the same PC without any conflicts? Is there a list of differences between QB64 and the current edition of Phoenix? Will all QB64 progs run on Phoenix?

You can easily have as many different QB64(pe) versions installed as you want, just make sure every version sits in its own base folder, don't mix them in one folder, that would scream for trouble.

Ex.
- download and extract v2.0 you get a folder "qb64", rename it to "qb64_v2"
- download and extract Phoenix v3.0.0 you get a folder "qb64pe", rename it to "qb64_v3" or "qb64pe_v3"
- download and extract Phoenix v4.0.0 you get a folder "qb64pe", rename it to "qb64_v4" or "qb64pe_v4"
and so on, no problems if each version is seperate.

You can even run all versions at the same time, as the different processes all work seperately in its respective base folders.

an overview of all Phoenix versions is here.
Reply
#4
(02-15-2025, 03:07 PM)Mad Axeman Wrote: Hi All

It's been a while since I had time to do anything with QB64. I've been bogged down with work Dodgy I'm still using QB64 v2.1build 9f81ba1.  Can I have Phoenix and QB64 installed on the same PC without any conflicts? Is there a list of differences between QB64 and the current edition of Phoenix? Will all QB64 progs run on Phoenix?

QB64, QB64 Official, and QB64PE are all based off the same initial source code.  When Team QB64 was shut down, the project branched off into multiple directions, but all were based off that same initial core.  Since then, we've worked on expanding things, optimizing things, adding new things, and fixing things, but we've tried hard not to BREAK anything.

All the old code you have *should* work with the newest version of QB64PE.  If not, post it and we'll either fix whatever we broke, or explain what broke it and how to work around it to correct the issue.  Wink

Note however, that code written in QB64PE is *not* guaranteed to work in older versions of QB64.  We've moved on, added new commands, swapped in new libraries.  While you can load a whole array of image types in QB64PE, you'd be limited to only a handful in those older versions of QB64 and QB64 Official.  Same with sound and other various improvements like the file open/save dialogs, messagebox, and other such innovations.

We *should* run everything old, but that doesn't mean everything old can run all our *new* stuff.  (Just something to keep in mind.)



Note that when installing multiple versions, you want to keep each version in their own separate folder.  You can't install them both in the same folder and expect things to go properly.  

For example, make a C:\QB64 folder and put all your QB64 stuff there, and make a C:\QB64PE folder and put all the QB64PE stuff there.  Don't try to mix them both in the same folder as we've swapped out the c-compiler and everything else over time to try and produce a better product for everyone to use.   

That said:  Welcome back.  Nice to see you around once again.  Wink
Reply
#5
Thanks all. I'm not looking at backwards compatability, just to swap over to this version seeing as it's being activley developed. I'm just off to download and see what I can break Big Grin
Oh look. A sig line :-)
Reply
#6
Well, it seems to compile everything I've thrown at it so far. It's creating slightly larger EXE files but I assume that's due to extra code in the libraries due to the extra commands available etc. ?
All I need now is a library to create PDF files.
Oh look. A sig line :-)
Reply
#7
(02-16-2025, 06:08 PM)Mad Axeman Wrote: Well, it seems to compile everything I've thrown at it so far. It's creating slightly larger EXE files but I assume that's due to extra code in the libraries due to the extra commands available etc. ?
All I need now is a library to create PDF files.

I had made code before that allowed creation of PDFs but I don't think it is compatible anymore.
The noticing will continue
Reply
#8
Any chance of a copy? It might give me some pointers in the right direction.
Oh look. A sig line :-)
Reply




Users browsing this thread: 2 Guest(s)