Windows startup issue

classic Classic list List threaded Threaded
17 messages Options
Reply | Threaded
Open this post in threaded view
|

Windows startup issue

J. Landman Gay via use-livecode
I have a customer who is having a weird issue with a Windows app built in LC (9.6.1). It worked fine for about a month, it works fine here for me all the time and it works fine for all our other customers.

On startup is begins to launch then gets a bunch of errors:

269,76,1
262,67,1
252,67,1
241,67,1
353,0,0
573,68,1
253,68,1
241,67,1
353,0,0

But it only happens for this *one* person. They have the latest version of Windows 10, have tried multiple installs and uninstalls, turned off virus software, etc. I have downloaded from the same link I've sent him, installed and it runs fine for me and all our other customers.

I know it's along shot, but has anybody seen anything like this or offer any advice?
---
Marty
_______________________________________________
use-livecode mailing list
[hidden email]
Please visit this url to subscribe, unsubscribe and manage your subscription preferences:
http://lists.runrev.com/mailman/listinfo/use-livecode
Reply | Threaded
Open this post in threaded view
|

Re: Windows startup issue

J. Landman Gay via use-livecode
The first things is to determine what the error codes mean. I forget off
teh top of my head, but I things of the first 2 numbers one is a line
number and the other an error code?

Hopefully someone can chime in who knows for sure. Knowing the errors
will tell you more about what the likely cause may be.

I suspect it is some sort of permissions issue. In all most all
instances where we have run into a weird startup issue with just one
customer, it has turned out to be permissions related. For example, does
you application create any preferences or license files or temporary
files? Or try to save anything to disk behind the scenes (i.e. not a
user driven file save dialog)? If so, chances are the place you are
trying to write to is read-only.

It could be many other things, but this has been the most common issue
like this we've run into.


On 11/9/2020 4:10 PM, Marty Knapp via use-livecode wrote:

> I have a customer who is having a weird issue with a Windows app built in LC (9.6.1). It worked fine for about a month, it works fine here for me all the time and it works fine for all our other customers.
>
> On startup is begins to launch then gets a bunch of errors:
>
> 269,76,1
> 262,67,1
> 252,67,1
> 241,67,1
> 353,0,0
> 573,68,1
> 253,68,1
> 241,67,1
> 353,0,0
>
> But it only happens for this *one* person. They have the latest version of Windows 10, have tried multiple installs and uninstalls, turned off virus software, etc. I have downloaded from the same link I've sent him, installed and it runs fine for me and all our other customers.
>
> I know it's along shot, but has anybody seen anything like this or offer any advice?
> ---
> Marty
> _______________________________________________
> use-livecode mailing list
> [hidden email]
> Please visit this url to subscribe, unsubscribe and manage your subscription preferences:
> http://lists.runrev.com/mailman/listinfo/use-livecode


_______________________________________________
use-livecode mailing list
[hidden email]
Please visit this url to subscribe, unsubscribe and manage your subscription preferences:
http://lists.runrev.com/mailman/listinfo/use-livecode
Reply | Threaded
Open this post in threaded view
|

Re: Windows startup issue

J. Landman Gay via use-livecode
Right, the first number is the error code and the second is the line number in the script. It
does look like a permissions error:

269 Operators is: error in right operand
262 import: can't open file, mask file or display
252 if-then: error in condition expression
241 Handler: error in statement
353 Object Name:
573 Handler: can't find handler
253 if-then: error in statement
241 Handler: error in statement
353 Object Name:

The top line is the one that is usually the main error, the second line in this case indicates
a file couldn't be opened. The remainder of the lines indicate the message path that led to the
error, in reverse order.

The list was generated by a free utility called "LiveCode Lookup Errors" which you can find in
Sample Stacks in LC's tool bar.


On 11/9/20 3:27 PM, Paul Dupuis via use-livecode wrote:

> The first things is to determine what the error codes mean. I forget off teh top of my head,
> but I things of the first 2 numbers one is a line number and the other an error code?
>
> Hopefully someone can chime in who knows for sure. Knowing the errors will tell you more about
> what the likely cause may be.
>
> I suspect it is some sort of permissions issue. In all most all instances where we have run
> into a weird startup issue with just one customer, it has turned out to be permissions related.
> For example, does you application create any preferences or license files or temporary files?
> Or try to save anything to disk behind the scenes (i.e. not a user driven file save dialog)? If
> so, chances are the place you are trying to write to is read-only.
>
> It could be many other things, but this has been the most common issue like this we've run into.
>
>
> On 11/9/2020 4:10 PM, Marty Knapp via use-livecode wrote:
>> I have a customer who is having a weird issue with a Windows app built in LC (9.6.1). It
>> worked fine for about a month, it works fine here for me all the time and it works fine for
>> all our other customers.
>>
>> On startup is begins to launch then gets a bunch of errors:
>>
>> 269,76,1
>> 262,67,1
>> 252,67,1
>> 241,67,1
>> 353,0,0
>> 573,68,1
>> 253,68,1
>> 241,67,1
>> 353,0,0
>>
>> But it only happens for this *one* person. They have the latest version of Windows 10, have
>> tried multiple installs and uninstalls, turned off virus software, etc. I have downloaded
>> from the same link I've sent him, installed and it runs fine for me and all our other customers.
>>
>> I know it's along shot, but has anybody seen anything like this or offer any advice?
>> ---
>> Marty
>> _______________________________________________
>> use-livecode mailing list
>> [hidden email]
>> Please visit this url to subscribe, unsubscribe and manage your subscription preferences:
>> http://lists.runrev.com/mailman/listinfo/use-livecode
>
>
> _______________________________________________
> use-livecode mailing list
> [hidden email]
> Please visit this url to subscribe, unsubscribe and manage your subscription preferences:
> http://lists.runrev.com/mailman/listinfo/use-livecode


--
Jacqueline Landman Gay         |     [hidden email]
HyperActive Software           |     http://www.hyperactivesw.com

_______________________________________________
use-livecode mailing list
[hidden email]
Please visit this url to subscribe, unsubscribe and manage your subscription preferences:
http://lists.runrev.com/mailman/listinfo/use-livecode
Reply | Threaded
Open this post in threaded view
|

Re: Windows startup issue

J. Landman Gay via use-livecode
In reply to this post by J. Landman Gay via use-livecode
Marty Knapp wrote:

> I have a customer who is having a weird issue with a Windows app built in LC (9.6.1). It worked fine for about a month, it works fine here for me all the time and it works fine for all our other customers.
>
> On startup is begins to launch then gets a bunch of errors:
>
> 269,76,1
> 262,67,1
> 252,67,1
> 241,67,1
> 353,0,0
> 573,68,1
> 253,68,1
> 241,67,1
> 353,0,0

Where do those appear?

And WTH happened to LC's error reporting dialog?

I see more and more error info reports like this in recent years.
Presenting anything like this to either devs or end-users is a horrible
experience.

We can do better.

--
  Richard Gaskin
  Fourth World Systems
  Software Design and Development for the Desktop, Mobile, and the Web
  ____________________________________________________________________
  [hidden email]                http://www.FourthWorld.com

_______________________________________________
use-livecode mailing list
[hidden email]
Please visit this url to subscribe, unsubscribe and manage your subscription preferences:
http://lists.runrev.com/mailman/listinfo/use-livecode
Reply | Threaded
Open this post in threaded view
|

Re: Windows startup issue

J. Landman Gay via use-livecode
The errors show up in a dialog window.

The section of code referenced is just checking the status a a custom font. On Windows we install the font with an Inno installer (and on Mac we just start using an embedded font). Here's my code with the line numbers added. 67 being referenced several times in the error:

67) if "MyCustomeFontName" is in the fontNames then
68)   put "installed" into tFontStatus
69) else put "loaded" into tFontStatus

---
Marty

> On Nov 9, 2020, at 1:54 PM, Richard Gaskin via use-livecode <[hidden email]> wrote:
>
> Marty Knapp wrote:
>
>> I have a customer who is having a weird issue with a Windows app built in LC (9.6.1). It worked fine for about a month, it works fine here for me all the time and it works fine for all our other customers.
>> On startup is begins to launch then gets a bunch of errors:
>> 269,76,1
>> 262,67,1
>> 252,67,1
>> 241,67,1
>> 353,0,0
>> 573,68,1
>> 253,68,1
>> 241,67,1
>> 353,0,0
>
> Where do those appear?
>
> And WTH happened to LC's error reporting dialog?
>
> I see more and more error info reports like this in recent years. Presenting anything like this to either devs or end-users is a horrible experience.
>
> We can do better.
>
> --
> Richard Gaskin
> Fourth World Systems
> Software Design and Development for the Desktop, Mobile, and the Web
> ____________________________________________________________________
> [hidden email]                http://www.FourthWorld.com
>


_______________________________________________
use-livecode mailing list
[hidden email]
Please visit this url to subscribe, unsubscribe and manage your subscription preferences:
http://lists.runrev.com/mailman/listinfo/use-livecode
Reply | Threaded
Open this post in threaded view
|

Re: Windows startup issue

J. Landman Gay via use-livecode
In reply to this post by J. Landman Gay via use-livecode
On 11/9/20 3:54 PM, Richard Gaskin via use-livecode wrote:
> Where do those appear?
>
> 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 developer
to include the translated references if they want to see those. Generally I don't bother, I
provide the optional built-in ability to send email to support or save a file. I can translate
the numbers myself since the meanings usually mean nothing to the end-user anyway.

The IDE does still translate for us.

--
Jacqueline Landman Gay         |     [hidden email]
HyperActive Software           |     http://www.hyperactivesw.com

_______________________________________________
use-livecode mailing list
[hidden email]
Please visit this url to subscribe, unsubscribe and manage your subscription preferences:
http://lists.runrev.com/mailman/listinfo/use-livecode
Reply | Threaded
Open this post in threaded view
|

Re: Windows startup issue

J. Landman Gay via use-livecode
In reply to this post by J. Landman Gay via use-livecode
That should work, I don't see anything in those three lines that would fail -- except maybe if
"the fontnames" couldn't be retrieved on that machine. It almost looks like the engine thinks
"the fontnames" is a custom function since it's reporting it can't find the handler.

I'm not sure how you'd fix that. I suppose you could wrap the clause in a "try" structure and
if it errors, assume the font isn't there.


On 11/9/20 4:10 PM, Marty Knapp via use-livecode wrote:

> The errors show up in a dialog window.
>
> The section of code referenced is just checking the status a a custom font. On Windows we install the font with an Inno installer (and on Mac we just start using an embedded font). Here's my code with the line numbers added. 67 being referenced several times in the error:
>
> 67) if "MyCustomeFontName" is in the fontNames then
> 68)   put "installed" into tFontStatus
> 69) else put "loaded" into tFontStatus
>
> ---
> Marty
>
>> On Nov 9, 2020, at 1:54 PM, Richard Gaskin via use-livecode <[hidden email]> wrote:
>>
>> Marty Knapp wrote:
>>
>>> I have a customer who is having a weird issue with a Windows app built in LC (9.6.1). It worked fine for about a month, it works fine here for me all the time and it works fine for all our other customers.
>>> On startup is begins to launch then gets a bunch of errors:
>>> 269,76,1
>>> 262,67,1
>>> 252,67,1
>>> 241,67,1
>>> 353,0,0
>>> 573,68,1
>>> 253,68,1
>>> 241,67,1
>>> 353,0,0
>>
>> Where do those appear?
>>
>> And WTH happened to LC's error reporting dialog?
>>
>> I see more and more error info reports like this in recent years. Presenting anything like this to either devs or end-users is a horrible experience.
>>
>> We can do better.
>>
>> --
>> Richard Gaskin
>> Fourth World Systems
>> Software Design and Development for the Desktop, Mobile, and the Web
>> ____________________________________________________________________
>> [hidden email]                http://www.FourthWorld.com
>>
>
>
> _______________________________________________
> use-livecode mailing list
> [hidden email]
> Please visit this url to subscribe, unsubscribe and manage your subscription preferences:
> http://lists.runrev.com/mailman/listinfo/use-livecode
>


--
Jacqueline Landman Gay         |     [hidden email]
HyperActive Software           |     http://www.hyperactivesw.com

_______________________________________________
use-livecode mailing list
[hidden email]
Please visit this url to subscribe, unsubscribe and manage your subscription preferences:
http://lists.runrev.com/mailman/listinfo/use-livecode
Reply | Threaded
Open this post in threaded view
|

Re: Windows startup issue

J. Landman Gay via use-livecode
In reply to this post by J. Landman Gay via use-livecode
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 developer to include the translated references if
 > they want to see those. Generally I don't bother, I provide the
 > optional built-in ability to send email to support or save a file.
 > I can translate the numbers myself since the meanings usually mean
 > nothing to the end-user anyway.

I've been using my own error-reporting for so long I can't recall seeing
the default standalone handling.

I have made a couple of quickies where I just used LC's error reporting,
but clumsy as that design is at least the output from the "Send Report"
button is more useful than the raw list of triplet integers.

How has such ungraceful error handling become acceptable?

Why is the least useful thing the easiest for new developers to do?

Shouldn't it be easy for LC devs to deliver a great application experience?

--
  Richard Gaskin
  Fourth World Systems
  Software Design and Development for the Desktop, Mobile, and the Web
  ____________________________________________________________________
  [hidden email]                http://www.FourthWorld.com


_______________________________________________
use-livecode mailing list
[hidden email]
Please visit this url to subscribe, unsubscribe and manage your subscription preferences:
http://lists.runrev.com/mailman/listinfo/use-livecode
Reply | Threaded
Open this post in threaded view
|

Re: Windows startup issue

J. Landman Gay via use-livecode
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 developer to include the translated references if
>  > they want to see those. Generally I don't bother, I provide the
>  > optional built-in ability to send email to support or save a file.
>  > I can translate the numbers myself since the meanings usually mean
>  > nothing to the end-user anyway.
>
> I've been using my own error-reporting for so long I can't recall seeing the default standalone
> handling.
>
> I have made a couple of quickies where I just used LC's error reporting, but clumsy as that
> design is at least the output from the "Send Report" button is more useful than the raw list of
> triplet integers. >
> How has such ungraceful error handling become acceptable?
>
> Why is the least useful thing the easiest for new developers to do?
>
> Shouldn't it be easy for LC devs to deliver a great application experience?
>

I can't remember a time when it *didn't* report the triplets outside of the IDE. That's why you
and I wrote the Error Lookup stack. ;)

--
Jacqueline Landman Gay         |     [hidden email]
HyperActive Software           |     http://www.hyperactivesw.com

_______________________________________________
use-livecode mailing list
[hidden email]
Please visit this url to subscribe, unsubscribe and manage your subscription preferences:
http://lists.runrev.com/mailman/listinfo/use-livecode
Reply | Threaded
Open this post in threaded view
|

Re: Windows startup issue

J. Landman Gay via use-livecode
In reply to this post by J. Landman Gay via use-livecode
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 developer to include the translated references if
> > they want to see those. Generally I don't bother, I provide the
> > optional built-in ability to send email to support or save a file.
> > I can translate the numbers myself since the meanings usually mean
> > nothing to the end-user anyway.
>
> I've been using my own error-reporting for so long I can't recall
> seeing the default standalone handling.
>
> I have made a couple of quickies where I just used LC's error
> reporting, but clumsy as that design is at least the output from the
> "Send Report" button is more useful than the raw list of triplet
> integers.
>
> How has such ungraceful error handling become acceptable?
>
> Why is the least useful thing the easiest for new developers to do?
>
> Shouldn't it be easy for LC devs to deliver a great application
> experience?
>

One big thing that LC could do to let developer's improve error handling
and standalone troubleshooting would be to include the
"scriptExecutionErrors" in Standalones. I know it is along list, but
would it really add that many more bytes to Standalones relative to the
current engine size?

I know you can replicate having the error text present by copying the
scriptExecutionErrors to a custom property in your standalone, but then
you have to be sure to update it with each engine release. To just have
it included when you build a standalone would be much better.


_______________________________________________
use-livecode mailing list
[hidden email]
Please visit this url to subscribe, unsubscribe and manage your subscription preferences:
http://lists.runrev.com/mailman/listinfo/use-livecode
Reply | Threaded
Open this post in threaded view
|

Re: Windows startup issue

J. Landman Gay via use-livecode
In reply to this post by J. Landman Gay via use-livecode
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 just assumed it was at least as good as my own.

Since then I've learned that providing any UI for error handling at all
is turned OFF by default.

Off.

As in, "Let's make providing a near-useless solution the thing we guide
new developers to deliver to their customers."

I was brainstorming with Mark Wieder a few weeks ago about adding static
analysis to IDE error reporting, aiming for something closer to the
helpful guidance Clang provides.  Even if we did little more than show
the var values causing something to trip up, it would save tremendous
time. Aiming higher seems useful. Other tools are getting better all the
time.

And that's for just the IDE. If LC devs are comfortable with
state-of-the-art-circa-2003, what we have in the IDE is at least adequate.

For end-users, though, that's where we really want to shine. It's where
we NEED to shine.

We want new devs picking up LC to look like heroes, and to deliver that
high-quality experience with less effort than they'd put in with other
tools.

That's the point. That's why we use LC.

If we can't do that, why are we here?

Everything is undergoing perpetual change. With products there's new
customer acquisition on the one side, and attrition on the other. As
long as change is happening, why not direct some of it? Why not aim a
little higher, to reduce attrition while attracting new users? Sure,
we'd all like to see that happen, but a hundred paper cuts unattended
undermine that goal.

And as paper cuts go, error handling cuts deep. It only happen when
something went wrong. It's an especially sensitive moment in the user
journey.  We can either lose the user's trust, or retain it.  So much
about the confidence end-users have in our work hinges on how we handle
when things go wrong.

Why not aim higher than the least useful experience?

Or to put this more clearly:

254,11,34
301,2,43
262,67,1
12,22,1
132,1,44
73,68,1
241,67,1
353,0,0
433,2,0
201,0,0
88,3,22
322,4,20
568,22,0

--
  Richard Gaskin
  Fourth World Systems



J. Landman Gay wrote:

> 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 developer to include the translated references if
>>  > they want to see those. Generally I don't bother, I provide the
>>  > optional built-in ability to send email to support or save a file.
>>  > I can translate the numbers myself since the meanings usually mean
>>  > nothing to the end-user anyway.
>>
>> I've been using my own error-reporting for so long I can't recall seeing the default standalone
>> handling.
>>
>> I have made a couple of quickies where I just used LC's error reporting, but clumsy as that
>> design is at least the output from the "Send Report" button is more useful than the raw list of
>> triplet integers. >
>> How has such ungraceful error handling become acceptable?
>>
>> Why is the least useful thing the easiest for new developers to do?
>>
>> Shouldn't it be easy for LC devs to deliver a great application experience?
>>
>
> I can't remember a time when it *didn't* report the triplets outside of the IDE. That's why you
> and I wrote the Error Lookup stack. ;)
>
> --
> Jacqueline Landman Gay         |     jacque at hyperactivesw.com
> HyperActive Software           |     http://www.hyperactivesw.com


_______________________________________________
use-livecode mailing list
[hidden email]
Please visit this url to subscribe, unsubscribe and manage your subscription preferences:
http://lists.runrev.com/mailman/listinfo/use-livecode
Reply | Threaded
Open this post in threaded view
|

Re: Windows startup issue

J. Landman Gay via use-livecode
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 assumed it was at least as good as my own.


We shouldn't confuse our own error handling with compiler errors. I include extensive logging
and error reporting when "the result" or something similar in my scripts fail. As developers,
it's our job to do that.

The cryptic numbers only occur when a compiler error happens. A well-tested stack won't have
many of those by the time it's distributed. The one in question here is an odd one-off which
only happened for one user.

So it sounds like you're asking LC to translate its compiler errors in standalones. These are
infrequent enough for me that the numbers aren't much of a concern; they largely happen during
development and those are translated for us. 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.


--
Jacqueline Landman Gay         |     [hidden email]
HyperActive Software           |     http://www.hyperactivesw.com


_______________________________________________
use-livecode mailing list
[hidden email]
Please visit this url to subscribe, unsubscribe and manage your subscription preferences:
http://lists.runrev.com/mailman/listinfo/use-livecode
Reply | Threaded
Open this post in threaded view
|

Re: Windows startup issue

J. Landman Gay via use-livecode
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 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.


_______________________________________________
use-livecode mailing list
[hidden email]
Please visit this url to subscribe, unsubscribe and manage your subscription preferences:
http://lists.runrev.com/mailman/listinfo/use-livecode
Reply | Threaded
Open this post in threaded view
|

Re: Windows startup issue

J. Landman Gay via use-livecode
In reply to this post by J. Landman Gay via use-livecode
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 then I'd never used LC's so I just assumed it was at least as
 >> good as my own.
 >
 > We shouldn't confuse our own error handling with compiler errors. I
 > include extensive logging and error reporting when "the result" or
 > something similar in my scripts fail. As developers,
 > it's our job to do that.

Of course, which is why I've not been able to find the recipe for seeing
these lists of error info people keep mentioning here and in the forums.

But given the number of times they're cited, it's clear a lot of people
are encountering them unexpectedly.


 > The cryptic numbers only occur when a compiler error happens. A well-
 > tested stack won't have many of those by the time it's distributed.
 > The one in question here is an odd one-off which only happened for
 > one user.

Compiler errors or execution errors?

If this is limited to compiler errors I'm wondering what went wrong
earlier in the workflow that so many people are able to close their
scripts and move on without noticing that the Script Editor has been
trying to get their attention, and that the scripts don't run at all
until they're compiled.

The Dictionary says compilation errors are only reported in "the result"
after an unsuccessful attempt to set the script of an object (apparently
the old scriptParsingError message is no longer sent, though oddly
enough a handler for it remains in the IDE).

Do we have that many people writing self-modifying code?


Execution errors are what I was referring to in my last post.

As thorough as we may be, in any sufficiently complex code base there's
likely to be some error condition we didn't explicitly code for.

Our choices are to handle those ourselves with an errorDialog handler,
or remember to click the checkbox in the Standalone Builder to use LC's
Execution Error reporting stack.

If you don't do either, errors fail silently (at least when I just
tested it here with a simple test stack).

But oddly, when I include LC's Execution Error dialog, the result was,
shall we say, not as expected:
http://fourthworld.net/lc/lc-err-dialog.png

That's in v9.6.1. Their exec err stack used to work. I wonder when it broke.


So for exec errors, at a minimum it would be very helpful to have the
Execution Error reporting window option set to be included by default in
new standalones, so that it can become possible for folks to know what
happened when behavior starts getting wonky.

Later on I have a wish list of improvements for that dialog, but having
some means of knowing when an error occurs in a form suitable for
end-users seems a reasonable minimum to expect.


Hard to say what's in play in this thread (and perhaps others like it)
where the only reported symptom is a list of error info, since Marty's
description was:

    "The errors show up in a dialog window."

Is that an answer dialog?  Is that an LC lib that does that, something
Marty wrote, or...?

How can I get a standalone to show me a list of error info like that?

Whatever that recipe is, that's the thing we'll want to fix.



 > So it sounds like you're asking LC to translate its compiler errors
 > in standalones. These are infrequent enough for me that the numbers
 > aren't much of a concern; they largely happen during development and
 > those are translated for us. But Paul's suggestion that standalones
 > include the entire error list isn't a bad one, though I'd like it to
 > be optional.

It looks they did that some time ago - kinda.  The revIDELookupError
function in "revIDELibrary" includes this tantalizing line:

     get line tCode of the scriptExecutionErrors

So it looks like a built-in function now, right?

Not quite: doesn't work in a standalone.

I'm guessing they copy the latest value that returns into their
Execution Error dialog when you add that checkbox, so custom things can
do the same. Still an extra step, but much easier than the old method we
used to use of having to remember which custom property - and before
that, which hidden field -- of which stack that list was stored in.

But that's for seasoned pros willing to roll their own.

First we need to figure out how people are unexpectedly seeing lists of
raw error info and turn that into a more useful experience.

Then we can look at enhancing LC's Execution Error dialog, and have the
default be on rather than off.

After that there are a hundred other paper cuts, but let's see if we can
knock these off first.

--
  Richard Gaskin
  Fourth World Systems
  Software Design and Development for the Desktop, Mobile, and the Web
  ____________________________________________________________________
  [hidden email]                http://www.FourthWorld.com



_______________________________________________
use-livecode mailing list
[hidden email]
Please visit this url to subscribe, unsubscribe and manage your subscription preferences:
http://lists.runrev.com/mailman/listinfo/use-livecode
Reply | Threaded
Open this post in threaded view
|

Re: Windows startup issue

J. Landman Gay via use-livecode
In reply to this post by J. Landman Gay via use-livecode
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
  Fourth World Systems
  Software Design and Development for the Desktop, Mobile, and the Web
  ____________________________________________________________________
  [hidden email]                http://www.FourthWorld.com

_______________________________________________
use-livecode mailing list
[hidden email]
Please visit this url to subscribe, unsubscribe and manage your subscription preferences:
http://lists.runrev.com/mailman/listinfo/use-livecode
Reply | Threaded
Open this post in threaded view
|

Re: Windows startup issue

J. Landman Gay via use-livecode
In reply to this post by J. Landman Gay via use-livecode
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 wasn't aware it was broken. I think it would be difficult to
include that automatically since it requires some input, at least an email
address and ideally a prompt. I suppose a default file could be generated
but the user wouldn't know it unless they were notified.


Lately I've been catching the errorDialog message and handling it myself.
But thinking back to the built-in method, I think it did include the
definitions. It's been a while since we got one of those, but I vaguely
recall reading an email and understanding the problem without needing to
look up any numbers. In that case we just need to include error handling in
standalone settings, which apparently adds the definitions to the app.

--
Jacqueline Landman Gay | [hidden email]
HyperActive Software | http://www.hyperactivesw.com
On November 10, 2020 8:34:57 PM Richard Gaskin via use-livecode
<[hidden email]> wrote:
>
> Compiler errors or execution errors?




_______________________________________________
use-livecode mailing list
[hidden email]
Please visit this url to subscribe, unsubscribe and manage your subscription preferences:
http://lists.runrev.com/mailman/listinfo/use-livecode
Reply | Threaded
Open this post in threaded view
|

Re: Windows startup issue

J. Landman Gay via use-livecode
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 | [hidden email]
HyperActive Software | http://www.hyperactivesw.com
On November 11, 2020 12:55:22 AM "J. Landman Gay via use-livecode"
<[hidden email]> wrote:

> 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 wasn't aware it was broken. I think it would be difficult to
> include that automatically since it requires some input, at least an email
> address and ideally a prompt. I suppose a default file could be generated
> but the user wouldn't know it unless they were notified.
>
>
> Lately I've been catching the errorDialog message and handling it myself.
> But thinking back to the built-in method, I think it did include the
> definitions. It's been a while since we got one of those, but I vaguely
> recall reading an email and understanding the problem without needing to
> look up any numbers. In that case we just need to include error handling in
> standalone settings, which apparently adds the definitions to the app.
>
> --
> Jacqueline Landman Gay | [hidden email]
> HyperActive Software | http://www.hyperactivesw.com
> On November 10, 2020 8:34:57 PM Richard Gaskin via use-livecode
> <[hidden email]> wrote:
>>
>> Compiler errors or execution errors?
>
>
>
>
> _______________________________________________
> use-livecode mailing list
> [hidden email]
> Please visit this url to subscribe, unsubscribe and manage your
> subscription preferences:
> http://lists.runrev.com/mailman/listinfo/use-livecode




_______________________________________________
use-livecode mailing list
[hidden email]
Please visit this url to subscribe, unsubscribe and manage your subscription preferences:
http://lists.runrev.com/mailman/listinfo/use-livecode