Author Topic: Follow the development of QB64  (Read 2679 times)

Offline Ashish

  • The joy of coding is endless.
Re: Follow the development of QB64
« Reply #15 on: August 01, 2018, 08: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

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: [Select]
_TITLE "GL Multisample Testing"
SCREEN _NEWIMAGE(800, 600, 32)

_GLRENDER _BEHIND
_PRINTSTRING (1, 1), "GL_MULTISAMPLE : Enable"
_PRINTSTRING (600, 1), "GL_MULTISAMPLE : Disable"
LINE (400, 0)-(400, _HEIGHT)

DO
    _LIMIT 30
LOOP

SUB _GL () STATIC
    IF NOT Init THEN
        Init = -1
        _glViewport 0, 0, _WIDTH, _HEIGHT
    END IF
    _glMatrixMode _GL_MODELVIEW
    _glLoadIdentity

    _glEnable _GL_MULTISAMPLE 'enable the multisample
    _glBegin _GL_LINE_LOOP
    FOR i = 0 TO _PI(2) STEP .1
        _glVertex2f COS(i) * .4 - .5, SIN(i) * .4
    NEXT
    _glEnd

    _glDisable _GL_MULTISAMPLE 'disable the multisample, you will se jagged ellipse
    _glBegin _GL_LINE_LOOP
    FOR i = 0 TO _PI(2) STEP .1
        _glVertex2f COS(i) * .4 + .5, SIN(i) * .4
    NEXT
    _glEnd

END SUB
« Last Edit: August 01, 2018, 08:43:44 AM by Ashish »
if (Me.success) {Me.improve()} else {Me.tryAgain()}


aKFrameWork - http://bit.ly/aKFrameWork
Menu System - http://bit.ly/guiMenuBar
p5.js in QB64 - http://bit.ly/p5jsbas

@KingOfCoders

Offline FellippeHeitor

  • QB64 Developer
  • LET IT = BE
    • QB64.org
Re: Follow the development of QB64
« Reply #16 on: August 01, 2018, 08:39:18 AM »
Exactly. On macOS _GL_MULTISAMPLE doesn't need to be enabled as it's on by default.

Offline FellippeHeitor

  • QB64 Developer
  • LET IT = BE
    • QB64.org
Re: Follow the development of QB64
« Reply #17 on: August 01, 2018, 10: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).
« Last Edit: August 01, 2018, 10:50:54 PM by odin »

Re: Follow the development of QB64
« Reply #18 on: August 17, 2018, 08: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)
« Last Edit: August 17, 2018, 08:28:01 AM by coder »

Offline FellippeHeitor

  • QB64 Developer
  • LET IT = BE
    • QB64.org
Re: Follow the development of QB64
« Reply #19 on: August 17, 2018, 08:31:30 AM »
Help -> About

Options -> Display

The modern UI is separate from QB64's core, check it out: 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.
« Last Edit: August 17, 2018, 08:50:08 AM by FellippeHeitor »

Offline FellippeHeitor

  • QB64 Developer
  • LET IT = BE
    • QB64.org
Re: Follow the development of QB64
« Reply #20 on: September 20, 2018, 12:56:04 PM »
New dev build available today (from git e490b1a) contains:

Enhancements
(as discussed here):
    - 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)
    - A bug that would cause an include line to be duplicated when resizing the IDE was fixed. (as discussed here)
« Last Edit: September 21, 2018, 01:38:53 AM by FellippeHeitor »

Offline Aureal

  • memes
Re: Follow the development of QB64
« Reply #21 on: September 21, 2018, 02:39:14 PM »
Pls implement a C++11 compatible compiler :( :( :(

Offline Petr

  • I am instructed.
Re: Follow the development of QB64
« Reply #22 on: September 22, 2018, 08:32:40 AM »
I find _SNDRAW bug in new IDE, read here: https://www.qb64.org/forum/index.php?topic=614.msg4813#msg4813
« Last Edit: September 22, 2018, 08:33:57 AM by Petr »

Offline FellippeHeitor

  • QB64 Developer
  • LET IT = BE
    • QB64.org
Re: Follow the development of QB64
« Reply #23 on: September 22, 2018, 10:42:41 AM »
Thanks for reporting, Petr.

Re: Follow the development of QB64
« Reply #24 on: October 08, 2018, 04:23:09 PM »
Pls implement a C++11 compatible compiler :( :( :(

Why ?

Can't you code in pure ANSI C Vs the cripled C++ ?
It's better to look like an idiot for a short time while asking something obvious to an expert than pretending to be smart all your life. (C) Me.

Offline Petr

  • I am instructed.
Re: Follow the development of QB64 - Memory release problem
« Reply #25 on: October 12, 2018, 03: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: [Select]

c = _NEWIMAGE(100, 100, 32)
_DEST c
LINE (0, 0)-(100, 100), _RGBA32(0, 0, 0, 100), BF
_DEST 0

SCREEN _NEWIMAGE(800, 600, 32)
_PUTIMAGE , _SCREENIMAGE
DO
    _DEST c
    CLS , _RGBA32(0, 0, 0, 100)
    _PRINTMODE _KEEPBACKGROUND , c
    _PRINTSTRING (20, 41), TIME$
    _DEST 0
    WHILE _MOUSEINPUT: WEND
    d = _COPYIMAGE(c, 33)
    _PUTIMAGE (_MOUSEX - 50, _MOUSEY - 50), d

    _DISPLAY
    _FREEIMAGE d
LOOP

Re: Follow the development of QB64
« Reply #26 on: October 16, 2018, 03:52:17 AM »
Can you implement SUB/FUNCTION sorting? This would be quite handy for lengthy source.

Re: Follow the development of QB64
« Reply #27 on: October 16, 2018, 04:24:49 PM »
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.

Offline SMcNeill

  • QB64 Developer
Re: Follow the development of QB64
« Reply #28 on: October 17, 2018, 06: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!

Re: Follow the development of QB64
« Reply #29 on: October 17, 2018, 08:09:08 PM »
Grab it.
Swap it.
Build it.
BOP-IT
That's it!



https://en.wikipedia.org/wiki/Bop_It
« Last Edit: October 17, 2018, 08:10:23 PM by STxAxTIC »
"An eye for an eye like a fish needs a bicycle" - Adolf Lincoln

Efforts:
http://www.barnesreport.net/scripturam/