11-07-2022, 10:49 PM
(This post was last modified: 11-07-2022, 10:50 PM by mnrvovrfc.
Edit Reason: Loading non-BMP was "natively" available but not saving
)
I had created a small BASIC code library that I used to compile to QLB, that I don't even use anymore, but I should try to use some of them. However, many of them were text-graphics like drawing boxes or creating menus that accepted input. At this time I have a couple of "BM" suffix files lying around and I'm just copy-pasting from them, not bothering to include one of them whole any longer.
This reminds me of something: I might start a thread about it. Or I should finally create an account with Github, ugh, want to avoid that if possible.
I like other's routines, the problem is I have to learn how to do the function call and what the parameters do. Such as the word-wrap thing that Terry did a short time ago. I was getting quite used to the version that he first posted before he changed it.
I really wanted to use Steve's library for loading and saving image files other than BMP, but on Linux. Right now I have to export everything to BMP, because I also have to leave open the possibility of programming in Freebasic. I like QB64PE's ability to include C/C++ code with "dot-H" files, not having to use some external DLL, SO or alike which is clunky. That said, I didn't mind the "overhead" that the old SDL version of QB64 required but those DLL's could eat some valuable disk space.
Despite the new "open" and "save" file dialogs I think that, only for uniqueness, I would continue using Dav's function on Linux. "Don't fix it if it isn't broken" but only if I had hundreds of source code files needing to display an open file dialog. At this moment I did only one program, which I had to delete from this forum due to the lack of interest. It was a program that read a text file having floating-point "x" and "y" values, one per line and plotted them by line on the screen. That was a bit complicated and therefore sought another solution. Such as the math expression parser that Steve and others did. I had used Lua, calling it via "SHELL" to produce the output text file. Using the Lua API is tricky and would require "liblua.dll" or "liblua.so" involved in creating the user program. But I really need to sit down and figure out how to do the "virtual machine", to send it a string which is a Lua script, and to obtain the output of that script (or error message) as a VLS.
This reminds me of something: I might start a thread about it. Or I should finally create an account with Github, ugh, want to avoid that if possible.
I like other's routines, the problem is I have to learn how to do the function call and what the parameters do. Such as the word-wrap thing that Terry did a short time ago. I was getting quite used to the version that he first posted before he changed it.
I really wanted to use Steve's library for loading and saving image files other than BMP, but on Linux. Right now I have to export everything to BMP, because I also have to leave open the possibility of programming in Freebasic. I like QB64PE's ability to include C/C++ code with "dot-H" files, not having to use some external DLL, SO or alike which is clunky. That said, I didn't mind the "overhead" that the old SDL version of QB64 required but those DLL's could eat some valuable disk space.
Despite the new "open" and "save" file dialogs I think that, only for uniqueness, I would continue using Dav's function on Linux. "Don't fix it if it isn't broken" but only if I had hundreds of source code files needing to display an open file dialog. At this moment I did only one program, which I had to delete from this forum due to the lack of interest. It was a program that read a text file having floating-point "x" and "y" values, one per line and plotted them by line on the screen. That was a bit complicated and therefore sought another solution. Such as the math expression parser that Steve and others did. I had used Lua, calling it via "SHELL" to produce the output text file. Using the Lua API is tricky and would require "liblua.dll" or "liblua.so" involved in creating the user program. But I really need to sit down and figure out how to do the "virtual machine", to send it a string which is a Lua script, and to obtain the output of that script (or error message) as a VLS.