QB64 Phoenix Edition v3.6.0 Released! - Printable Version +- QB64 Phoenix Edition (https://staging.qb64phoenix.com) +-- Forum: Official Links (https://staging.qb64phoenix.com/forumdisplay.php?fid=16) +--- Forum: Announcements (https://staging.qb64phoenix.com/forumdisplay.php?fid=18) +--- Thread: QB64 Phoenix Edition v3.6.0 Released! (/showthread.php?tid=1488) |
RE: QB64 Phoenix Edition v3.6.0 Released! - a740g - 02-20-2023 (02-20-2023, 05:07 PM)TerryRitchie Wrote:(02-20-2023, 06:07 AM)DSMan195276 Wrote:(02-20-2023, 05:47 AM)TerryRitchie Wrote: 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. 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. RE: QB64 Phoenix Edition v3.6.0 Released! - doppler - 02-20-2023 (02-20-2023, 05:17 PM)SMcNeill Wrote:(02-20-2023, 04:19 PM)doppler Wrote:(02-20-2023, 07:54 AM)SMcNeill Wrote: OpenGL for Vulcan, or such major upheaval. Thanks for the info. I can see why you switched over to it. RE: QB64 Phoenix Edition v3.6.0 Released! - Kernelpanic - 02-21-2023 Runs! Good work, thanks! RE: QB64 Phoenix Edition v3.6.0 Released! - Fifi - 02-25-2023 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 Cheers. Fifi RE: QB64 Phoenix Edition v3.6.0 Released! - mnrvovrfc - 02-25-2023 Oh dear again! I wanted Fifi to be happy with this. https://staging.qb64phoenix.com/showthread.php?tid=1388 RE: QB64 Phoenix Edition v3.6.0 Released! - DSMan195276 - 02-25-2023 (02-25-2023, 12:10 PM)Fifi Wrote: Hi all, Any idea if you might have changed something since last attempting to compile 3.5.0? The compiler was able to find curl/curl.hwhen 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? RE: QB64 Phoenix Edition v3.6.0 Released! - Kernelpanic - 02-26-2023 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. RE: QB64 Phoenix Edition v3.6.0 Released! - bplus - 02-26-2023 (02-26-2023, 10:33 PM)Kernelpanic Wrote: 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! It usually appears when Window is maximized and disappears when not. Max Not Maxed RE: QB64 Phoenix Edition v3.6.0 Released! - mnrvovrfc - 02-27-2023 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.) RE: QB64 Phoenix Edition v3.6.0 Released! - Kernelpanic - 02-27-2023 @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. |