Hi Kevin,
Thanks for acknowledging that you received it!
I will compile a video of the problems, but will happily schedule a zoom
and talk about some other things as well.
I should have a video compiled within 1 week, since i'll still be using it
all week long.
Thanks Kevin,
Tom
On Fri, Sep
I went back and re-did the tests, checking on the results.
The file *is* UTF8, so I need to textDecode() it; if I don't, the result
are simply wrong, and so the times are irrelevant.
1. Once it has been textDecoded(), i.e. is in internal format, and I run
my algorithm it gets the correct
In one word: DreamCard! :D
Mark Schonewille
Economy-x-Talk
KvK 50277553
VAT NL002099948B21
https://ecxtalk.nl
https://www.nt2.nu
Programming LiveCode for the Real Beginner
http://www3.economy-x-talk.com/file.php?node=programming-livecode-for-the-real-beginner
Op 2-9-2021 om 15:49 schreef
On 9/3/21 3:53 AM, Ludovic THEBAULT via use-livecode wrote:
Hello,
When I build a Windows or macOS standalone, I sometimes have several alerts that concern the "livecode's
stacks" ("answer dialog", "print chooser" ...) that are saved in the standalone (but
I don't want them to be!) and that
I'm very much hoping that Mark W might magically fix this in 9.6.5.
But in the meantime FWIW, the place where this was really hurting (in a script
that took 8 minutes under LC6, was taking 8 hours under LC9, but I've
gradually tamed it down to under an hour by buffering the large
What I liked about your email to me Tom was that it was extremely specific. You
had just a handful of issues you considered absolutely key and offered to Zoom
to show that to me. I look forward to scheduling that once I finish getting
unburried __
Kind regards,
Kevin
Kevin Miller ~
There are some good suggestions here around the Lagi, thank you. We will
certainly be exploring ways to make that experience just right in the coming
days.
Kind regards,
Kevin
Kevin Miller ~ ke...@livecode.com ~ http://www.livecode.com/
LiveCode: Develop Yourself
On 02/09/2021, 22:33,
I was wondering this too: when Lagi mentioned 'fix the IDE' I thought this
might be a reference to some of a number of usabiity snags - it didn't occur
to me that it was just speed.
I develop on a nine-year old MacBook and have never noticed a speed issue with
the IDE. I wonder if it's
I always have to double check this as well. I think the point is that LC knows
what its internal format is, but doesn't know what the source format is. So
you always have to specify the 'external' format, but never the internal one.
With that in mind, it feels (at least in my language
Excuses for my typos. Kevin ofcourse.
Met vriendelijke groet,
Erik Beugelaar
From: e.beugel...@me.com
Sent: Friday, September 3, 2021 3:39:54 PM
To: How to use LiveCode
Subject: Re: Bye, and thanks for the fish
About this I can say it is really true.
I am
About this I can say it is really true.
I am supporting LiveCode from 2012 and never had the time to program a single
word in it... but I loved the filosophy. I only did a review for Packt
Publishing. There is hope!!!
Blame me not to write any code till yet ;-) but the people behind LiveCode are
On 03/09/2021 11:07, David V Glasgow via use-livecode wrote:
Alex states that put textEncode(tWHoleText, "UTF8") into tWholeText speeds
replace up, but David B says LC internal format is UTF16. Doesn’t the 8 vs 16 difference
matter? Or matters less than other encodings?
I would regard
Following this with interest, but also a little confusion. I completely fell
into the trap of assuming you encode outgoing and decode incoming.
Alex states that put textEncode(tWHoleText, "UTF8") into tWholeText speeds
replace up, but David B says LC internal format is UTF16. Doesn’t the 8 vs
Hello,
When I build a Windows or macOS standalone, I sometimes have several alerts
that concern the "livecode's stacks" ("answer dialog", "print chooser" ...)
that are saved in the standalone (but I don't want them to be!) and that
conflict with the original stacks.
And rarely it ends with a
14 matches
Mail list logo
