When debugging a program, I get white letters in the output on a black background.
This is fine when looking at it, but the printout is a nightmare.
first of all, its hard to read.
Secondly, it uses up all the ink in my printer cartridge.
Do I have to save the output text somewhere before I can print it?
I don't see why we cant reverse the color scheme. But there seems to be no option for that.
This is the only Web site I know of, where you have to deal with white letters.
链接已复制
"Web site"? You're referring to a console program's console window, yes?
White text on black background is the Windows default for console windows. For a given program, you can change the background and text colors by right clicking on the window icon in the far upper left, selecting Properties, and then Colors. You can also change this for any command prompt shortcut you may have.
If you want to change the default for all console applications when run from within Visual Studio or by double-clicking on the EXE, see the second answer at http://superuser.com/questions/581924/i-want-to-permanently-change-the-background-color-to-white-and-the-text-color-to and select Defaults.
I tried opening a graphics window, but there is no way to change the properties of it.
When I clicked on the upper left, that does not appear as a choice.
I only see Restore, minimize, and close
So far the only way I can get text is "Select all" then Copy.
I use Quickwin frequently, and I also believe in printing as a means of aiding debug efforts. So, I feel like I should be able to help, but I don't completely understand what you are trying to do.
Are you copying the project or child window to the clipboard, then pasting that into a text editor (e.g. notepad, wordpad, or even Word) and using that to print?
Please describe your procedure in more detail.
Well, when I have the graphics window open, there are three choices:
Copy text
copy graphics
copy all.
If I select Copy all, then I have to Paste it into a text editor to get black on white.
I was just wondering if there was an easier way to do it.
Of course, if there is a huge amount of debugging text, another approach
is to write it to a formatted file somewhere, then examine that.