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
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.
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
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
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
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 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
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
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
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
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.
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
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:
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:
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
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
17 matches
Mail list logo
