Hi Fellippe,

I just bought the professional release 16.1 of Zorin OS 64 bit and of course  immediately installed both QB64 2.0.2 and InForm 1.3 but unfortunately, like with ElementaryOS ofmy previous post, QB64 runs fine but InForm does not work, with the same behavior than with Elementary, then just expecting for a long time the "HandChecking" to be established, then after almost 2 minutes, saying "Inform is not running. Please run the main program" when the main InFormWindows still is displayed.

My last test was made on a baremetal hardware, but I get the similar problem with VMs using VMware Fusion onmy iMac 27.

Please, can you check if you still support InForm?

Kind regards.
Fifi

PS: like Elementary, Zorin is an Unbuntu 20.04 LTS derivative.

Hello everyone,

I updated my multi-language bash install script (rev #35 English, French, German, Italian, Russian and Portuguese) now located on my own server.

It installs (and uninstalls) both QB64 v 2.0.2 (which includes vWatch) and InForm v 1.3 together with a few mouse clicks.

This installation also allows to use the QB64 compiler from any terminal session like any other standard compiler (i.e. gcc, g++, etc) without having to be launched from the directory where QB64 is installed by the following simple command line:


Same for InForm.

As an option, you can have icons placed directly on your desktop without having to go through the programming menu to launch QB64 or InForm and to directly access the QB64 directory.

In addition to the many supported Linux distributions, special thanks to doppler it is supposed to work for Raspbian on Pi as well.

The new location is at: http://www.l7d.ddns.net (or 86.248.12.125).

Thank you in advance for your feedback and your suggestions to improve it further.

Cheers.
Fifi

Hello Fellippe.

I wanted to get the latest build to confirm a bug but the title of this post describes a first issue itself. :(

Hope this helps.

Cheers.
Fifi

PS: So, I'll report the bug in a second message.

Hello all.

To date, the Raspberry Pi has sold over 50 million units worldwide and is now available with a 64 bit quad core CPU and an OS directly derived from Debian Linux for well under $ 100.00.

Please do me the favor and take a few minutes to read the Foundation's 2020 Annual Report: https://static.raspberrypi.org/files/about/RaspberryPiFoundationReview2020.pdf

Then, please answer these two simple questions:

1) Given the Raspberry Pi's obvious target, which is education, should QB64, InForm and vWATCH64 remain inaccessible to this environment for a long time and give way to Microsoft or Google once again?

2) What should be done to make these three great and amazing development tools available for this platform?

And I do not think that the price of the acquisition for example of a Pi400 which is just ready to use is a real obstacle for any developper.

Looking forward.

Cheers.
Fifi

PS: a partnership with the fundation is even possible and if needed, due to my background, I may help to create and manage it.

Hello the QB64 Team,

I'm trying to help doppler to install QB64 smoothly on his Pi using my multi lingual installation script.

His main problem is the use of the floating point that does'nt work (fails on the compil of libqb).

As of July 31, 2019 Jack posted: https://www.qb64.org/forum/index.php?topic=1550.msg107663#msg107663

Did you edit the file common.h and add #define QB64_NOT_X86

Since I'm not a C++ developper, can someone please help me and tell where exactly to add this "#define QB64_NOT_X86" declaration in the common.h file (at the top, at the end, somewhere else)?

Then, I'll be able to modify my multi lingual installation script to make it run on a Pi by checking the machine and the OS used then providing a modified common.h (e.g. common.raspbian) file just for this specific purpose.

Now, a better solution would be later to modify the common.h file with a define block keyed on for exemple "QB64_RASPBIAN" so that the statement "#define QB64_NOT_X86" would only get included as required.

But for now, my proposed work arround (two use a specific common.h file) would be enough to make tests. 

TIA.

Kind regards.
Fifi

Hello Fellippe,

Without going into the details of the internal InForm (because I do not have the skills), can I know if you generate the .bas source at the same time as we create a form or is this only when we save the form?

Depending on your answer, I may have a suggestion for you.

Best regards.

Hi everyone,

Thanks to several contributors, including without limitation to Fellippe Heitor and TempodiBasic for their post translations, revision # 31 of my multilingual ( English, French, German, Italian, Portuguese and Russian ) is now available and install (and nicely uninstall) QB64 version 1.5, InForm version 1.2 and vWATCH64 version 1.102 o, Linux boxes (bare metal and / or VM).

This script also supports the InForm issue of not showing the initial form of UiEditorPreview on some distributions such as Mint 20.1 or Debian 8 & 9.

Additionally, if you chose it, the script creates handy starters with their relevant icons right on your desktop as well as a link to the QB64 folder (/opt/qb64):

  [ You are not allowed to view this attachment ]  

Furthermore, the script allows you to call QB64 from any window even if you are not in the folder where QB64 is installed, and the compiler then behaves like any other compiler (GCC, G++, etc.) when using the -x and -o options.

Exemple from any window (no need anymore of the ./qb64 command within the QB64 folder).:


  [ You are not allowed to view this attachment ]  

As usual, you can get my script from my dedicated web page: http://www.as2.com

Please feel free to come back to me for your comment and suggestions.

Cheers.
Fifi

Hello folks.

I've been away for a while but... I'm back :)

Bad news: QB64 v 1.4 Stable Release From Git 0f49b2c for Linux doesn't compile anymore vWATCH64 (from Fellippe Heitor).

http://www.as2.com/qb64/pictures/qb64-1.4.png

The problem is the compiler (not the app) since the previous release (QB64 v 1.3) compiles vWATCH64 like a charm.

http://www.as2.com/qb64/pictures/qb64-1.3.png

Tests made on a VM with VMware running Linux Mint 20.1 Cinnamon (or Mate, or Xfce).

BTW, same problem on Ubuntu (18.04.5 and 20.2).

Below is the content of compilelog.txt file.

In file included from ../../src/hrtf.c:47:
../../src/hrtf_tables.inc:493:68: error: invalid suffix "$8" on integer constant
  493 |         { +6696, +8017, +1498, +2006, +2624, -2005, -1798, +3417, +7$8, -2614, -432, +706, +173, -173, +53, -56, -573, -718, +132, -67, -717, -164, -301, -196, -38, -159, -197, -465, -469, -327, -185, -358, },
      |                                                                    ^~~
../../src/hrtf_tables.inc:495:35: error: expected ‘}’ before ‘!’ token
  495 |         { +7032, +9112, +2294, +13!9, +2928, -1295, -2725, +3058, +1141, -2349, -736, +409, +218, -319, +37, -5, -474, -896, -105, +108, -719, -327, -414, -210, -8, -342, -280, -290, -610, -529, -264, -398, },
      |         ~                         ^
ar: temp/hrtf.o: No such file or directory
g++: error: parts/audio/out/os/lnx/src.a: No such file or directory

Hope this helps to fix QB64.

Cheers.