12-10-2022, 07:47 AM
(This post was last modified: 12-10-2022, 07:53 AM by mnrvovrfc.
Edit Reason: Rambling as usual, it's what I do best
)
Welcome to the forums.
I wish there was another program, which is not a &%$*#@ing web browser that could display HTML documents formatted properly. It's because no web browser loads fast, and tolerable enough to use it offline like the first few versions of Internet Explorer and Firefox.
This way could work for documents greater than 1MB. But source code seldom gets that big, definitely not C++ or Python or any other OOP. I proposed advice that was given away for free for many years in the QB64 Wiki, which doesn't apply to those on Unix-like operating systems that cannot have Wine.
Hmmm... doesn't Visual Studio IDE have an option to run a program EXE file with command-line arguments? Then QB64(PE) could be used to write a program that does the printing, after it's passed an ordinary text file. Just use "LPRINT" and watch out for CHR$(34) put literally in the code.
EDIT: It requires the code to be saved as ordinary text file. Now I don't remember but I read somewhere that things could get as perverse as binary signatures and stuff like that being part of a function header! Don't want to anger somebody about what it looks like his/her favorite tool...
I wish there was another program, which is not a &%$*#@ing web browser that could display HTML documents formatted properly. It's because no web browser loads fast, and tolerable enough to use it offline like the first few versions of Internet Explorer and Firefox.
This way could work for documents greater than 1MB. But source code seldom gets that big, definitely not C++ or Python or any other OOP. I proposed advice that was given away for free for many years in the QB64 Wiki, which doesn't apply to those on Unix-like operating systems that cannot have Wine.
Hmmm... doesn't Visual Studio IDE have an option to run a program EXE file with command-line arguments? Then QB64(PE) could be used to write a program that does the printing, after it's passed an ordinary text file. Just use "LPRINT" and watch out for CHR$(34) put literally in the code.
EDIT: It requires the code to be saved as ordinary text file. Now I don't remember but I read somewhere that things could get as perverse as binary signatures and stuff like that being part of a function header! Don't want to anger somebody about what it looks like his/her favorite tool...