A silly program to test Impulse Tracker module playback, and PCM data creation from it on QB64 Phoenix Edition v3.1:

Is your computer watching you?

Well, not exactly symmetrical, but close. So I call it: A Big Tree.

An update that I'm happy to announce, with lots of changes for people to enjoy -- version 3.1 has been released!

Quote:https://github.com/QB64-Phoenix-Edition/...tag/v3.1.0 See GitHub link for full release notes. 

Enhancements
 - New audio backend using miniaudio
- Miniaudio and a few other libraries have replaced the OpenAL-based audio backend that was previously used. - This fixes licensing concerns with using OpenAL, which was LGPL licensed. - Newly supported formats include flac, mod, s3m, xm, it, rad
. - Image backend enhancements - Support for pcx images was added.
 - _LOADIMAGE was improved to support loading 256-color images.
 - Add _ROR & _ROL support. 

Bug Fixes
  - Use -no-pie on Linux, fixes running compiled executables from file browsers
  - Remove DPI Awareness on Windows, QB64 executables will properly scale based on the OS setting 


Full Changelog: https://github.com/QB64-Phoenix-Edition/...0...v3.1.0

I got inspired by other folks tree programs  and decided to spend part of my birthday making one to share.
Mostly new code aside from a few subs I may or may not have shared in the past.

Exploring moving/controlling an object etc...very fun project

No collisions yet, no sound.   Control with w, a, d keys 

Cheers

Remember Planetsourcecode.com and all the VB4,5,6 projects there? 

Well, someone backed up a good chunk of it, and put it on github, categorized, and with the original program descriptions / screenshots / ZIP files / etc. 

This will take days / weeks / months to go through, but I am seeing some really neat stuff there. 

The classic VB stuff alone will provide plenty of ideas for future QB64 projects, algorithms, etc., so I just wanted to post the URL for anyone interested. 

Index: https://github.com/Planet-Source-Code/PSCIndex

By Category: https://github.com/Planet-Source-Code/PS...ByCategory

1. Submissions by Worlds
   
2. Submissions by Categories
   
3. Submissions by Authors
   
4. All Time Best Code/Article/Tutorial Hall of Fame
   
5. All Submissions (with Search)
   

I know B+ has made a better one awhile back, but I've wanted to make one of these myself for years and FINALLY did it!!
It doesn't add leaves but it makes the trunk and random branches. And the land line. 
It finally came to me this morning to just use PSET color plot points and to loop it and at every loop it also scans to find those PSET color plot points. 
It's very simple if you take a look at the code and play around with it.  
In the comments I added the PSET color not to use anywhere else on the screen for your own programs since that's where it needs those points. In the code I put where you can play around with other numbers on 2 lines. 

Press the Space Bar to make another random tree. 
The funny thing is, I was trying to do this yesterday but ended up making the Tesla Coil instead.  

Actually, no new routine for calling a video has to be worked into QB64, it can also be done that way. 
One can call a program for playing videos created in Visual Basic with "Run" from QB64. In the example, programs and video are in the same directory, but this is not necessary.

Let's see if you can also call up a player directly. Would be even easier. 

"Well I don't give a damn about my bad reputation."

- Joan Jett, Bad Reputation



Basic has gotten a bad reputation, some of it deserved, some of it "sneering" by people who use "real" programming languages. Or they don't know, or don't realize, the Basic languages of today "are not your father's Basic." Let's look at some of the criticisms people have of basic.

• Requires line numbers. Basic hasn't "required" line numbers for over 30 years. Most of the "world-class" compilers (and interpreters) support line numbers if needed, but labels may be used. It is entirely possible to write functional Basic programs without needing line numbers or labels.
  
• Only allows short (1 or 2 character variable names). This restriction hasn't been present in Basic for over 40 years. And variables can include the underline _ as a separator.
  
• Variables have to be identified by a type symbol, e.g. % for integer, $ for string, etc. This is done as a convenience, so variables can be "defined" when used, and the compiler will know what the variable is used for. It is also provided for backward compatibility. You can declare a variable as a certain type before use, (e.g. DEFINE MyName AS STRING), declare certain variables beginning with certain letters have a default data type, and can even require all variables be declared before use.
  
• Requires declaring assignments by using "LET" as a prefix. Developments in scanning eliminated that requirement back in the 1970s. The LET keyword is kept strictly for backward compatibility.
  
• Produces "spaghetti code." When programs were written on an "ad hoc" or "seat of the pants" methods, yes, you got programs that jumped all over the place, and had no consistency. But this was true of any language that lacked good control structures, had line labels, and no means other than  GOTO and IF statements to choose code paths. This includes C, Fortran and Cobol. It is possible, even when all Basic had for program control and branching were GOTO, GOSUB, and IF x THEN GOTO, to write structured or cohesive programs that were more-or-less consistent in using structure in code.
  
• Weak or inadequate control structures. Basic has all the control structures supported by other high-level languages, including: WHILE, CASE, FOR, IF statement block, procedures (SUB) and functions.
  
• Lacks support for structures or records. The TYPE statement allows creation of a structured record. Fields in a structure can be accessed using the standard variable.field notation.
  
• You can't access external routines written in other languages. External routines can be called, and any of the common calling conventions may be used.
  
• No database support. Since external routines can be accessed, any database system that provides a shared library for database access can be used.
  
• Only supports short (<256 byte) strings. Basic supports virtually unlimited length of strings. I wrote a short (<10 line) program to double the length of a string on each iteration of a loop. After 26 iterations, I had concatenated a string that was over 130 million characters long. Not that you're likely to need to work with strings that long, it is trivially easy to handle 1K or 100K strings in a Basic program.
  
• No dynamic memory. Basic supports pointers, creation of dynamically allocated structures (records) using the NEW keyword. Basic supports dynamic arrays that can be shrunk or expanded.
  
• Is trivially easy to learn. This is a criticism? You can go online and find videos on YouTube to teach C++ in 10 hours. The fact that Basic can be picked up by a person not familiar with programming even faster than this does not mean the language is a "toy." Basic can and has been used to develop professional applications. It just happens to have a gentler learning curve than other programming languages is a strength, not a weakness. It also creates an advantage, in that once you learn one programming language, it's easier to pick up others. Basic's ease of use may make it appear to be less capable than other languages, but it is usable by professionals to actually accomplish real work.
  
• Can't be used for GUI applications or anything other than for text applications. Some versions of Basic support Windows forms. One supports the WXWidgets GUI framework. Others support Windows WIN32 API, or other GUI frameworks. Most Basics support line drawing and other graphical image drawing functions.