08-16-2022, 01:39 PM
Updated the program once again, and you'll need to redownload it from the first post in this topic. What's changed?
1) We now have a pretty little splash screen for an intro to the program.
2) Users can now <R>un a program from the select menu.
NOTE: This requires that the archive is extracted into your QB64 folder, so that it'll find paths and such properly. Your QB64 folder should look something like the following once you've extracted it into the proper place:
![[Image: image.png]](https://i.ibb.co/xFZF8TW/image.png)
NOTE 2: This is still a work in progress. It *ONLY* runs the sample program as long as there is a single BAS file inside the folder so it knows which one to compile and run. Some of the samples rely on multiple EXE files being compiled (such as for a CHAIN example, or one with a TCP/IP localhost example), and those simply get ignored at the moment and won't run at all. (Or do anything really -- not even toss you a nice "these need to be manually compiled" message yet. What can I can say except it's still a work in progress.)
I'll be truly curious for feedback on what we have now, especially from any Linux/Mac folks who might want to point out when/where I may've went wrong with slashes or filename cases, or extensions, or whatnot. I'm no expert on Linux and QB64 -- not by a long shot -- and I honestly don't know if this will work at all for you guys. Does Linux even append a nice .bas or .exe to the filenames for us? If not, then how does it keep track of which is the text file and which is the executable?
Guess I'm going to have to do some more digging into QB64 and Linux/Mac, if I want to say that the Sample Showcase works as it should on them, just as it does on Windows.
1) We now have a pretty little splash screen for an intro to the program.
2) Users can now <R>un a program from the select menu.
NOTE: This requires that the archive is extracted into your QB64 folder, so that it'll find paths and such properly. Your QB64 folder should look something like the following once you've extracted it into the proper place:
NOTE 2: This is still a work in progress. It *ONLY* runs the sample program as long as there is a single BAS file inside the folder so it knows which one to compile and run. Some of the samples rely on multiple EXE files being compiled (such as for a CHAIN example, or one with a TCP/IP localhost example), and those simply get ignored at the moment and won't run at all. (Or do anything really -- not even toss you a nice "these need to be manually compiled" message yet. What can I can say except it's still a work in progress.)
I'll be truly curious for feedback on what we have now, especially from any Linux/Mac folks who might want to point out when/where I may've went wrong with slashes or filename cases, or extensions, or whatnot. I'm no expert on Linux and QB64 -- not by a long shot -- and I honestly don't know if this will work at all for you guys. Does Linux even append a nice .bas or .exe to the filenames for us? If not, then how does it keep track of which is the text file and which is the executable?
Guess I'm going to have to do some more digging into QB64 and Linux/Mac, if I want to say that the Sample Showcase works as it should on them, just as it does on Windows.