Vince is fine programmer with specially clean style of coding. Hate to see his work get buried (= lost) in Programs section, so I offered and he accepted a little place of his own. He has very nice graphics both 2D and 3D and a fan of FreeBasic and JustBasic (really?) or just being an independent program language type guy...

So vince thankyou, this thread is yours. (If you don't like the title let me know.)

If you can see in the thumbnail there, we've added a new option to the start menu for "Run only (no exe)".  This option allows you to compile your file, run it, and then cleans it off your drive when it's finished.  I saw a request somewhere about compiling to temp files, and so I took a while to come up with this for us. 

Currently it's only in my personal fork of the repo, and I've only tested it and verified that it's working as intended for Windows.  Tomorrow I'll test to get it up and going for Linux (and hopefully Mac, though I don't have a Mac to test things on), and then I'll push it into our repo and it'll be one of the features added in to our next build release. 

https://www.tapatalk.com/groups/qbasic/v...05&t=39725

Maybe I should tweak the the attachment limits here a bit. Seems Tapatalk is okay with over 500K.

Pete

RightClickMenu is an easy way to add a small right click popup menu to you programs.  There are several menu styles to choose from - or set your own custom menu colors.  Just define your menu items and call the function by right clicking on the screen.  There are menu separators and items can be disabled/enabled on the fly.   The demo code below show how to call and use the function.  If you need any help just ask.

This is an older version, I lost the newer one that had more menu styles.

- Dav

PPRINT lets you print with QB64's built-in screen font in various sizes, not just the default size.  I use this little SUB often in my programs because it's small, easy to use, and no external FONT files are needed to make large text sizes.  It works by turning printed text to images that _PUTIMAGE can use.   Steve has made a better text to image program that blows mine away, so be sure to check his out HERE.

This demo just PPRINT's the DATE$ on the screen in various sizes.

- Dav

FileSelect$ is a simple to use file selector function that you can use to list all files in the current directory and select a filename from that list.  This is an updated version that allows user defined colors, so it's fully customizable now.  The function pops up a scroll-able box, allows the user to navigate (using the keyboard) and select a file, and it returns that filename as a variable to use.  The screen background is preserved.  The program below contains an example of using the function.   Tested under Windows and Linux.

(Personally I'd recommend Steve's file list routine over this one, but here's mine to play with anyway)

- Dav

it would be nice to have a pdf documentation of qb64. does it exist?

I know QBPE is a compiler, which makes it great, but I end up with MANY *.exe files that accumulate that I don't want.  Can I choose to have a "temp.exe" for example that would overwrite the previous version?

Working (playing) with the "PSET hat" program, I wanted to see some math functions.  So another QB64 program was needed.

I know there are online function plotting and other QBPE programs, but I like simplicity, and I like my own.  So here is what I use for plotting functions.  Since you have to compile it to put in your functions, I put in comments to document the use of it.  I hope it is clear.  This version has a variety of functions for demonstration.  I reserve the right to edit this to later versions.

Since QB64 Phoenix Edition is a newly created offshoot of QB64, people have had various questions about who we are, what we're doing, and what ties we have with QB64 -- and they want to know what's up with our new releases.  Let me address those things one at a time for everyone:


Since Fellippe just walked away from the QB64 Team, things turned into a mess almost overnight with the new CEO.  Issues arose on the Discord, and I'm not going into any details over those things here as it'd just be rehashing the same old news over and over by now.  In the end, QB64 as it existed previously was destroyed.  The old team was completely removed from the repo, with all rights to push, pull, merge, or do releases taken from them.  The forums were shut down.  The wiki was taken offline.  QB64 was burnt to the ground.

Until we stepped in.  The Phoenix Edition worked hard to get the first editable wiki back up on the internet, from an old off-line that had been preserved, so people could have a working reference for the QB64 commands.  We worked to get up a new set of forums so the community could regather and not fragment into a thousand broken pieces.  We've worked hard on gathering up and making all the old resources as available to the public as we possibly can, and hosting as much old information on our servers as we can possibly find and share such as the old Podcasts and transcripts from those.

Most importantly, we've cloned the old repo and have been working fairly fervently to update the source to bring QB64 once again up to a stable version.  If you look at our repo, we've already had 54 commits pushed into it, showing there's been a LOT of activity by the recent team working on things.  We're the new team working hard so that QB64 doesn't die, as the new CEO obviously intended for it to do!

Quote:We will keep the Github Repo up and if their is enough people wanting to keep it alive please keep developing and we may come back.

(04-28-2022, 10:16 AM)Coolman Wrote: thank you for your work. is this version based on qb64 2.01?

(04-28-2022, 10:44 AM)PhilOfPerth Wrote: Pardon my ignorance, but what's the simplest way to transition from the old tQB64 to the new  one? Will I need to move my "home-grown" files, or anything else, into a new directory?