Thanks Neville, for doing this research, noting your results in public and
putting together the library of corresponding font names.
Your effort will make it easier for livecode to fix things up.
I have some plans for doing some more advanced font work, so I'm sure down
the road it will help me als
In my last post I alluded to an elusive problem on Windows 10 with the
fontnames function. I think I have identified at least one circumstance where
fontNames() causes a crash on Windows 10.
If in a Windows standalone you call
stop using font file foo.ttf
and then try to get fontNames() witho
Mud is much clearer. ;-)
Bob S
On Feb 3, 2017, at 19:20 , Fraser Gordon via use-livecode
mailto:use-livecode@lists.runrev.com>> wrote:
So, no, because LiveCode doesn't provide a way to get the "display name" of the
font used for these.
But yes, because the font really *is* "(Message)" becaus
A masterful explanation! Thanks Fraser -
Phil
On 2/3/17 7:20 PM, Fraser Gordon via use-livecode wrote:
On 2017-02-03 21:03, Phil Davis via use-livecode wrote:
I'm currently fiddling around with fonts. I see that the list
returned by 'the fontNames' contains some 'placeholder' values,
namely
On 2017-02-03 21:03, Phil Davis via use-livecode wrote:
I'm currently fiddling around with fonts. I see that the list returned
by 'the fontNames' contains some 'placeholder' values, namely these:
(Default)
(Menu)
(Message)
(Styled Text)
(System)
(Text)
(Tooltip)
Is there
Hi Craig,
Maybe those new 'fonts' debuted in LC 7. I see what you're talking about
in LC 6.7.10, then in 8.0.2 I see the additional ones. I don't have LC 7
installed anywhere and don't want to take the time, and none of the
release notes for 6 / 7 / 8 mention it (that I can see), so... guess I
I fear I am becoming more and more orphaned around here, languishing in v.6x.
For what it is worth, the fontNames returns only a list of fonts, one per
line, in my world. Is it a v.8 thing?
Craig Newman
--
View this message in context:
http://runtime-revolution.278305.n4.nabble.com/fontNames-
