QB64 Phoenix Edition
vs GUI Updates - the latest from b+ - Printable Version

+- QB64 Phoenix Edition (https://qb64phoenix.com/forum)
+-- Forum: QB64 Rising (https://qb64phoenix.com/forum/forumdisplay.php?fid=1)
+--- Forum: Prolific Programmers (https://qb64phoenix.com/forum/forumdisplay.php?fid=26)
+---- Forum: bplus (https://qb64phoenix.com/forum/forumdisplay.php?fid=36)
+---- Thread: vs GUI Updates - the latest from b+ (/showthread.php?tid=689)

Pages: 1 2 3 4 5 6 7 8


RE: vs GUI Updates - the latest from b+ - bplus - 12-21-2022

Some updates:

Did I mention Controls now all have optional label, drawn one time with NewControl call (the white ones with screen background color).

Labels have labels and you can toggle bullets, they are now full fledged Control with tab stops and enter keypress to use toggle bullets option.

   

Folders now for Fonts and Images to declutter and organize GUI files, yeah should have done this from start!
This way all GUI apps can share Images, fonts... and only need one copy of BI and BM.
   

Navigation tools in List Box for quicker access to bottom of the list items eg with a dictionary even PgDn button is too slow to get to "s" words.
   

Pete's recent post to Raven has struck at just the right time as I am reconsidering MONOSPACED fonts again with overhaul to text and list boxes property names.


RE: vs GUI Updates - the latest from b+ - vince - 12-22-2022

very nice B+, this must be the Boggle helper


RE: vs GUI Updates - the latest from b+ - Pete - 12-22-2022

Marks' not helping you with your boggle anytime soon, and if you keep it up, Santa Steve might get jealous!

Pete

All I want for Christmas is a coal-onosocpy.


RE: vs GUI Updates - the latest from b+ - vince - 12-22-2022

oh it's up


RE: vs GUI Updates - the latest from b+ - mnrvovrfc - 12-22-2022

(12-21-2022, 05:15 PM)bplus Wrote: Pete's recent post to Raven has struck at just the right time as I am reconsidering MONOSPACED fonts again with overhaul to text and list boxes property names.

The monospaced fonts would be all right in text entry. Otherwise the option to keep things as they are. To say another way, the labels and buttons look better with non-monospaced fonts. Just don't use certain serif fonts like some web browsers displaying "ff" or "fl" in "code" block trying to do it in one-letter space. That's supposed to be a monospaced font and that's why it bothers me.

For example:

Code: (Select All)
fly off

is supposed to be seven places in a monospaced font, right? Actually with Firefox and a certain serif font, it's five. Incredible.


RE: vs GUI Updates - the latest from b+ - bplus - 12-22-2022

Yeah I've spent allot of time thinking about Font. It's a core issue for sizing and finding thinks with mouse clicks.

I've searched Internet for 1:2 ratio fonts and only found one, and that was licensed for personal use only. 

Never knew how rare our default _Font 16 was! I have found a couple of sizable MONSPACE fonts near 1:2 ratio 7,9, 10 to 16 high and I really wonder if it's worth the trouble for text boxes and list boxes to use different heights other than _Font 16. I've changed the List Box back already because drawing character by character to fit cells was taking too long for scrolling. Eventually I want Cut Copy and Paste and ultimately I want an Edit box combining a Text Box with a List Box for full fledged Editor functions (the heck with a stupid line editor!)

I like using any font I want for labels and buttons, that stays for sure but should I allow more that one of those type fonts again seems more trouble than it's worth? 

Ideal would be one nice clean and crisp MONOSPACE font any size that doesn't get so wide across it becomes impractical to use. Arial like, I think I've come close with a Consolas.
   
   
   

Oxy looks like it would be It except it's hitting the title bar, telling me this is one of those fonts that gets cut off along the top.


RE: vs GUI Updates - the latest from b+ - SMcNeill - 12-22-2022

That font clipping is why I've started plugging QPrint into almost all my libraries and stuff.  I'm migrating completely away from the QB64 font handling routines anymore.  Wink


RE: vs GUI Updates - the latest from b+ - mnrvovrfc - 12-22-2022

https://fonts.google.com/noto/specimen/Noto+Sans+Mono

However the lowercase "R" is ugly.

Some Linux terminals set it as console font which is just unacceptable, it's supposed to be a serious thing! For those who like "cute stuff", go for Konsole in Manjaro KDE. On the other hand, "XTerm" is something I would never come to grips with, I need the ability to copy text output and a few other things.

About 1:2 ratio, do you mean less horizontal pixels than vertical? That's difficult largely thanks to "M" and other characters that require accurate diagonals drawn, and otherwise people dislike the "jaggies". Must go for large point sizes, at least 16, and then it would be the "condensed" or "thin" styles which are difficult for us middle-aged folks to read.


RE: vs GUI Updates - the latest from b+ - Pete - 12-22-2022

I download all mine from a little place called Font-asy Island. Ask for Mr. Rorke, but avoid the little guy. He spends all his time in the Comic Sands.

I think I only found 4 M$ ones that work.

Someone linked me this site. Two that qualify are:

https://www.1001fonts.com/monospaced+sans-serif-fonts.html

https://www.1001fonts.com/monospaced-fonts.html

If you have options of fancy, choose the plain, the plain!

Pete


RE: vs GUI Updates - the latest from b+ - bplus - 12-22-2022

Yeah Pete, I already mined that 1001 Fonts site that Steve had referenced some time ago and showed what I found in screen shots, not bad the 7x16 will likely be too narrow for our older eyes but the last might work if I want to gain width usage by 1.125 pixels. It might even be a little more readable?

Thanks Minerva, Google fonts I did look into, there was something about the license or the ratios available that had me continue on with my search. For Ratio, I did mean pixel width to pixel height, since QB64 uses pixel measures for fonts.

I guess writing out my concerns with fonts helped make it clear to just use _Font 16 for Text boxes like I did for List boxes and will be especially appreciated if I ever get to full Edit Boxes I am sure! If I did go with MONOSPACE it would be huge hassle to recode allot of things specially the Control labels which I am liking how they cut the need for labels to zero almost! Just about every Text box needs a label to 'prompt" for input.