LiveCode Forums.

When I compile a standalone program I am creating, I am getting a debug error that says:
The Script Editor of this any card in the Stack does not have any lines of code. The only code is on the Stack Script Editor. I have seen this error before on other applications that I am working on and have not been able to figure this out. I am getting this error when I send the application to other people as I do not see this error on the computer that has LiveCode installed on it.

I also noticed that the Executing Time does not change and is always the same time.

"... the shore name of...."
Did you mean short???

Simon

Yes that is correct.

Executing at 2:58:29 PM
Type
Object card id 1002
Line put "Object" & tab & the short name of tObject & cr after tErrorString
Hint preOpenCard


Which this line is no where in my scripts of either a card or a stack.

gpearson wrote:Yes that is correct.

Which this line is no where in my scripts of either a card or a stack.

That would be very odd.
Have you tried a Find and Replace making sure you have selected This stack and all substacks?
Tip, just use "put "Object" & tab & the short name of tObject & cr after tErrorString"

Simon

Simon wrote:That would be very odd.
Have you tried a Find and Replace making sure you have selected This stack and all substacks?
Tip, just use "put "Object" & tab & the short name of tObject & cr after tErrorString"
Simon

In the Application Browser I loaded up each of the stacks for this project and in the Find/Replace I searched for various words that was displayed in the error message. Each time I searched for a term, I got back 0 Objects Found. I even checked all of the 6 buttons (Name, Script, Custom, Field Text, Button Text, All Other) with the same result of 0 Objects Found. Another search I messed with the IN dropdown and selected This stack file and its stack files, All stack files in a folder, All Open stacks, All Open Stack Files, etc all producing the same result of 0 Objects found. I searched for & tab &, tObject, tErrorString, "Object" which all produced the same result of 0 objects found.

To make sure that I was using this correctly, I did some searching on variables that I used in my application and seen how it displayed the results.

I even got this debug message on another application that I am working on as well. It is just strange that each time this happens it is with the same timestamp and happens in the Commercial Edition of Livecode.

I just loaded up the stack in the Community Edition and received the same error message with the same timestamp. I just do not get it as I do not have the line it says anywhere in my script on cards or stacks.

Anyone know if this got resolved ?

Three years later is it has reappeared - for me at least.
Precisely the same error report and that code is nowhere in my application.

Any pointers would be appreciate as this is stopping me from publishing my app - cheers.

PS from a search this bug seems to go back nearly 10 years.

This looks like an error from the IDE library that reports a script error. Whatever object is causing the error can't be identified to the library, so it can't report what's wrong. The exact phrase won't be in your own scripts.

One thing to try is to add an errorDialog handler to your stack. That bypasses LC's error management and reports the problem directly to your script. When that happens you will see a series of numbers which you will need to interpret yourself. See errorDialog in the dictionary for what the numbers mean. If you want a quick way to decode them, download "LiveCode Error Lookup" from the Sample Stacks area in the LC toolbar, since it accomodates any version of LC. The location of the error codes mentioned in the dictionary is no longer accurate for LC 8.

Thank you Jacque, that's a very informative response and a new aspect of LC for me, I will have a go tomorrow.

I've pinned the error to a very specific situation - I'm testing a handler to adjust my stack's rectangle in response to a desktop changed message - this error is thrown up when I have a substack open along with the mainstack. I'm looking forward to seeing what gets reported as I'm at a loss to find a fault.
Cheers.