Dark mode QB64-PE IDE colors themes
#11
That's a nice font @TerryRitchie or is it the size? I've tried some Arial but did not like results.
b = b + ...
Reply
#12
(06-30-2023, 10:05 PM)bplus Wrote: That's a nice font @TerryRitchie or is it the size? I've tried some Arial but did not like results.
Here are my settings:


Attached Files Image(s)
   
Software and cathedrals are much the same — first we build them, then we pray.
QB64 Tutorial
Reply
#13
Maybe I'll give that a shot, I am wondering about char cell width.

Update: Ah! at 18 the font stops being too thin and I can still fit 100+ chars across the screen.
b = b + ...
Reply
#14
(06-30-2023, 10:05 PM)bplus Wrote: That's a nice font @TerryRitchie or is it the size? I've tried some Arial but did not like results.

It's actually Lucida Console, or "C:\Windows\Fonts\lucon.ttf". Arial is not a monospaced font. Also in Terry's screenshot he seems to have selected the boldfaced edition of Lucida Console which is too intense for my taste.

I took another look at the screenshot. It actually shows off half the screen with blue as dark as possible and bright white. But it's not boldface. I got fooled.
Reply
#15
Has anyone at least tried my program or made adjustments to it? Huh

Please read the instructions provided in the post:

https://staging.qb64phoenix.com/showthre...2#pid17362
Reply
#16
(07-01-2023, 02:34 PM)mnrvovrfc Wrote: Has anyone at least tried my program or made adjustments to it? Huh

Please read the instructions provided in the post:

https://staging.qb64phoenix.com/showthre...2#pid17362

Ok for you I tried it. Had to fix this section to print to a file in my Docs to copy / paste to config.
Code: (Select All)
'fe = freefile
Open afile$ For Output As #1
For w = 1 To 20
    Print #1, sf(w)
Next
Close #1
Print "ALL DONE!"
System

Here is best IMO maybe:
   

I don't think you would stumble on ideal color scheme randomly, but maybe get ideas from random run.
b = b + ...
Reply
#17
Thanks!

The font selection of the "reply" box doesn't work, cannot select "Courier New" and otherwise I have to use "code" block. This forum absolutely hates whitespace, tries to kill all that it could find not inside sentences.

Code: (Select All)

case 7, 8, 9
rr = Random1(96)
gg = Rand(16, 64)
bb = Rand(32, 96)
if Random1(2) = 1 then swap gg, bb
if Random1(2) = 1 then swap rr, gg
if Random1(2) = 1 then swap rr, bb

In this code section could set all three variables to pick a random value from zero to 64 or even lower for "true dark mode". I did it like that because I accept slight red, blue, purple etc. which is dark, as background color. Not the absolute black that dominates some people's displays.

I wrote the file statements and then commented them out because somebody would have requested direct change into "internal/config.ini" without wanting to do it themselves. If one doesn't know what he/she is doing here he/she could become peaked off at me for ever supplying this "trick" program...

Also "why do you not give me kewl names of the schemes?" Time for some more poetry.
Reply
#18
@mnrvovrfc I thought how you did file statements was great because you left the internal\config.txt alone = safe. And also how you left just showing in print what it was writing fine as well, if it were showing. You closed the thing not with End but with System which clears the screen and I just see a flash and it is gone.
b = b + ...
Reply
#19
Remember I use Linux and Windows10, not Windows11 so if I have $CONSOLE:ONLY at the top I have to use SYSTEM instead of END if I don't want the annoying "Press enter to continue" prompt and after I press [ENTER] the terminal does not clear.

Now I have to remember if I share my programs to not even bother with $CONSOLE:ONLY and to use END instead of SYSTEM, because apparently I'm the only one dealing with the prompt that END gives out.

Because this is a program that only outputs text, I put the $CONSOLE:ONLY to cut the executable file by about half. The executable then is about 650KB in size. If I left the SCREEN 0 in my program then the executable bloats to 1.2MiB more or less. Writing messages ending with "Press any key to continue" out of the usual screen derrived from QBasic is annoying to me if the program only creates text that goes to some output file.
Reply
#20
$Console:ONLY is fine specially if its smaller size and End works fine with it.

End saves you from typing 
Sleep: System
If you want the user to see what the program wrote for them.

Code: (Select All)
$Console:Only
Print "hello world"
'End
System ' LOL what?
b = b + ...
Reply




Users browsing this thread: 2 Guest(s)