fontmap was (I think) introduced with 6.7 but at least here it?s not
>> used. I guess I should get on and test this with LC7 + LC8?
>>
>> John, what version of LC did you test with?
>>
>> Thanks again
>>
>> Alan
>>
>>> On 12 Oct
s again
>
>Alan
>
>On 12 Oct 2015, at 7:16 pm, use-livecode-requ...@lists.runrev.com wrote:
>
>> From: Scott Rossi
>> To: How to use LiveCode
>> Subject: Re: mobileControlSet "fontname" parameter
>> Message-ID:
>> Content-Type: text/plain;charset=utf-8
&
@lists.runrev.com wrote:
>>
>> From: Scott Rossi
>> To: How to use LiveCode
>> Subject: Re: mobileControlSet "fontname" parameter
>> Message-ID:
>> Content-Type: text/plain;charset=utf-8
>>
>> AFAIK, you do need to use the Postscript
to use LiveCode
> Subject: Re: mobileControlSet "fontname" parameter
> Message-ID:
> Content-Type: text/plain; charset=utf-8
>
> AFAIK, you do need to use the Postscript name, and the names are case
> sensitive. Also, the FontMap addition to the standalone bui
> mmm...
>
> just tried in with
>
> iphoneControlSet inputID, "fontName", "helvetica"
> iphoneControlSet inputID, "fontName", "american typewriter"
>
> and it works, in the simulator, anyway...
>
>> From: alanstenho...
mmm...
just tried in with
iphoneControlSet inputID, "fontName", "helvetica"
iphoneControlSet inputID, "fontName", "american typewriter"
and it works, in the simulator, anyway...
> From: alanstenho...@hotmail.com
> Subject: mobileContr
Can someone confirm (or not) that when setting the fontname for a text input
control on mobile, that we have to use the Postscript name of the font?
e.g.
mobileControlSet controlID, “fontname”, FontPostscriptName
I had somehow thought this was being handled automatically for us, but if it’s
not
