06-25-2023, 08:30 PM
I have used libraries, mostly to get the hang of doing it. However, I tend to use the libraries as a place to copy and paste those routines that I need for a larger project. That way the project is all inclusive and I can do modifications in one project without affecting others.
I keep the executables with the source folder as a rule. The exception would be when doing tests of code snippets, then I just do it in the QB64 folder. Once it works it gets copied and pasted to its ultimate destination.
I like putting assets in associated folders like 'images', 'sounds', 'scenario saves' and such like. If I do have inter-directory assets, then I resort to zip files for posting, but I try to avoid that. I'm not much for downloading zips; preferring to copy and paste member's code examples, and I assume others find it a bit of a pain too. A lot of the time, I try to have the code create what it needs when feasible.
I keep the executables with the source folder as a rule. The exception would be when doing tests of code snippets, then I just do it in the QB64 folder. Once it works it gets copied and pasted to its ultimate destination.
I like putting assets in associated folders like 'images', 'sounds', 'scenario saves' and such like. If I do have inter-directory assets, then I resort to zip files for posting, but I try to avoid that. I'm not much for downloading zips; preferring to copy and paste member's code examples, and I assume others find it a bit of a pain too. A lot of the time, I try to have the code create what it needs when feasible.
DO: LOOP: DO: LOOP
sha_na_na_na_na_na_na_na_na_na:
sha_na_na_na_na_na_na_na_na_na: