Querying the fontNames includes:
(Default)
(Styled Text)
(Menu)
(Text)
(Message)
(Tooltip)
(System)
These are not font names, but constants the engine accepts so that we
can have good-looking, HIG-savvy UIs on multiple platforms.
But they're not font names. They're not fonts at all. They're
On 3/11/20 5:36 PM, Richard Gaskin via use-livecode wrote:
Querying the fontNames includes:
(Default)
(Styled Text)
(Menu)
(Text)
(Message)
(Tooltip)
(System)
These are not font names, but constants the engine accepts so that we can have good-looking,
HIG-savvy UIs on multiple platforms.
But
On 3/11/2020 6:48 PM, J. Landman Gay via use-livecode wrote:
On 3/11/20 5:36 PM, Richard Gaskin via use-livecode wrote:
Querying the fontNames includes:
(Default)
(Styled Text)
(Menu)
(Text)
(Message)
(Tooltip)
(System)
These are not font names, but constants the engine accepts so that we
can
On 2020-03-11 23:38, Paul Dupuis via use-livecode wrote:
I filled a bug report on this back in February:
https://quality.livecode.com/show_bug.cgi?id=22564
Mark Waddingham declared it was not a bug but a documentation issue,
so I filed and enhancement request:
https://quality.livecode.com/show_b
On 2020-03-11 22:36, Richard Gaskin via use-livecode wrote:
Querying the fontNames includes:
(Default)
(Styled Text)
(Menu)
(Text)
(Message)
(Tooltip)
(System)
These are not font names, but constants the engine accepts so that we
can have good-looking, HIG-savvy UIs on multiple platforms.
But
On 3/12/2020 3:46 AM, Mark Waddingham via use-livecode wrote:
On 2020-03-11 23:38, Paul Dupuis via use-livecode wrote:
I filled a bug report on this back in February:
https://quality.livecode.com/show_bug.cgi?id=22564
Mark Waddingham declared it was not a bug but a documentation issue,
so I fil
Indeed, the current implementation of
(Default),(Menu),(Message),(Styled Text),(System),(Text),(Tooltip)
is not very useful.
For example (System) at size 13 on MacOS 10.15 is on Windows 10
at about (System) at size 12. So one needs nevertheless a platform
switch.
___
Thanks for chiming in, Mark. Would it be helpful to have a bug report
on this, or should I wait to see what you find in your code review?
--
Richard Gaskin
Fourth World Systems
Mark Waddingham wrote:
On 2020-03-11 22:36, Richard Gaskin via use-livecode wrote:
Querying the fontNames includ
On 2020-03-12 15:53, Paul Dupuis via use-livecode wrote:
So here is the simple use-case I ran into. We have a field with an
editor toolbar for rich content editing in an app. The field is set to
(Text) upon start up, as in:
set the textFont of fld "X" to "(Text)"
So that the font is initially i
On 3/12/2020 12:47 PM, Mark Waddingham via use-livecode wrote:
On 2020-03-12 15:53, Paul Dupuis via use-livecode wrote:
So here is the simple use-case I ran into. We have a field with an
editor toolbar for rich content editing in an app. The field is set to
(Text) upon start up, as in:
set the
Another approach might be to find a font or subset of fonts that looks the same
on all platforms and use that. You may have to pay for the font(s) but you gain
consistency.
Bob S
> On Mar 12, 2020, at 10:23 , Paul Dupuis via use-livecode
> wrote:
>
> Yes, it does. Lacking a detailed techni
Hi Mark,
> Am 12.03.2020 um 17:47 schrieb Mark Waddingham via use-livecode
> :
> ...
> A couple of weeks ago (or maybe longer?)
yep, about four weeks ago.
> Klaus noticed a really strange problem with text extraction from a PDF
> printed using LiveCode on macOS - specifically digits did not ex
On 3/12/2020 12:22 PM, hh via use-livecode wrote:
Indeed, the current implementation of
(Default),(Menu),(Message),(Styled Text),(System),(Text),(Tooltip)
is not very useful.
For example (System) at size 13 on MacOS 10.15 is on Windows 10
at about (System) at size 12. So one needs nevertheless a
Paul Dupuis wrote:
> I *do* find that cross-platform UI design and implementation to still
> be the hardest thing to do in LiveCode (on a relative scale of course,
> since LiveCode overall is easy)
>
> I would just like to be able to say in a preferences box for my app
> that I am deploying to thi
On 3/12/2020 3:24 PM, Richard Gaskin via use-livecode wrote:
With more substantial content (web authoring, printed materials, etc.)
the user cares very much, and the likelihood of ever wanting the
OS-specific default font is low, so assigning your own default font
explicitly would work well (ev
On 2020-03-12 17:23, Paul Dupuis via use-livecode wrote:
Yes, it does. Lacking a detailed technical understanding of the
ridiculous complexity of the macOS (or Windows for that matter), is
one reason we used/use HyperCard, SuperCard, MetaCard, Revolution,
LiveCode for the past 25+ years for our a
Hi
If you need a specific font to work because of look, scale, print, etc I
suggest using a font editor app to copy the font you require, rename it to
something unique (the name is embedded so just changing the file name changes
nothing) and then embed it into your app in LC Standalone Settings
Also, there are two major types of vector based fonts: TrueType and OpenType.
OpenType is a Microsoft format, but the same font file can be used for Windows
and Mac.
TrueType gets a little tricky. TrueType fonts made for Windows will also work
for Mac. TrueType made for Mac must be CONVERTED t
18 matches
Mail list logo
