QB64pe version 3.0 released!

[SMcNeill]

@SMcNeill,

maybe you should add a permanent redirect link on the "Official links" board to point to the latest release:

h t t p s://github.com/QB64-Phoenix-Edition/QB64pe/releases/latest

Note I've added spaces to the http part to avoid the forum software mangles it into a clickable link.

I've the same link on the Wiki main page.

How's the above look for you?  Latest Release is now a quick link topic available via one click from the main board. 

[RhoSigma]

That's it

[Coolman]

Am I the only person who gets a minicule console screen for output, with no apparent means to increase its size.

if version 0.8.2 works well. copy the file :

../internal/config.ini

in version 3.0.0 at the same location. Make a backup of the file config.ini.

[Coolman]

Some key differences: https://github.com/QB64-Phoenix-Edition/...COPYING.md <-- you'll no longer have to worry over LGPL License restrictions when making a program with sound in it. That was the old audio library that was being used -- the new one is MIT Licensed.

SMcNeill. you are in the right direction. the user license is often a brake to creativity and many developers avoid restrictive licenses. your judicious choice of the MIT license will surely attract many talents...

[RNBW]

Am I the only person who gets a minicule console screen for output, with no apparent means to increase its size.

if version 0.8.2 works well. copy the file :

../internal/config.ini

in version 3.0.0 at the same location. Make a backup of the file config.ini.

@Coolman
Tried that.  Surprisingly the IDE for QB64PE 3 reduced in size, but the output screen remained the same small size.

@SMcNeill
My config file for QB64PE V3 (I forgot to give you it)

Code: (Select All)

[GENERAL SETTINGS]
DisableSyntaxHighlighter=False
PasteCursorAtEnd=True
ExeToSourceFolderFirstTimeMsg=True
WhiteListQB64FirstTimeMsg=True
SaveExeWithSource=False
EnableQuickNav=True
ShowErrorsImmediately=True
ShowLineNumbers=True
ShowLineNumbersSeparator=True
ShowLineNumbersUseBG=True
BracketHighlight=True
KeywordHighlight=False
MultiHighlight=True
IgnoreWarnings=False
BackupSize=100 'in MB
DebugInfo=False
WikiBaseAddress=https://qb64phoenix.com/qb64wiki

[MOUSE SETTINGS]
SwapMouseButton=False

[DEBUG SETTINGS]
BaseTCPPort=9000
WatchListToConsole=False
AutoAddDebugCommand=True

[IDE DISPLAY SETTINGS]
IDE_SortSUBs=False
IDE_KeywordCapital=True
IDE_SUBsLength=True
IDE_AutoPosition=True
IDE_NormalCursorStart=6
IDE_NormalCursorEnd=8
IDE_AutoFormat=True
IDE_AutoIndent=True
IDE_IndentSUBs=True
IDE_IndentSize=3
IDE_CustomFont=True
IDE_UseFont8=False
IDE_CustomFont$=C:\Windows\Fonts\lucon.ttf
IDE_CustomFontSize=21

[CUSTOM DICTIONARIES]
Instructions1="Add custom keywords separated by the 'at' sign."
Instructions2="Useful to colorize constants (eg @true@false@)."
CustomKeywords$=@

[IDE COLOR SCHEMES]
Instructions1="Create custom color schemes in the IDE (Options->IDE Colors)."
Instructions2="Custom color schemes will be stored in this section."
Scheme1$=User-defined|000000000255147157206010255206000000206098088128186118255255255245245245000147177170170170

[IDE WINDOW 1]
IDE_Width=80
IDE_Height=30
IDE_TopPosition=2
IDE_LeftPosition=858

[IDE COLOR SETTINGS 1]
SchemeID=11
TextColor=_RGB32(0, 0, 0)
KeywordColor=_RGB32(255, 147, 157)
NumbersColor=_RGB32(206, 10, 255)
QuoteColor=_RGB32(206, 0, 0)
CommentColor=_RGB32(128, 186, 118)
ChromaColor=_RGB32(170, 170, 170)
MetaCommandColor=_RGB32(206, 98, 88)
HighlightColor=_RGB32(0, 147, 177)
BackgroundColor=_RGB32(255, 255, 255)
BackgroundColor2=_RGB32(245, 245, 245)

[COMPILER SETTINGS]
OptimizeCppProgram=False
StripDebugSymbols=True
MaxParallelProcesses=3
ExtraCppFlags=
ExtraLinkerFlags=

[james2464]

Question...I'm still only a couple of months using qb64 and I just checked, I have version 2.02. It says "stable" version. Should I upgrade to 3.0 or is that more important for advanced users?

[OldMoses]

Question...I'm still only a couple of months using qb64 and I just checked, I have version 2.02.  It says "stable" version.  Should I upgrade to 3.0 or is that more important for advanced users?

I was using a previous version (2.1 beta) until very recently, when I finally switched to using mostly PE version 0.8.2. I would say it's a matter of personal preference. I've had no problems with what I've been doing and haven't downloaded 3.0 yet, either, but I'll get around to it soon.

[SMcNeill]

Question...I'm still only a couple of months using qb64 and I just checked, I have version 2.02.  It says "stable" version.  Should I upgrade to 3.0 or is that more important for advanced users?

3.0 does everything that 2.0.2 does, but it's got several improvements and fixes in it.  Some, I'd consider almost vital for use, such as fixing the Help so you can download wiki pages without freezing up and locking up the IDE.

That said, at this point in time, I'd wait until the weekend to grab the *next* version which we're currently working on.  I think we're going to try and swap over to a weekly release schedule now that we've got things more-or-less in working order, and the next release will have the fix for the DPI Awareness glitch as RNBW mentioned above, along with several other new additions and changes which I think you guys will all enjoy seeing pushed into the language. 

[james2464]

Awesome, I'll stay up to date on this thread in the meantime. Thank you.

[Coolman]

there is a bug. in the compilelog.txt file, I find the two options -O3 and -O2 while I checked Compile programm with C++ optimization flag and specified -O3...

g++ -O3 -O2 -w -std=gnu++11 -DFREEGLUT_STATIC...