Author Topic: Follow the development of QB64 v1.3  (Read 14824 times)

0 Members and 1 Guest are viewing this topic.

Offline Ashish

  • Forum Resident
  • Posts: 630
  • Never Give Up!
Re: Follow the development of QB64
« Reply #15 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

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.  
  4. _PRINTSTRING (1, 1), "GL_MULTISAMPLE : Enable"
  5. _PRINTSTRING (600, 1), "GL_MULTISAMPLE : Disable"
  6. LINE (400, 0)-(400, _HEIGHT)
  7.  
  8.     _LIMIT 30
  9.  
  10. SUB _GL () STATIC
  11.     IF NOT Init THEN
  12.         Init = -1
  13.         _glViewport 0, 0, _WIDTH, _HEIGHT
  14.     END IF
  15.     _glMatrixMode _GL_MODELVIEW
  16.  
  17.     _glEnable _GL_MULTISAMPLE 'enable the multisample
  18.     _glBegin _GL_LINE_LOOP
  19.     FOR i = 0 TO _PI(2) STEP .1
  20.         _glVertex2f COS(i) * .4 - .5, SIN(i) * .4
  21.     NEXT
  22.     _glEnd
  23.  
  24.     _glDisable _GL_MULTISAMPLE 'disable the multisample, you will se jagged ellipse
  25.     _glBegin _GL_LINE_LOOP
  26.     FOR i = 0 TO _PI(2) STEP .1
  27.         _glVertex2f COS(i) * .4 + .5, SIN(i) * .4
  28.     NEXT
  29.     _glEnd
  30.  
  31.  
« Last Edit: August 01, 2018, 07:43:44 am by Ashish »
if (Me.success) {Me.improve()} else {Me.tryAgain()}


My Projects - https://github.com/AshishKingdom?tab=repositories
OpenGL tutorials - https://ashishkingdom.github.io/OpenGL-Tutorials

FellippeHeitor

  • Guest
Re: Follow the development of QB64
« Reply #16 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.

FellippeHeitor

  • Guest
Re: Follow the development of QB64
« Reply #17 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).
« Last Edit: August 01, 2018, 09:50:54 pm by odin »

Offline coder

  • Newbie
  • Posts: 3
  • My Name Is Not Steve.
Re: Follow the development of QB64
« Reply #18 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)
« Last Edit: August 17, 2018, 07:28:01 am by coder »

FellippeHeitor

  • Guest
Re: Follow the development of QB64
« Reply #19 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

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, 07:50:08 am by FellippeHeitor »

FellippeHeitor

  • Guest
Re: Follow the development of QB64
« Reply #20 on: September 20, 2018, 11:56:04 am »
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, 12:38:53 am by FellippeHeitor »

Offline Aureal

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

Offline Petr

  • Forum Resident
  • Posts: 1720
  • The best code is the DNA of the hops.
Re: Follow the development of QB64
« Reply #22 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
« Last Edit: September 22, 2018, 07:33:57 am by Petr »

FellippeHeitor

  • Guest
Re: Follow the development of QB64
« Reply #23 on: September 22, 2018, 09:42:41 am »
Thanks for reporting, Petr.

Offline Fifi

  • Forum Regular
  • Posts: 181
    • My small QB64 contribution
Re: Follow the development of QB64
« Reply #24 on: October 08, 2018, 03: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

  • Forum Resident
  • Posts: 1720
  • The best code is the DNA of the hops.
Re: Follow the development of QB64 - Memory release problem
« Reply #25 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)
  3. LINE (0, 0)-(100, 100), _RGBA32(0, 0, 0, 100), BF
  4.  
  5. SCREEN _NEWIMAGE(800, 600, 32)
  6.     _DEST c
  7.     CLS , _RGBA32(0, 0, 0, 100)
  8.     _PRINTSTRING (20, 41), TIME$
  9.     _DEST 0
  10.     d = _COPYIMAGE(c, 33)
  11.     _PUTIMAGE (_MOUSEX - 50, _MOUSEY - 50), d
  12.  
  13.     _DISPLAY
  14.     _FREEIMAGE d
  15.  

Offline codeguy

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

Offline Bert22306

  • Forum Regular
  • Posts: 206
Re: Follow the development of QB64
« Reply #27 on: October 16, 2018, 03: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
  • Forum Resident
  • Posts: 3972
    • Steve’s QB64 Archive Forum
Re: Follow the development of QB64
« Reply #28 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!
https://github.com/SteveMcNeill/Steve64 — A github collection of all things Steve!

Offline STxAxTIC

  • Library Staff
  • Forum Resident
  • Posts: 1091
  • he lives
Re: Follow the development of QB64
« Reply #29 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
« Last Edit: October 17, 2018, 07:10:23 pm by STxAxTIC »
You're not done when it works, you're done when it's right.