+- QB64 Phoenix Edition (https://staging.qb64phoenix.com)
+-- Forum: Chatting and Socializing (https://staging.qb64phoenix.com/forumdisplay.php?fid=11)
+--- Forum: General Discussion (https://staging.qb64phoenix.com/forumdisplay.php?fid=2)
+--- Thread: Print source code from the IDE (/showthread.php?tid=1191)
RE: Print source code from the IDE - Dimster - 12-10-2022
Another way to do this Kernelpanic is with a Screen Snip app. I'm using Windows and find it on my task bar. You just highlight what you want to print, snip it and just print. The problem is it also prints all the color so the IDE background needs to be white. I find this quick but can only highlight a page worth of the IDE screen at a time. App I'm using is call Snip & Sketch
RE: Print source code from the IDE - SMcNeill - 12-10-2022
Isn't the easiest solution to just save the program to drive, open your preferred word processor, and then print it from there?
RE: Print source code from the IDE - bert22306 - 12-10-2022
If I want to print only a few lines of the code, I just do a copy-paste from IDE to Word. If I want to include an entire program in a document, just copy the .bas file to whatever folder you are working in, even maybe a temp folder, and then change the filename extension from .bas to .txt. Print using Notepad, WordPad, Word, whatever.
If the .bas file includes characters from the extended IBM character set, Word will ask you how to import that .txt file. They will show up correctly. Actually, I've been doing this since back in MS QuickBasic days.
RE: Print source code from the IDE - Kernelpanic - 12-11-2022
Quote:. . .I just do a copy-paste from IDE to Word.
I wrote a small program to calculate the percentage price increase in electricity. I copied the output and pasted it into Word. - I'm missing the color in the source code. The color didn't work that well in Notepad++ either, so I wrote the whole thing again in C and printed it out in color.
RE: Print source code from the IDE - Pete - 12-11-2022
I'm glad you mentioned color. When I print, it's all black and white. I didn't consider making a color printing of the IDE.
+1
Pete
RE: Print source code from the IDE - bplus - 12-12-2022
No more color, no more ink, no more dried up clogged print heads. Toner sure solved allot of problems!
RE: Print source code from the IDE - mnrvovrfc - 12-12-2022
(12-12-2022, 03:46 AM)bplus Wrote: No more color, no more ink, no more dried up clogged print heads. Toner sure solved allot of problems!LOL. That first sentence could almost be sung if it rhymed, to the tune of, "No more pencils, no more books ..."
I was cheered up the day I discovered one cadence in the U.S.Army was, "No more M-16's, only beautyqueens ..."
RE: Print source code from the IDE - SMcNeill - 12-12-2022
No more color, no more ink, no more dried-up, clogged-up, printhead stink!
Toner's good, and toner's great! It sure solved lots of problems, mate!
...and you can write the rest of the ditty.
RE: Print source code from the IDE - Pete - 12-12-2022
I print greyscale, saves some bucks
Too bad "Steve-boy's" jingle sucks
RE: Print source code from the IDE - Kernelpanic - 12-12-2022
Printed information can still be useful today.
Until about 2014 I had Linux (SuSE) from 1996 on as a second system on my computers. When SuSE 11.3 had problems with the monitor again, I had had enough and finally deleted it from my system. A process that I had already done umpteen times, since I reinstalled every SuSE version.
After the procedure known to me, there was the usual restart, and . . . I thought I didn not see it right: No system found. Shock at noon!
I had Win Vista Ultimate installed at the time and my private data was all encrypted. And of course I had not backed up the key.
It was a Sunday and it took me from 12pm to 1am to restore my system. The tips and advice I had printed out earlier helped me in this case. Without these documents I would never have gotten back into my system and much of my private data would have been lost as I had made the last backup about ten/twelve days before.
Progress or not, nothing beats the good old methods.
My first Linux
<- 
![[Image: SUSE4-3.jpg]](https://i.ibb.co/6mfVXB9/SUSE4-3.jpg)