QB64x64 (12-22-2018)

[SMcNeill]

Updated the 64-bit version to include all the latest changes and enhancements to QB64.
Also swapped out the old c-compiler from 2014 for the latest version (v8.10, I believe.)
Did a little tinkering under the hood so both halves will play nicely together.

Feel free to grab a copy from here: DEBUGGING — GRAB NEWEST VERSION FROM “BEST ANSWER”

And most important:  MERRY CHRISTMAS!!

[bplus]

Thanks Steve, Merry Christmas to you as well!

[RhoSigma]

Well Steve, thanks for your efforts, but it seems to me that whatever you did in QB64 itself or maybe just the new compiler did broke regular and box line drawing. I noticed it by trying my latest GuiTools release (GuiAppDemo-GL.bas) with your new x64 version, and all object frames as well as rulers are either completely gone or drawn very pixelized. However, a quickly written test program shows that box fill drawing is not affected.

Will now test your x32 version with the new compiler...

[SMcNeill]

Do you have a sample of the broken code to test?  I’ll dig into it and see what’s going on.

EDIT:

LINE (100,100)-(200,200), color, BF — works.


LINE (100,100)-(200,200), color, B — doesn’t.  I’ll dig into it later and see why it doesn’t want to work as advertised with the newest compiler version.  Probably a simple syntax change somewhere.

[bplus]

Yes, I am getting a number of odd things. The download file wouldn't complete when I exited browser even though at 100% on display. Then Antimalware ran and ran activating fan. Then I couldn't delete the 7z file with 0 bytes in it for some time. When fan finally settled down and 7z deleted, I tested graphics programs and backgrounds weren't clearing. And you know about lines not working..

The IDE is red lining this line which is fine in previous version:
CONST polyAngle = pi / 6  'pi was dim shared = _PI

[FellippeHeitor]

Can't mix variables with CONST. Sure that was working before?

[SMcNeill]

Yes, I am getting a number of odd things. The download file wouldn't complete when I exited browser even though at 100% on display. Then Antimalware ran and ran activating fan. Then I couldn't delete the 7z file with 0 bytes in it for some time. When fan finally settled down and 7z deleted, I tested graphics programs and backgrounds weren't clearing. And you know about lines not working..

The IDE is red lining this line which is fine in previous version:
CONST polyAngle = pi / 6  'pi was dim shared = _PI

CONST polyAngle = _PI / 6 should work, but it's definitely not going to work with a shared variable with your CONST.

The glitch with lines and boxes has been corrected.

Can you share a program where the background isn't clearing?  I'll dig into it.

[bplus]

Can't mix variables with CONST. Sure that was working before?

No not anymore, when I added an ' to <<<<<<<<<<<<<<<<<<< to point to it, it red lined!!!

but before the comment, I was looking at OK in older QB64 X 64 IDE (see screen shot). This is not a big concern but still...

[bplus]

Can you share a program where the background isn't clearing?  I'll dig into it.

The background was drawn with Line, when I added , , BF to line the background "clearing" problem was fixed as it went from drawing nothing to coloring fill sections. So if you have that fixed then we should be good.

[bplus]

OH Steve, if you are going to repost update, can you provide more info in the Help > About window X64 (as Fifi suggested) and date.

[FellippeHeitor]

It's a puzzling screenshot. It's also irreproducible at my machine. CONST never accepts a variable.

[SMcNeill]

Give this version a shot, guys.  See if all isn't working as intended:

https://www.dropbox.com/s/56a267uav7cub9d/QB64x64%20%2812-22-2018%29.7z?dl=1

This should fix the line bug for us, and if so, I'll update the x32 version with the changes and repost it again in a few.

(Seems like there's always a few little tweaks which are required any time the compiler is swapped out for a replacement.  Let's hope this is all we need to get current, this time.  ;) )

[Qwerkey]

Mine also crashed inside a FUNCTION

Code: QB64: [Select]

1. FUNCTION ToHardware& (ImgName$, X1%, Y1%)
2.     TempImg& = _NEWIMAGE(X1%, Y1%, 32)
3.     _PUTIMAGE (0, 0)-(X1% - 1, Y1% - 1), _LOADIMAGE(ImgName$, 32), TempImg&
4.     ToHardware& = _COPYIMAGE(TempImg&, 33)
5.     _FREEIMAGE TempImg&
6. END FUNCTION

at the _PUTIMAGE line.

[SMcNeill]

Can you guys share the full code of whatever crashes, please.  It’s a little difficult to debug from code snippets alone.  It’s much appreciated.  :)

[SMcNeill]

Mine also crashed inside a FUNCTION

Code: QB64: [Select]

1. FUNCTION ToHardware& (ImgName$, X1%, Y1%)
2.     TempImg& = _NEWIMAGE(X1%, Y1%, 32)
3.     _PUTIMAGE (0, 0)-(X1% - 1, Y1% - 1), _LOADIMAGE(ImgName$, 32), TempImg&
4.     ToHardware& = _COPYIMAGE(TempImg&, 33)
5.     _FREEIMAGE TempImg&
6. END FUNCTION

at the _PUTIMAGE line.

* might want to check this for a memory leak as well.  There’s no way to FREEIMAGE the _LOADIMAGE when _PUTIMAGE is done.