QB64 Phoenix Edition v3.6.0 Released!

[a740g]

When you get some time please code a quick example on how to use the new _LOADIMAGE argument. Very curious. Thank you for keeping the changes/fixes coming.

Sorry! I should have linked to the Wiki, it includes more information and has an example at the end: https://qb64phoenix.com/qb64wiki/index.php/LOADIMAGE

In my view this feature is very useful when paired with the HTTP support from v3.5.0, you can download an image file into a String and then pass that String directly to `_LOADIMAGE()` to open it. That lets you avoid having to write the image to a file first.

Ah, ok, I see. One could embed an entire sprite sheet within the code using this technique and then parse the individual sprites without ever having to access a drive.

Yes. And Terry I borrowed one of your example code for Example 3. 
So, now you can embed all sorts of images and sounds that QB64-PE supports and load them directly from memory without having to touch any kind of storage.

[doppler]

OpenGL for Vulcan, or such major upheaval.

What is Vulcan, except a planet in "Star Trek" ?

I could not fathom how to search that one in Google.  Without a deluge of ST references.

https://en.wikipedia.org/wiki/Vulkan

Thanks for the info.  I can see why you switched over to it.

[Kernelpanic]

Runs! Good work, thanks!

[Fifi]

Hi all,
Unfortunately, I have a problem installing QB64PE (latest 3.6.0) on my iMac27 with macOS High Sierra.
Below is the error message:

Code: (Select All)

c++  -w -std=gnu++11 -I./internal/c/libqb/include -I./internal/c/parts/core/src/ -I./internal/c/parts/core/glew/include/ -DDEPENDENCY_SOCKETS -DDEPENDENCY_NO_PRINTER -DDEPENDENCY_ICON -DDEPENDENCY_NO_SCREENIMAGE -DDEPENDENCY_LOADFONT  internal/c/libqb/src/http.cpp -c -o internal/c/libqb/src/http.o
internal/c/libqb/src/http.cpp:9:10: fatal error: 'curl/curl.h' file not found
#include <curl/curl.h>
         ^~~~~~~~~~~~~
1 error generated.
make: *** [internal/c/libqb/src/http.o] Error 1
make: *** Waiting for unfinished jobs....
In file included from internal/c/libqb.cpp:5:
internal/c/parts/core/glew/src/glew.c:7938:9: error: use of undeclared identifier 'glGetMapAttribParameterfvNV'; did you mean
      '__glewGetMapAttribParameterfvNV'?
  r = ((glGetMapAttribParameterfvNV = (PFNGLGETMAPATTRIBPARAMETERFVNVPROC)glewGetProcAddress((const GLubyte*)"glGetMapAt...
        ^~~~~~~~~~~~~~~~~~~~~~~~~~~
        __glewGetMapAttribParameterfvNV
internal/c/parts/core/glew/src/glew.c:2123:36: note: '__glewGetMapAttribParameterfvNV' declared here
PFNGLGETMAPATTRIBPARAMETERFVNVPROC __glewGetMapAttribParameterfvNV = NULL;
                                   ^
1 error generated.
make: *** [internal/c/libqb_make_00010101000000.o] Error 1

Compilation of QB64-PE failed!

Any idea to fix that?
Cheers.
Fifi

[mnrvovrfc]

Oh dear again! I wanted Fifi to be happy with this.

https://qb64phoenix.com/forum/showthread.php?tid=1388

[DSMan195276]

Hi all,
Unfortunately, I have a problem installing QB64PE (latest 3.6.0) on my iMac27 with macOS High Sierra.
Below is the error message:

Code: (Select All)

c++  -w -std=gnu++11 -I./internal/c/libqb/include -I./internal/c/parts/core/src/ -I./internal/c/parts/core/glew/include/ -DDEPENDENCY_SOCKETS -DDEPENDENCY_NO_PRINTER -DDEPENDENCY_ICON -DDEPENDENCY_NO_SCREENIMAGE -DDEPENDENCY_LOADFONT  internal/c/libqb/src/http.cpp -c -o internal/c/libqb/src/http.o
internal/c/libqb/src/http.cpp:9:10: fatal error: 'curl/curl.h' file not found
#include <curl/curl.h>
         ^~~~~~~~~~~~~
1 error generated.
make: *** [internal/c/libqb/src/http.o] Error 1
make: *** Waiting for unfinished jobs....
In file included from internal/c/libqb.cpp:5:
internal/c/parts/core/glew/src/glew.c:7938:9: error: use of undeclared identifier 'glGetMapAttribParameterfvNV'; did you mean
      '__glewGetMapAttribParameterfvNV'?
  r = ((glGetMapAttribParameterfvNV = (PFNGLGETMAPATTRIBPARAMETERFVNVPROC)glewGetProcAddress((const GLubyte*)"glGetMapAt...
        ^~~~~~~~~~~~~~~~~~~~~~~~~~~
        __glewGetMapAttribParameterfvNV
internal/c/parts/core/glew/src/glew.c:2123:36: note: '__glewGetMapAttribParameterfvNV' declared here
PFNGLGETMAPATTRIBPARAMETERFVNVPROC __glewGetMapAttribParameterfvNV = NULL;
                                   ^
1 error generated.
make: *** [internal/c/libqb_make_00010101000000.o] Error 1

Compilation of QB64-PE failed!

Any idea to fix that?
Cheers.
Fifi

Any idea if you might have changed something since last attempting to compile 3.5.0? The compiler was able to find `curl/curl.h` when you ran into the other problems. Additionally that GL error is not something we have changed. I'm wondering if maybe your XCode version got downgraded, or something along those lines?

[Kernelpanic]

I have noticed something now: I had ever pointed out the "gap" below in the IDE on the screen, nothing earth shattering, but it suddenly disappeared under 3.5. Now it is back. Welcome back! 

I know something like this from the Windows updates.

[bplus]

I have noticed something now: I had ever pointed out the "gap" below in the IDE on the screen, nothing earth shattering, but it suddenly disappeared under 3.5. Now it is back. Welcome back! 

I know something like this from the Windows updates.

It usually appears when Window is maximized and disappears when not.

Max Not
   

Maxed
   

[mnrvovrfc]

LOL that's what happens when the authors of WIndows10 intended to replace all title bars from the past with that plastic strip. They didn't succeed in a few programs I used, they remained with the title bars from Vista. Also some old 32-bit programs using the open file requester at its minimum, before it grew up to be a bloatware case (such as saved URI's, "Favorites" and "Libraries") refuse to be reskinned but those programs now are rare.

Linux has a similar problem with some people terminally insisting in running junk done with clunky GTK2, FLTK and other GUI toolkits not much simpler to program than Qt which seems to be everywhere now. (KDE Plasma and LXQt desktop environments especially.)

[Kernelpanic]

@bplus & @mnrvovrfc, I don't know if you mean the same thing now.
The bug first appeared on 3.4.1, then on 3.5.0, and suddenly disappeared a few weeks before 3.6.0. With 3.6.0 it was there again.