mobileControlSet "fontname" parameter

[Alan Stenhouse]

Hi Mark

Done. 

http://quality.runrev.com/show_bug.cgi?id=16206

Hope that’s understandable enough.

cheers

Alan

On 12 Oct 2015, at 9:36 pm, use-livecode-request at lists.runrev.com wrote:

> 
> Hi Alan,
> 
> Could you file a bug about this? I can't recall off the top of my head whether the fontName property of native controls passes through the fontmap.
> 
> Warmest Regards,
> 
> Mark
> 
> Sent from my iPhone
> 
>> On 12 Oct 2015, at 19:44, Alan Stenhouse <alanstenhouse at hotmail.com> wrote:
>> 
>> Thanks John + Scott.
>> 
>> So, that doesn?t seem to be any clearer - 2 conflicting reports. I?ve also tried setting it to the display fontname and that works - but only when the postscript name is the same, AFAICS.
>> 
>> I was testing on the simulator with iOS 8.2 and on device with iOS 7.
>> 
>> The 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 2015, at 7:16 pm, use-livecode-request at lists.runrev.com wrote:
>>> 
>>> From: Scott Rossi <scott at tactilemedia.com>
>>> To: How to use LiveCode <use-livecode at lists.runrev.com>
>>> Subject: Re: mobileControlSet "fontname" parameter
>>> Message-ID: <AFE2F72A-B4D3-4AB5-9803-638AE3565AE5 at tactilemedia.com>
>>> 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 builder allows you to define how a custom installed font name used in your stack maps to the font name on a device.  And I may be mistaken but I believe the LiveCode folks have taken care of the default font mappings already (I believe Mark W commented on this some time back).
>>> 
>>> Not sure if this was introduced after 6.7.6 however.
>>> 
>>> Regards,
>>> 
>>> Scott Rossi
>>> Creative Director
>>> Tactile Media UX/UI Design