Text Only | Text with Attachments

QB64.org Forum

Active Forums => QB64 Discussion => Topic started by: odin on June 29, 2018, 12:49:52 pm

Title: Follow the development of QB64 v1.3
Post by: odin on June 29, 2018, 12:49:52 pm
Hi everyone,

The latest stable release of QB64 is version 1.2. It was built from the master branch of the repository and is the version you can fetch from www.qb64.org ([abandoned, outdated and now likely malicious qb64 dot net website - don’t go there] is a bit behind even on the stable release).

We also have a development branch being worked on and you can always help us beta test it by downloading the Development release at www.qb64.org. The version currently available will eventually become the next stable release, and as the homepage says, "If you're adventurous, we encourage you to help us find bugs!"

To follow what's being done, check the commit history in the development branch at https://github.com/Galleondragon/qb64/commits/development (https://github.com/Galleondragon/qb64/commits/development)

QB64 is a collaborative effort based on the amazing and extensive work Galleon did by creating QB64 and developing it up to version 1.000.

We truly hope you enjoy using it as much as we enjoy working on it.

The team.
Title: Re: Follow the development of QB64
Post by: odin on June 29, 2018, 12:58:15 pm
To request a feature or report a bug, use this forum board or, ideally, add a new issue at https://github.com/Galleondragon/qb64/issues (https://github.com/Galleondragon/qb64/issues).

By following the link above you will see the list of currently open issues and you can also see the list of closed issues, so you can know what has already been tackled by the team recently.
Title: Re: Follow the development of QB64
Post by: Petr on June 29, 2018, 03:35:00 pm
Hi Odin. _SNDRAW play not correctly left / right channel. Is not possible set volume to zero for L/R, it something do, but plays both channels always. See attached program. SNDRAW outputs are on lines 638 and 286. You can try also WAV format 8/16 mono/stereo, 11050 to 44100 Hz. Use the bars below the channel volume pointer. Because is not possible send it correctly here, isen it to thread "SNDRAW Player" in Program section.

Title: Re: Follow the development of QB64
Post by: Pete on June 30, 2018, 02:33:58 pm
Nice swap of RUN DETACHED now just needing just an F5 press. I've refrained from making those types of suggestions as it is somewhat picky when other work is being done or requested. Still, it's a really nice change and thanks for making it. I always run QB64 detached and never quite figured out why Rob made the default as attached.

Pete :)

Title: Re: Follow the development of QB64
Post by: FellippeHeitor on July 31, 2018, 12:08:07 am
If you've decided to help beta test the next release of QB64 (likely to be numbered 1.3), here's a list of what to look for so you can help us test the new features and eventually find bugs.

Note: some things got fixed, some of the reported issues are still pending and some new features have been added.

Improvements:
    - Adds Ctrl+Shift+G shortcut to jump to line with error (try the shortcut when your program has an error and the IDE is indicating it on the status area)
    - New Ctrl+T to toggle comments on the current line or selection (also available via Edit menu and by right-clicking the code)
    - Updates NanoJPEG to the version 1.3.5 (try loading different jpg files to see if all works well)
    - Makes F5 run detached by default. (you no longer get an unresponsive IDE while your program is running; equivalent to Ctrl+F5 in older versions).
    - Disables maximize box when $RESIZE isn't enabled. (Windows only -> remember when a non-resizable window would still show Maximize and when you clicked it the window would just move to the top-left corner? That won't happen anymore).
    - Quick Navigation (back arrow) can now be disabled in the Search menu.
    - It is now possible to have variable-length strings in User Defined Types (UDTs).
    - [Windows version] Mingw compiler upgraded to version 8.1.0. A 64-bit package is now available officially.
    - New warnings system indicates when a declared variable isn't used and also when a constant is redefined with the same value - useful for using multiple libraries that define TRUE/FALSE for example (instead of an error stopping compilation, a warning is displayed).

Fixes:
    - Tab in included files won't generate an error anymore.
    - A bug that would cause an include line to be duplicated when resizing the IDE.
    - A bug that would not allow reassigning precompiler $LET variables.
    - A memory leak involving PRINT USING and TAB().
    - _PRINTSTRING not using the passed image handle parameters.
    - Selecting a disabled menu item with a hot key would crash the IDE.

New statements and functions:
    - _ECHO (https://github.com/Galleondragon/qb64/commit/688e31c0f3da4d1f453581dd562437199ce23124): Previously, you could have a $CONSOLE window enabled but to alternate printing to the main program and to the console you'd have to switch _DEST to _CONSOLE, print the text then switch _DEST back to the main program. With the _ECHO command a $CONSOLE-enabled program can output text to the console window without the hassle.

    - _ALLOWFULLSCREEN (https://github.com/Galleondragon/qb64/commit/d911e3d01e47a9159492fe32b16729e4c53f31a7): the statement allows you to set the behavior of the ALT+ENTER combo. You can allow only certain modes or disable the combo altogether.

    - _SMOOTH: returns true (-1) if the current _FULLSCREEN mode has antialiasing enabled or false (0) if disabled.

    - _RGB32: of course this is not a new function but it has been improved greatly. You no longer need to alternate between _RGB32 and _RGBA32 as it now accepts an optional fourth parameter for alpha. Also: You can create a grayscale color without having to repeat parameters. More details at https://github.com/Galleondragon/qb64/commit/6ee70f1afa3d9dd8ded201743c15711d7b79a1eb

    - _INSTRREV (https://github.com/Galleondragon/qb64/commit/bc6b427a994c03a5192766aad0dd6e301575bee6): like INSTR, _INSTRREV allows you to search for a substring inside another string, but unlike INSTR it returns the last occurrence instead of the first one.

    - _TRIM (https://github.com/Galleondragon/qb64/commit/ed28f453f03907f6957a38b8b47c5c353c574f95)$: Single function to remove trailing and leading spaces from a string. Macro for RTRIM$(LTRIM$(text$)).

    - Drag/Drop support (https://github.com/Galleondragon/qb64/commit/c83b15eb95e3655b6c8e8c1f1bba1e8cfb44e09c) (Windows-only): new statements _ACCEPTFILEDROP, _TOTALDROPPEDFILES and _DROPPEDFILE$ allow your program to accept and handle files dropped from a folder at run-time.

    - New _SHL and _SHR functions for bit-shifting (left/right), as in PRINT _SHL(2, 4) (returns 32) and PRINT _SHR(-8, 3) (returns -1).

The list above contains what's new up to development build 358b725 available today, which you can get from www.qb64.org (http://www.qb64.org). Notice that the Help->About dialog will still report an older build number (that will only be updated once development becomes stable), so what really matters is that Help->About shows you From git 358b725.
Title: Re: Follow the development of QB64
Post by: FellippeHeitor on July 31, 2018, 12:39:44 am
_ECHO sample usage:
Code: QB64: [Select]
  2. PRINT "This will be seen in the main program's window"
  3. _ECHO "This will be output to the console"
Title: Re: Follow the development of QB64
Post by: FellippeHeitor on July 31, 2018, 12:41:52 am
_ALLOWFULLSCREEN usage (BTW, _FULLSCREEN now accepts OFF without the underscore):

Code: QB64: [Select]
  1. '_ALLOWFULLSCREEN only affects the behavior of ALT+ENTER.
  2. '
  3. 'Existing _FULLSCREEN statement is not bound by _ALLOWFULLSCREEN's settings.
  4.  
  5. 'default mode:
  6. fsMode$ = "_ALLOWFULLSCREEN not used (or _ALLOWFULLSCREEN _ALL, _ALL or without arguments)"
  7. fsDesc$ = "both stretched and 1:1 modes allowed; both normal and antialised modes allowed."
  8.  
  10.     CLS
  11.  
  12.     LOCATE 7
  13.     COLOR 14: PRINT "_ALLOWFULLSCREEN statement demo": COLOR 7
  14.     PRINT "    - Press 1-8 to change _ALLOWFULLSCREEN mode"
  15.     PRINT "    - Press ALT+ENTER to test"
  16.     PRINT
  17.     COLOR 14: PRINT "Syntax:": COLOR 7
  18.     PRINT "    _ALLOWFULLSCREEN [{_STRETCH|_SQUAREPIXELS|OFF|_ALL}][,{_SMOOTH|OFF|_ALL}]"
  19.  
  20.  
  21.     k& = _KEYHIT
  22.  
  23.     IF k& >= 49 AND k& <= 56 THEN
  24.         _FULLSCREEN OFF
  25.         altEnter = 0
  26.         SELECT CASE CHR$(k&)
  27.             CASE "1"
  28.                 fsMode$ = "_ALLOWFULLSCREEN OFF"
  29.                 fsDesc$ = "full screen mode disabled; alt+enter can be manually trapped."
  30.                 _ALLOWFULLSCREEN OFF
  31.             CASE "2"
  32.                 fsMode$ = "_ALLOWFULLSCREEN _STRETCH, _ALL"
  33.                 fsDesc$ = "stretch mode allowed only; normal+antialiased modes allowed"
  34.                 _ALLOWFULLSCREEN _STRETCH , _ALL
  35.             CASE "3"
  36.                 fsMode$ = "_ALLOWFULLSCREEN _SQUAREPIXELS, _ALL"
  37.                 fsDesc$ = "1:1 mode allowed only; normal+antialiased modes allowed"
  38.                 _ALLOWFULLSCREEN _SQUAREPIXELS , _ALL
  39.             CASE "4"
  40.                 fsMode$ = "_ALLOWFULLSCREEN _STRETCH, OFF"
  41.                 fsDesc$ = "stretch mode allowed only; normal mode allowed only"
  42.                 _ALLOWFULLSCREEN _STRETCH , OFF
  43.             CASE "5"
  44.                 fsMode$ = "_ALLOWFULLSCREEN _SQUAREPIXELS, OFF"
  45.                 fsDesc$ = "1:1 mode allowed only; normal mode allowed only"
  46.                 _ALLOWFULLSCREEN _SQUAREPIXELS , OFF
  47.             CASE "6"
  48.                 fsMode$ = "_ALLOWFULLSCREEN _STRETCH, _SMOOTH"
  49.                 fsDesc$ = "stretch mode allowed only; antialiased mode allowed only"
  50.                 _ALLOWFULLSCREEN _STRETCH , _SMOOTH
  51.             CASE "7"
  52.                 fsMode$ = "_ALLOWFULLSCREEN _SQUAREPIXELS, _SMOOTH"
  53.                 fsDesc$ = "1:1 mode allowed only; antialiased mode allowed only"
  54.                 _ALLOWFULLSCREEN _SQUAREPIXELS , _SMOOTH
  55.             CASE "8"
  56.                 fsMode$ = "_ALLOWFULLSCREEN not used (or _ALLOWFULLSCREEN _ALL, _ALL or without arguments)"
  57.                 fsDesc$ = "both stretched and 1:1 modes allowed; both normal and antialised modes allowed."
  58.                 _ALLOWFULLSCREEN _ALL , _ALL
  59.         END SELECT
  60.     ELSEIF k& = 13 THEN
  61.         IF _KEYDOWN(100307) OR _KEYDOWN(100308) THEN
  62.             altEnter = altEnter + 1
  63.         END IF
  64.     END IF
  65.  
  66.     LOCATE 14
  67.     COLOR 14: PRINT "Current setting:": COLOR 7
  68.     PRINT fsMode$
  69.     COLOR 14: PRINT "Behavior:": COLOR 7
  70.     PRINT fsDesc$
  71.  
  72.     IF altEnter THEN
  73.         LOCATE 18
  74.         PRINT "ALT+ENTER manually trapped"; altEnter; "times."
  75.     END IF
  76.  
  77.     _DISPLAY
  78.     _LIMIT 30
  80.  
Title: Re: Follow the development of QB64
Post by: SMcNeill on July 31, 2018, 12:42:16 am
Are you guys certain that _RGB32 should have that optional 4th parameter for Alpha?  Seems to me that it's just asking for trouble since _RGB has a different, optional 4th parameter for image handle.

Honestly, I think _RGBA32 should work fine enough for most folks, without any possible issues for parameter confusion between such similar named commands.
Title: Re: Follow the development of QB64
Post by: FellippeHeitor on July 31, 2018, 12:43:15 am
Details on the new _RGB32:

Existing syntax:
Code: QB64: [Select]
  1. colour~& = _RGB32(red, green, blue)

New possible uses:
- Instead of passing identical rgb values to achieve a shade of gray, pass only 1 parameter for all color components:

Code: QB64: [Select]
  1.     colour~& = _RGB32(51) 'same as _RGB32(51, 51, 51)

- _RGB32 can now take an optional alpha parameter, which makes _RGBA32 obsolete (although it still exists for retrocompatibility):

Code: QB64: [Select]
  1.     colour~& = _RGB32(255, 0, 255, 30) 'same as _RGBA32(255, 0, 255, 30)

- If you want a shade of gray and also to specify the alpha level, you can pass just two parameters:

Code: QB64: [Select]
  1.     colour~& = _RGB32(51, 30) 'same as _RGBA32(51, 51, 51, 30)

In summary:

    - 1 parameter  = red, green and blue simultaneously set.
    - 2 parameters = red, green and blue simultaneously set plus alpha level.
    - 3 parameters = red, green and blue as usual.
    - 4 parameters = red, green and blue plus alpha level (same as _RGBA32).
Title: Re: Follow the development of QB64
Post by: FellippeHeitor on July 31, 2018, 12:44:06 am
Quote from: SMcNeill on July 31, 2018, 12:42:16 am
Are you guys certain that _RGB32 should have that optional 4th parameter for Alpha?  Seems to me that it's just asking for trouble since _RGB has a different, optional 4th parameter for image handle.

Honestly, I think _RGBA32 should work fine enough for most folks, without any possible issues for parameter confusion between such similar named commands.

All new features of _RGB32 are optional and it can continue to be used as always. _RGBA32 will also continue to exist.
Title: Re: Follow the development of QB64
Post by: FellippeHeitor on July 31, 2018, 12:44:48 am
_INSTRREV:
Code: QB64: [Select]
  1.  fullPath$ = "C:\Documents and Settings\Administrator\Desktop\qb64\internal\c\libqb\os\win\libqb_1_2_000000000000.o"
  2. file$ = MID$(fullPath$, _INSTRREV(fullPath$, "\") + 1)
  3. PRINT file$
Title: Re: Follow the development of QB64
Post by: FellippeHeitor on July 31, 2018, 12:45:40 am
Drag/drop support demo (for Windows only):
Code: QB64: [Select]
  1. SCREEN _NEWIMAGE(128, 25, 0)
  2.  
  4. PRINT "Drag files from a folder and drop them in this window..."
  5.  
  8.         FOR i = 1 TO _TOTALDROPPEDFILES
  9.             a$ = _DROPPEDFILE$
  10.             COLOR 15
  11.             PRINT i,
  12.             IF _FILEEXISTS(a$) THEN
  13.                 COLOR 2: PRINT "file",
  14.             ELSE
  15.                 IF _DIREXISTS(a$) THEN
  16.                     COLOR 3: PRINT "folder",
  17.                 ELSE
  18.                     COLOR 4: PRINT "not found", 'highly unlikely, but who knows?
  19.                 END IF
  20.             END IF
  21.             COLOR 15
  22.             PRINT a$
  23.         NEXT
  24.     END IF
  25.  
  26.     _LIMIT 30
Title: Re: Follow the development of QB64
Post by: FellippeHeitor on July 31, 2018, 09:48:30 am
Latest dev build:

- _DROPPEDFILE can now take an optional index parameter, which goes from 1 TO _TOTALDROPPEDFILES and allows you to read the dropped files list in any order.
- When reading _DROPPEDFILE using an index, instead of sequentially, _TOTALDROPPEDFILES won't get reset until a new drag/drop occurs or until _FINISHDROP is called.

Code: QB64: [Select]
  1. SCREEN _NEWIMAGE(128, 25, 0)
  2.  
  4.  
  6.     PRINT "Drag files from a folder and drop them in this window..."
  7.  
  9.  
  10.     PRINT _TOTALDROPPEDFILES; " files/folders dropped;"
  11.  
  13.         a$ = _DROPPEDFILE(i)
  14.         COLOR 15
  15.         IF _FILEEXISTS(a$) THEN
  16.             COLOR 2: PRINT "file",
  17.         ELSE
  18.             IF _DIREXISTS(a$) THEN
  19.                 COLOR 3: PRINT "folder",
  20.             ELSE
  21.                 COLOR 4: PRINT "not found", 'highly unlikely, but who knows?
  22.             END IF
  23.         END IF
  24.         COLOR 15
  25.         PRINT a$
  26.     NEXT
  28.  
  29.     _LIMIT 30
Title: Re: Follow the development of QB64
Post by: RhoSigma on August 01, 2018, 04:11:28 am
The _DROPPEDFILE keyword works syntax error free with and without "$" sign for both, indexed (array) usage and sequencial usage. Is that by intention? Shouldn't it not require the "$" sign as it is mandatory for eg. the COMMAND$ keyword with and without its indexed usage?
Title: Re: Follow the development of QB64
Post by: FellippeHeitor on August 01, 2018, 07:00:15 am
It accepts the $ sygil in alignment with _CONNECTIONADDRESS, which also works both with and without it. It makes sense in that it returns a string, so it's kind of instinctive for BASIC users like us, but it also works without it cause it belongs to QB64-exclusive keywords.

COMMAND$, on the other hand, although the indexed syntax is not inherited from QuickBASIC, is historically mandatorily followed by $, which is why it only works with it.
Title: Re: Follow the development of QB64
Post by: Ashish on August 01, 2018, 07:24:42 am
The latest build also support multisample antialiasing for OpenGL context [Windows only].
The multisample feature can be trigger on and off with the help of _glEnable and _glDisable by using _GL_MULTISAMPLE.

The link to this commit is here (https://github.com/Galleondragon/qb64/commit/820d6736f7966cb95777c282d6ae3eb1971215ee)

It was achieved by adding one more GLUT_MULTISAMPLE mode to glutInitDisplayMode() of libqb.cpp and by defining the constant in
../gl_header/gl.h

Here's a sample code which demonstrate this -

Code: QB64: [Select]
  1. _TITLE "GL Multisample Testing"
  2. SCREEN _NEWIMAGE(800, 600, 32)
  3.  
  5. _PRINTSTRING (1, 1), "GL_MULTISAMPLE : Enable"
  6. _PRINTSTRING (600, 1), "GL_MULTISAMPLE : Disable"
  7. LINE (400, 0)-(400, _HEIGHT)
  8.  
  10.     _LIMIT 30
  12.  
  13. SUB _GL () STATIC
  14.     IF NOT Init THEN
  15.         Init = -1
  16.         _glViewport 0, 0, _WIDTH, _HEIGHT
  17.     END IF
  18.     _glMatrixMode _GL_MODELVIEW
  20.  
  21.     _glEnable _GL_MULTISAMPLE 'enable the multisample
  22.     _glBegin _GL_LINE_LOOP
  23.     FOR i = 0 TO _PI(2) STEP .1
  24.         _glVertex2f COS(i) * .4 - .5, SIN(i) * .4
  25.     NEXT
  26.     _glEnd
  27.  
  28.     _glDisable _GL_MULTISAMPLE 'disable the multisample, you will se jagged ellipse
  29.     _glBegin _GL_LINE_LOOP
  30.     FOR i = 0 TO _PI(2) STEP .1
  31.         _glVertex2f COS(i) * .4 + .5, SIN(i) * .4
  32.     NEXT
  33.     _glEnd
  34.  
  36.  
Title: Re: Follow the development of QB64
Post by: FellippeHeitor on August 01, 2018, 07:39:18 am
Exactly. On macOS _GL_MULTISAMPLE doesn't need to be enabled as it's on by default.
Title: Re: Follow the development of QB64
Post by: FellippeHeitor on August 01, 2018, 09:14:09 pm
Latest dev build accepts drag/drop for quick loading a file from a folder when the IDE is already running (Windows only).
Title: Re: Follow the development of QB64
Post by: coder on August 17, 2018, 07:26:27 am
You need an ABOUT menu item that shows what version of QB64 I am running.
I haven't messed with QB64 since version 10 and just saw that it now has a VB-like 'modern' UI ability.
So I downloaded and installed qb64_2018-02-12-19-30-35_1d0f920-master_win.7z.

I thought, back in 2016, that I could change the font sizes so that I can see the menu and text easier.
Maybe I modified the program. It would be nice if we could do that without having to modify the source code.
I tried changing the text size and it didn't seem to work. (Windows 10)
Title: Re: Follow the development of QB64
Post by: FellippeHeitor on August 17, 2018, 07:31:30 am
Help -> About

Options -> Display

The modern UI is separate from QB64's core, check it out: qb64.org/inform (http://qb64.org/inform)

Make sure to check the option to use a custom font in the Display dialog and to specify a font that is monospaced. Default suggestion that comes preset is Lucida Console.

Welcome to the forum.
Title: Re: Follow the development of QB64
Post by: FellippeHeitor on September 20, 2018, 11:56:04 am
New dev build available today (from git e490b1a) contains:

Enhancements
(as discussed here (https://www.qb64.org/forum/index.php?topic=577.0)):
    - New Ctrl+T to toggle comment marker (') on the current line or selection (also available via Edit menu and by right-clicking the code)
    - Quick Navigation (back arrow) can now be disabled in the Search menu.

Fixes:
    - Tab in included files won't generate an error anymore. (as discussed here (https://www.qb64.org/forum/index.php?topic=508.msg3591#msg3591))
    - A bug that would cause an include line to be duplicated when resizing the IDE was fixed. (as discussed here (https://www.qb64.org/forum/index.php?topic=238.msg1288#msg1288))
Title: Re: Follow the development of QB64
Post by: Aureal on September 21, 2018, 01:39:14 pm
Pls implement a C++11 compatible compiler :( :( :(
Title: Re: Follow the development of QB64
Post by: Petr on September 22, 2018, 07:32:40 am
I find _SNDRAW bug in new IDE, read here: https://www.qb64.org/forum/index.php?topic=614.msg4813#msg4813
Title: Re: Follow the development of QB64
Post by: FellippeHeitor on September 22, 2018, 09:42:41 am
Thanks for reporting, Petr.
Title: Re: Follow the development of QB64
Post by: Fifi on October 08, 2018, 03:23:09 pm
Quote from: Aureal on September 21, 2018, 01:39:14 pm
Pls implement a C++11 compatible compiler :( :( :(

Why ?

Can't you code in pure ANSI C Vs the cripled C++ ?
Title: Re: Follow the development of QB64 - Memory release problem
Post by: Petr on October 12, 2018, 02:17:06 pm
This source works correctly..... BUT until you take with the mouse program window and start to move it (and do not release the mouse button). Then,  _COPYIMAGE still fills the memory, but  _FREEIMAGE will not release it until you are holding with mouse program window. I think it would be more logical to pause _COPYIMAGE when moving, not just _FREEIMAGE.

Code: QB64: [Select]
  1.  
  2. c = _NEWIMAGE(100, 100, 32)
  4. LINE (0, 0)-(100, 100), _RGBA32(0, 0, 0, 100), BF
  6.  
  7. SCREEN _NEWIMAGE(800, 600, 32)
  10.     _DEST c
  11.     CLS , _RGBA32(0, 0, 0, 100)
  13.     _PRINTSTRING (20, 41), TIME$
  14.     _DEST 0
  16.     d = _COPYIMAGE(c, 33)
  17.     _PUTIMAGE (_MOUSEX - 50, _MOUSEY - 50), d
  18.  
  19.     _DISPLAY
  20.     _FREEIMAGE d
  22.  
Title: Re: Follow the development of QB64
Post by: codeguy on October 16, 2018, 02:52:17 am
Can you implement SUB/FUNCTION sorting? This would be quite handy for lengthy source.
Title: Re: Follow the development of QB64
Post by: Bert22306 on October 16, 2018, 03:24:49 pm
Quote from: codeguy on October 16, 2018, 02:52:17 am
Can you implement SUB/FUNCTION sorting? This would be quite handy for lengthy source.

Just as a FWIW, I much prefer the subs to be sorted in the order I decide, rather than forced to be alphabetically sorted as MS QuickBasic does. So, IMO, any sorting should be optional, please?

I prefer to arrange the subs in a logical order, for example, in the order in which they are called. Such as, setup, intro, inputs, and so forth. To me, the ability to arrange subs in a logical order was a big "feature" of QB64. Thanks.
Title: Re: Follow the development of QB64
Post by: SMcNeill on October 17, 2018, 05:32:20 pm
Made a few pushes to the development branch today:

1) Change so that _PRINTSTRING now works with the optional image handle.  (As basically described here: https://www.qb64.org/forum/index.php?topic=709.msg5841#msg5841 , though cleaned up a bit for the "official version" which we all share and love.)

2) Bug fix so that we can now upgrade to a 64-bit version of QB64 with zero-difficulty.  (As basically described here: https://www.qb64.org/forum/index.php?topic=354.msg2357#msg2357 )

Change #2 allows us to simply download the 64-bit compiler (you can get a compatible version of the windows 64-bit compiler here: https://www.dropbox.com/s/lwb05aubpsf220v/mingw-w64-bin-x86_64-20141001.7z?dl=1 ), delete the contents of internal/c/c_compiler, and then replace them with the extracted contents of the 7z above, and rebuild QB64 into a 64-bit version. 

The build process is now basically:
Grab it.  (The 64-bit compiler)
Swap it.  (Delete the 32-bit compiler and replace it.)
Build it.   (Run setup_win.bat and build QB64 as a 64-bit application instead of a 32-bit one.)
That's it!
Title: Re: Follow the development of QB64
Post by: STxAxTIC on October 17, 2018, 07:09:08 pm
Grab it.
Swap it.
Build it.
BOP-IT
That's it!



https://en.wikipedia.org/wiki/Bop_It (https://en.wikipedia.org/wiki/Bop_It)
Title: Re: Follow the development of QB64
Post by: SMcNeill on October 21, 2018, 11:10:11 pm
Push to fix the $IF/$LET issue as I reported here: https://www.qb64.org/forum/index.php?topic=720.0

This also adds a new capability so we can check to see if a precompiler variable has been previously defined or not, which allows for useful "smart definitions" of common variables/CONSTs in library files, such as:

Code: QB64: [Select]
  1. $IF TRUEFALSE = UNDEFINED THEN
  2.     CONST True = -1, False = 0
  3.     $LET TRUEFALSE = TRUE

With the above, we can now use True and False as constants in multiple libraries and not have to worry about whether they'll create duplicate definitions or not.  Only the first one executes (while the TRUEFALSE precompiler variable is unset), and the rest of the occurrences are ignored completely by our program. 

*********************

Pushed fix to memory leak issue with PRINT USING following a different print in the same statement, as described here: https://www.qb64.org/forum/index.php?topic=721.msg6075#new
Title: Re: Follow the development of QB64
Post by: Cobalt on October 30, 2018, 12:29:46 am
A little on the new bit shifting functions _SHR(shift right) and _SHL(shift left)
as functions _SHR(VALUE,AMOUNT ) [same applies to _SHL]
where VALUE is up to a INTEGER64 variable that you want shifted
and     AMOUNT is the number of bits to move

null=_SHR(MyVariable,3) will shift the bits in MyVariable to the right by 3 and put the result in null

_SHL will have the effect of increasing the value, so in essence bit 0 is the right most bit. so a value of 1 would have bit 0 turned on( as _byte: 0000 0001) example

Code: QB64: [Select]
  1. a~%%=1 'as bits (0000 0001)
  2. b~%%=_SHL(a~%%, 1) 'shift it by 1 and it is now (0000 0010)
  3. PRINT b~%%
  4.  
the output would be 2 (0000 0010)

_SHR will have the effect of decreasing the value, and bits are simply dropped off the end of the value.
taking b~%% from the above code

Code: QB64: [Select]
  1. c~%%=_SHR(b~%%, 2)
  2. PRINT c~%%
  3.  
now c~%% will be 0 cause we moved the bit from (0000 0010) over 2 which made it drop off leaving (0000 0000)

Trying to shift a value of 0 will have no result because there are no 'set' bits too move. [(0000 0000) no '1's to move!]
it is possible to move the bits too far left and get the same result, going with (0000 0010) we
c~%%=_SHL(b~%%,7)
and wind up with 0 because we move the bit clear off the left side requiring at least an INTEGER to hold the new value.

Values up to INTEGER64,  you can have signed or unsigned depending on what variable use use to hold the returned value a%%_SHL(1,7) will be -128 while a~%%=_SHL(1,7) will be 128
Title: Re: Follow the development of QB64
Post by: SMcNeill on November 02, 2018, 08:23:37 am
Good news for all the nice folks who want to _SCREENMOVE _MIDDLE -- you now can!!

I pushed a fix into the development build (511aee9) a while ago which was basically a change of the original:

Code: QB64: [Select]
  1.                     int32 SW, SH, WW, WH;
  2.                     SW = glutGet(GLUT_SCREEN_WIDTH);
  3.                     SH = glutGet(GLUT_SCREEN_HEIGHT);
  4.                     WW = glutGet(GLUT_WINDOW_WIDTH);
  5.                     WH = glutGet(GLUT_WINDOW_HEIGHT);
  6.                     x = (SW - WW)/2;
  7.                     y = (SH - WH)/2;
  8.                     glutPositionWindow (x,y);
  9.                 }

To the new:

Code: QB64: [Select]
  1.                     int32 SW=-1, SH, WW, WH;
  2.                     while (SW==-1){SW = glutGet(GLUT_SCREEN_WIDTH);}
  3.                     SH = glutGet(GLUT_SCREEN_HEIGHT);
  4.                     WW = glutGet(GLUT_WINDOW_WIDTH);
  5.                     WH = glutGet(GLUT_WINDOW_HEIGHT);
  6.                     x = (SW - WW)/2;
  7.                     y = (SH - WH)/2;
  8.                     glutPositionWindow (x,y);
  9.                 }

So how's this fix work?

Glut returns a value of -1 if we try to use glutGet on an invalid window.

What the issue before was, was QB64 trying to move the window, before glut had finished registering itself properly with the OS and getting a valid handle...

So now, we set the value to -1 to begin with (as if it's an invalid window), and we simply keep pestering glut to return a proper value to us once it's all finished doing its initialization junk with the OS.

Simple fix and _SCREENMOVE _MIDDLE now works as advertised. 
Title: Re: Follow the development of QB64
Post by: SMcNeill on November 02, 2018, 09:17:03 pm
It's been a few days since I pushed changes to CONST into the development build, but I forgot to mention it here.  I apologize.

As I described here -- https://www.qb64.org/forum/index.php?topic=742.0 -- CONST and the internal math routines have now been completely overhauled.

CONST names are now resolved and usable inside other CONST without glitching out, and this now includes our math functions as well.

Before, this would error out:

CONST X = 1.2
CONST Y = INT(X)

It now works perfectly fine.  (Or at least, it should.)

*************

Change #2: CONST has been changed to work with the standard QB64 syntax with the functions/keywords it supports.  Instead of CONST X = ARCCOS(0.5), which didn't follow standard syntax, it now accepts CONST X = _ACOS(0.5).  This should open up ease of use for folks and add increased flexibility to CONST.
Title: Re: Follow the development of QB64
Post by: Robert Claypool on December 17, 2018, 10:45:41 pm
Can you bring back midi file playing. A lot of qb45 programs used TSRs to play midi files and it used to be not that hard to swap in _SND* commands to play them instead.
These, for example: http://qbrpgs.blarg.ca/rpgs.php?view=ALL&page=1
Title: Re: Follow the development of QB64
Post by: FellippeHeitor on January 05, 2019, 06:49:50 pm
Quote from: Robert Claypool on December 17, 2018, 10:45:41 pm
Can you bring back midi file playing. A lot of qb45 programs used TSRs to play midi files and it used to be not that hard to swap in _SND* commands to play them instead.
These, for example: http://qbrpgs.blarg.ca/rpgs.php?view=ALL&page=1

We need a free reliable cross-platform c++ midi library suggestion.

Now, if you're on Windows, just use the builtin system capabilities: https://www.qb64.org/forum/index.php?topic=811.msg100434#msg100434
Title: Re: Follow the development of QB64
Post by: Petr on February 12, 2019, 11:45:45 am
Please repair function _MOUSEMOVEMENTX! Thank you!

not that I could not get around it, but the dysfunction does not really benefit my laziness.

:-D



Code: QB64: [Select]
  1. 'mousemovementX, mousemovementY alternative
  2.  
  3.  
  4. DIM SHARED OldMouseX AS INTEGER, OldMouseY AS INTEGER
  6. OldMouseX = _MOUSEX
  7. OldMouseY = _MOUSEY
  10.     PRINT MOUSEMOVEMENTX, MOUSEMOVEMENTY
  11.     _LIMIT 20
  13.  
  14. FUNCTION MOUSEMOVEMENTX
  15.     SELECT CASE OldMouseX
  16.         CASE IS > _MOUSEX: MOUSEMOVEMENTX = -1: OldMouseX = _MOUSEX
  17.         CASE IS < _MOUSEX: MOUSEMOVEMENTX = 1: OldMouseX = _MOUSEX
  18.         CASE ELSE: MOUSEMOVEMENTX = 0
  19.     END SELECT
  21.  
  22. FUNCTION MOUSEMOVEMENTY
  23.     SELECT CASE OldMouseY
  24.         CASE IS > _MOUSEY: MOUSEMOVEMENTY = -1: OldMouseY = _MOUSEY
  25.         CASE IS < _MOUSEY: MOUSEMOVEMENTY = 1: OldMouseY = _MOUSEY
  26.         CASE ELSE: MOUSEMOVEMENTY = 0
  27.     END SELECT
  29.  
  30.  

Title: Re: Follow the development of QB64
Post by: FellippeHeitor on April 01, 2019, 09:47:04 am
Development build available today (from git 358b725) contains a few more minor fixes and a new warning system has been implemented:

 [ This attachment cannot be displayed inline in 'Print Page' view ]  

So far there are two types of compiler warnings that will be presented to the user but will not prevent compilation:

Also with this build the macOS Mojave issues have been fixed (one by Apple itself with version 10.14.4 of their OS and one by us), so we're compatible with macOS again.

Please help us test these new features of the latest dev version (as well as the ones outlined on this post (https://www.qb64.org/forum/index.php?topic=304.msg2554#msg2554)) as we're **this** close to releasing version 1.3.

Fellippe.
Title: Re: Follow the development of QB64
Post by: RhoSigma on April 01, 2019, 11:38:26 am
The Windows development download links on qb64.org are not available (x32 version, the former text link) and or not working (x64 version, the icon link), which returns "Forbidden", as it only points to autobuilds/development folder, not to an actual download file.

EDIT:
Ok, after deleting all cached browser content and then reloading qb64.org, both download links (x32/x64) appear, but still, both only point to autobuilds/development/ and error out "Forbidden".

BTW - I was wondering long time, that the windows dev download stuck on the built from 2019-02-01, while Linux and Mac dev builds were updated regulary. Maybe a build script problem?

EDIT2:
Forget about it, everything's working now. Probably i just tried to download it in the middle of the built process...
...delete this post, if you want.

Title: Re: Follow the development of QB64
Post by: jack on April 01, 2019, 01:14:38 pm
thank you FellippeHeitor :)
Title: Re: Follow the development of QB64
Post by: Pete on April 01, 2019, 11:51:23 pm
Will _INSTRREV work with a seed? Example x% = _INSTR(10, x$, ",") Where 10 is the seed and wuld mean go ten characters from the right of x$ and then start looking for the first comma?

Pete
Title: Re: Follow the development of QB64
Post by: FellippeHeitor on April 02, 2019, 12:08:07 am
_INSTRREV takes an optional numeric first parameter but it doesn't go from right to left; it just specifies where to start looking, just like with INSTR. If you want ten characters from the right you'd still have to do x% = _INSTRREV(LEN(x$) - 10, x$, ",")
Title: Re: Follow the development of QB64
Post by: Pete on April 02, 2019, 12:34:32 am
What? Don't you think that should be changed? I think it should be changed, and it should cost 5-cents.

Pete
Title: Re: Follow the development of QB64
Post by: FellippeHeitor on April 02, 2019, 12:39:13 am
I'm borrowing the name and the behaviour from VB, and it did make sense to me to specify a start position from left to right instead of the contrary.
Title: Re: Follow the development of QB64
Post by: RhoSigma on April 02, 2019, 02:07:30 am
I also do it the same way in my RInstr&() function (part of GuiTools). It's just the start position as usual from the beginning (left side) of a string and to be honest I found it the same way in almost every BASIC like language I've ever used, doesn't matter how the name of the actual function was. I've taken RInstr&() from MaxonBASIC (very popular on the Commodore Amiga in mid 1990's). Fellippe took _INSTRREV form VB, but it's all the same functionality.

I was about exchanging my RInstr&() with the new _INSTRREV, but didn't, as I still use the old SDL version a lot, which doesn't have the new commands. Unfortunately I still have to stick to SDL, as GL don't work correctly with intl. chars and some symbols on CP437. KEYHIT, INKEY$, INPUT$, (LINE) INPUT all give different results here, but non of it give the correct values/chars. I wish this would be the next great step in improving QB64 GL, bring that back to the SDL behavior, which handled this gracefully. It's a pitty to say that, but cause of this discrepancies, QB64 GL is almost useless for my projects at work, I can use it in private, coding everything in english, but can't expect my work fellows to use english software, as most only speak their native language german.
Title: Re: Follow the development of QB64
Post by: Pete on April 02, 2019, 02:37:55 am
Quote from: FellippeHeitor on April 02, 2019, 12:39:13 am
I'm borrowing the name and the behaviour from VB, and it did make sense to me to specify a start position from left to right instead of the contrary.

Well give it back and borrow this, instead...

Code: QB64: [Select]
  1. sstrng$ = "*,@,h,&,h,a,b,c,d,e,f,g,h,1,2,h"
  2. srch$ = "h"
  3. seed& = 2
  4. PRINT instrrev&(seed&, strng$, srch$)
  5.  
  6. FUNCTION instrrev& (seed&, strng$, srch$)
  7. b$ = SPACE$(LEN(strng$))
  8. FOR i& = LEN(b$) TO 1 STEP -1
  9.     j& = j& + 1
  10.     MID$(b$, j&, 1) = MID$(strng$, i&, 1)
  12. instrrev& = LEN(b$) - INSTR(seed&, b$, srch$) + 1

So I'm asking it to get the first "h" that is 2 or more characters from the right. The example above returns 25, which tells me in my string, the "h" I want located if 25 characters from the left. That's useful for very long strings, where you know what you are looking for is repeated several times throughout the string, but the one you want is very near the end. Maybe this is what you are describing too, as I cannot see a way to seed it from left to right in reverse. I mean using 10 in the above example seems weird to me when I know I want the "h" two or more characters in from the right.

Pete
Text Only | Text with Attachments