I only call start using fonts in preOpenStack and there really is no point =
to stop using fonts.=20
Bob S
> On Apr 16, 2025, at 3:36 PM, Neville Smythe via use-livecode wrote:
>=20
> Does your script call stop using font?
>=20
> This can cause corruption of the font handling code in Windows;=2
Does your script call =E2=80=98stop using font=E2=80=99?
This can cause corruption of the font handling code in Windows; =
typically calling the fontnames thereafter does nothing and I have seen =
a crash
https://quality.livecode.com/show_bug.cgi?id=3D24151
The bug was reported in 2023. It is c
Typo - that was supposed to be Windows 10 (but, the 9 and 0 are really
close on my keyboard and my fingers seem to grow bigger and the keys
smaller as the years go by!)
On 4/15/2025 1:43 PM, Bob Sneidar via use-livecode wrote:
Are you from the future? (There is no Windows 19) LOL!
Bob S
_
Are you from the future? (There is no Windows 19) LOL!
Bob S
> On Apr 15, 2025, at 9:03 AM, Paul Dupuis via use-livecode wrote:
>=20
> With the assorted list problems, I hope this get posted in a readable for=
m.
>=20
> On Windows 19, in a Standalone built on Livecode 9.6.3, the following lin=
With the assorted list problems, I hope this get posted in a readable form.
On Windows 19, in a Standalone built on Livecode 9.6.3, the following line:
put the fontNames into tFonts
Is generating the following execution error:
put: error in expression: (Line 5789, column 1)
This code works -
