Lying in the bath, but telling the truth.
richmondmathewson at gmail.com
Wed Jun 15 12:27:16 EDT 2016
As is often the case, I was doing some *Livecode* programming
in a nice, hot bath, ably assisted by a good, strong cup of coffee
and Aly Bain playing the "St. Anne's Reel": I had to be careful not to
splash Aly's fiddle with bath water . . . but I digress.
Anyway, I was musing on my tendency to come to things later in life
than many other people, as I learnt to drive a car at 32, and so on.
Of course *set the useUnicode to true* bubbled up from somewhere near
the plug-hole . . .
Now, being, now, the owner (for a season) of an Indy licence to Livecode
it behoves me to port my Devawriter Pro to 7.1.4 or, even, 8. something
as several of my customers, having upgraded their Macintoshes to 10.11
are getting Devawriter 1.x crashing like mad.
To contextualise further; currently Devawriter Pro is being developed on
G5 Macintosh running
Livecode (that's Runtime Revolution to you) 4.5 on Mac OS 10.5.8; and is
about to be moved
on a DELL Optiplex 745 running Xubuntu 16.04.
So, obviously, I will have to set a "bot" to trawl its way through my code
and replace every incidence of *numToChar* to *numToCodePoint*, and
replace the surrogate pairs in the upcoming *Grantha* interface
with "standard" Unicode addresses. The first of which should (?) be
simple if the global search-N-replace behaves itself, the second will be a
bother, but nothing insurmountable.
Anyway; to cut a short story long, as is my wont: to *set the useUnicode
what is unclear from the Livecode 7.x documentation is if this is now
More information about the Use-livecode