The stack is, in fact, password protected. But we get other error
reports where the info is filled in, which is more usual. Weird.
On 6/18/19 1:24 PM, Ralph DiMola via use-livecode wrote:
I've seen the "empty error dialog" on password protected stacks.
Ralph DiMola
IT Director
Evergreen Inform
I see this regularly and have for a long time. Not sure what causes it. Seems
to go away if I close and re-open the script editor.
Bob S
> On Jun 18, 2019, at 08:41 , Dar Scott Consulting via use-livecode
> wrote:
>
> A hint for bounty hunters:
> It seems to me I have seen this outside of L
Just got this today... API 28 will be required for new apps on 8/1/2019 and
updated app by 8/1/2019. Message from Google Play below. QCC 22194
submitted.
Warnings
Your app currently targets API level 26 and must target at least API level
28 to ensure it is built on the latest APIs opt
I've seen the "empty error dialog" on password protected stacks.
Ralph DiMola
IT Director
Evergreen Information Services
rdim...@evergreeninfo.net
-Original Message-
From: use-livecode [mailto:use-livecode-boun...@lists.runrev.com] On Behalf
Of J. Landman Gay via use-livecode
Sent: Tuesda
Some users are getting empty script error dialogs in a standalone. The
errors are infrequent, sporadic, always in different places in the app,
not repeatable. When they happen, the user can repeat their last action
and it works without error. We get these reports because the standalone
has erro
Curt Ford wrote:
A client needs to make minor updates to the text in a number of modules
I've created over several years. To eliminate the back-and-forth of
corrections and proofs, he's asked about making the changes himself in
LiveCode. (He's never used LiveCode and doesn't have a copy.)
Sim
What about community plus - or is that not a perpetual licence either?
Lagi
On Tue, 18 Jun 2019 at 17:15, Curt Ford via use-livecode <
use-livecode@lists.runrev.com> wrote:
> Dear Heather,
>
> Thanks for the clarification. This is the answer I'd basically expected,
> but it'll be easier for me t
Dear Heather,
Thanks for the clarification. This is the answer I'd basically expected,
but it'll be easier for me to steer the client in a different direction
with the official word from you at LiveCode, so this is helpful.
(They had originally suggested using Splashtop to try and make the
u
Whoops. That is a couple years old. I need to get my coffee.
> On Jun 18, 2019, at 9:41 AM, Dar Scott Consulting via use-livecode
> wrote:
>
> A hint for bounty hunters:
> It seems to me I have seen this outside of LiveCode. Perhaps the bug is a
> common one.
> I'm on a Mac.
>
> I don't trus
A hint for bounty hunters:
It seems to me I have seen this outside of LiveCode. Perhaps the bug is a
common one.
I'm on a Mac.
I don't trust my memory; YMMD.
> On Aug 14, 2017, at 5:38 PM, RunRevPlanet via use-livecode
> wrote:
>
> Hi,
>
> Over at LiveCode Quality Control Centre (QCC) the
On 6/18/2019 9:01 AM, Trevor DeVore via use-livecode wrote:
On Tue, Jun 18, 2019 at 6:28 AM Paul Dupuis via use-livecode <
use-livecode@lists.runrev.com> wrote:
I should learn how to contribute to updating documentation myself, but I
have tried setting up GIT on Windows twice without success (o
On Tue, Jun 18, 2019 at 6:28 AM Paul Dupuis via use-livecode <
use-livecode@lists.runrev.com> wrote:
>
> I should learn how to contribute to updating documentation myself, but I
> have tried setting up GIT on Windows twice without success (obviously I
> am doing something basic wrong).
The good
On 6/18/2019 3:29 AM, Mark Waddingham via use-livecode wrote:
On 2019-06-17 22:09, Paul Dupuis via use-livecode wrote:
Folks (those who may have an interest at least):
I just filed a bug: https://quality.livecode.com/show_bug.cgi?id=22192
Does this ("Private" NOT Unicode aware) seem like a Fea
Dear Curt,
Thanks for asking. This would be prohibited by this clause in your EULA:
"f) Any Created Software built with this Licensed Edition is fully functional
and allows users full access to the entire LiveCode feature set. Where the
Created Software is a standalone executable, the end user
On 2019-06-17 22:09, Paul Dupuis via use-livecode wrote:
Folks (those who may have an interest at least):
I just filed a bug: https://quality.livecode.com/show_bug.cgi?id=22192
Does this ("Private" NOT Unicode aware) seem like a Feature or a Bug?
This is a documentation bug really - you can o
15 matches
Mail list logo
