Release 6.7.5 / 7.0.5
Sebastien Nouat
sebastien.nouat at livecode.com
Fri May 15 10:14:59 EDT 2015
On 15/05/2015 14:34, Mike Kerner wrote:
> "The only change from the RC 3 releases is in what we believe was the cause
> of the startup slowdown on iOS 8.1+, despite the font mapping fix. No bug
> fix note has been added since it was another aspect of the bug 14116."
> What does THAT mean? Is manual font mapping still required?
>
> On Fri, May 15, 2015 at 9:16 AM, Sebastien Nouat <
> sebastien.nouat at livecode.com> wrote:
>
>> Dear List Members,
>>
>> We are pleased to announce the release of LiveCode 6.7.5 Stable and 7.0.5
>> Stable: all the bug fixes added from LiveCode 6.7.5 RC 1 / 7.0.5 RC 1 are
>> now considered as stable for both versions.
>>
>> The only change from the RC 3 releases is in what we believe was the cause
>> of the startup slowdown on iOS 8.1+, despite the font mapping fix. No bug
>> fix note has been added since it was another aspect of the bug 14116.
>>
>> **Getting the Release**
>> To get the release please select "check for updates" from the "help" menu
>> in the product or download the installer directly at:
>> http://downloads.livecode.com
>>
>> *6.7.6 RC 1 / 7.0.6 RC 1*
>> The progress of the bug fix merging can be followed on GitHub:
>> - 6.7.6 RC 1: https://github.com/runrev/livecode/milestones/6.7.6-rc-1
>> - 7.0.6 RC 1: https://github.com/runrev/livecode/milestones/7.0.6-rc-1
>>
>> The next maintenance builds are expected to be released within a 2-week
>> span.
>>
>> Warm regards,
>>
>> The LiveCode Team
>>
>> _______________________________________________
>> use-livecode mailing list
>> use-livecode at lists.runrev.com
>> Please visit this url to subscribe, unsubscribe and manage your
>> subscription preferences:
>> http://lists.runrev.com/mailman/listinfo/use-livecode
>>
>
>
Hi Mike,
The issue tackled in the Stable releases was internal, and not something
the font mapping could fix.
So yes, adding a custom font mapping file is still needed for any custom
font that you add in your app.
--
Sébastien Nouat
LiveCode Development Team
More information about the use-livecode
mailing list