Just a little more info for those that are interested.
In general, it is extremely frustrating having to recreate a solution to a
problem which has clearly been solved already many times. I can list several
iOS apps which I use personally that appear to give reasonably accurate
measures of
Ah! That would have to mean that script interaction with the message box is
using send in time!
Bob S
On Nov 10, 2020, at 10:58 AM, Craig newman via use-livecode
mailto:use-livecode@lists.runrev.com>> wrote:
Not stupid. Wierder than you think.
Substitute "field 1" for the message box. Works
Weirder of Weider???
R
> On Nov 10, 2020, at 12:03 PM, Bob Sneidar via use-livecode
> wrote:
>
> Wierder than you think.
___
use-livecode mailing list
use-livecode@lists.runrev.com
Please visit this url to subscribe, unsubscribe and manage your
On 11/10/2020 2:14 AM, Richard Gaskin via use-livecode wrote:
J. Landman Gay wrote:
> On 11/9/20 3:54 PM, Richard Gaskin via use-livecode wrote:
>> And WTH happened to LC's error reporting dialog?
>
> Standalones have always reported this way on both desktop and mobile.
> It is up to the
Not stupid. Wierder than you think.
Substitute "field 1" for the message box. Works just fine, like it ought to.
Craig
-Original Message-
From: use-livecode [mailto:use-livecode-boun...@lists.runrev.com] On Behalf Of
Bob Sneidar via use-livecode
Sent: Monday, November 09, 2020 12:04 PM
On 11/10/20 1:14 AM, Richard Gaskin via use-livecode wrote:
J. Landman Gay wrote:
> On 11/9/20 3:54 PM, Richard Gaskin via use-livecode wrote:
>> And WTH happened to LC's error reporting dialog?
>
> Standalones have always reported this way on both desktop and mobile.
> It is up to the
I am switching between the forum discussion about this and here.
The plain old wait command, (without "with messages") works fine when the
target field is on another stack. So it not the fact that the field is not
"local". There is something about the message box itself, ostensibly just a
stack,
"Send in time". Hmmm
So the line "put start" is actually delayed until after the wait command,
er, starts, and gets stuck there?
And if one uses "wait with messages" that stuck command can worm its way out
and back into play?
So then LC knows when the message box is about to be the target,
I vaguely remember long time, many moons, this came up. The upshot of the
conversation is that because the message box is a stack file in it’s own right,
certain features would only work this way, or it would interfere with other
things if it didn’t work this way. I dunno, it was all all so
Yes, I had my part of the code handy from my custom error handling.
But at the time it seemed to me the tool was for edge cases where one
might encounter raw error data with no UI. It never occurred to me to
ship an application without error handling, and back then I'd never used
LC's so I
On 11/10/2020 7:45 PM, J. Landman Gay via use-livecode wrote:
But Paul's suggestion that standalones include the entire error list
isn't a bad one, though I'd like it to be optional. Users don't care
what the descriptions are and I can look them up, but some might want
those included.
I
On 11/10/20 3:28 PM, Richard Gaskin via use-livecode wrote:
But at the time it seemed to me the tool was for edge cases where one might encounter raw error
data with no UI. It never occurred to me to ship an application without error handling, and
back then I'd never used LC's so I just
J. Landman Gay jacque wrote:
> On 11/10/20 3:28 PM, Richard Gaskin via use-livecode wrote:
>> But at the time it seemed to me the tool was for edge cases where one
>> might encounter raw error data with no UI. It never occurred to me
>> to ship an application without error handling, and
>> back
Sorry, I meant execution errors. You're supposed to read my mind. I keep
telling my husband that but he doesn't always get it either. ;)
I've used the built-in error reporting mechanism in the past and it worked
well; I usually choose the email option and it works on both deaktop and
mobile.
I just saw your execution error image, I haven't seen an empty dialog
before. Did you include a prompt?
I'll try a test tomorrow.
--
Jacqueline Landman Gay | jac...@hyperactivesw.com
HyperActive Software | http://www.hyperactivesw.com
On November 11, 2020 12:55:22 AM "J. Landman Gay via
Paul Dupuis wrote:
> I imagine that they could be added to the Inclusions - if on
> automatic, use of the "scriptExecutionErrors" in your code
> would lead to automatic inclusion. If on manual, you get to
> include them or not.
FWIW it's only 29k uncompressed, 7k compressed.
--
Richard Gaskin
16 matches
Mail list logo
