04-28-2022, 03:08 AM
(04-27-2022, 08:29 PM)johnno56 Wrote: Fascinating. An interesting concept.
I am going to assume that, the addition of the "spritesheet" data stored within the main program itself, could possibly reduce time in "reading" the sheet.
I am however left with two questions.
1. Is there an overall saving of disc space by having the data stored withing the main program? ie: Core program + external datasheet or Combined.
2. If the user wanted to edit a sprite, just how could that be done, without an "external" file?
Do not misunderstand. I do not oppose the use of such a program. This is an interesting concept. I would be understandably curious, at some point in time, to see an application or game created by using this method. This program is quite good. I look forward to witnessing its progress.
Well done.
J
1. There's no real saving of space. It's more to just keep it with the program and distribute the whole things as one file it also makes asset management easy because the image is in the program.
2. A- Write an image editor. Save it out and read it back in or pass it through BASIMAGE and slap it back in.
B- You could actually just copy the image out to the clipboard and edit it in any paint program you wish.
Save it in the paint program, run it through BASIMAGE, and redit the code.
This is really DAV's work. It's just so easy to make use of.