09-16-2025, 10:36 AM
That is certainly something someone could build, but you'd have to deal with all the nuances for calling images, paths, etc. For instance, if I use: _LOADIMAGE("c:\qb64\space-invaders\mypic.jpg", 32) I could easily find the path to create the directory if it didn't already exist, but if I use: _LOADIMAGE(dir1$ +"mypic.jpg", 32) then my routine would have to examine the software and figure out what path dir1$ was used for... and it gets worse; what if I use dir1$ for more than one path and I don't use a progressive top to bottom flow in my program? Now I essentially have to make my routine read and determine the entire code flow, to see what dir1$ assignment was used for this image to unpack it into the correct folder.
So no, I haven't made one of these nor do I use one.
What I did make 20+ years ago was a pseudo-zip file. It put all my routines together as one big exe file. The files were joined in such a way that when they were copied back with BINARY read/write, a header was read at the beginning of the file to determine the number of bytes of each file and the path and name, so each path could be made and each file could be copied to the correct folder in its exact size, and the remaining would look to the next set of header entries to begin unpacking the next file, and so on.
Pete
So no, I haven't made one of these nor do I use one.
What I did make 20+ years ago was a pseudo-zip file. It put all my routines together as one big exe file. The files were joined in such a way that when they were copied back with BINARY read/write, a header was read at the beginning of the file to determine the number of bytes of each file and the path and name, so each path could be made and each file could be copied to the correct folder in its exact size, and the remaining would look to the next set of header entries to begin unpacking the next file, and so on.
Pete
