Don't understand this error message

[micmac]

Hi there

Using CE 9.6.3

Im seeing this error message:

Skærmbillede 2022-01-12 kl. 16.31.03.png (55.31 KiB) Viewed 9664 times

I do understand recursion problems, but the handler mentioned is not mine (it starts with rev)

The stack is an old stack that worked fine in macOS High Sierra.
I have recently changed to macOS Catalina.

What do you make of it?

Thanks
Michael

[richmond62]

All I can think of is that there is something somewhere going round in ever-decreasing circles,
amd most likely it is a script.

Been there, done that . . .

https://www.mail-archive.com/use-liveco ... 86523.html

[micmac]

Thank you Richmond!

...and thank you for quoting the listinfo thread.

There was a lot of good information in there.



Michael

[OpenXTalkPaul]

Here's the docs for that IDE handler that's in that answer alert screenshot with the recursion problem:
If you could post the stack that's doing that then we could take a look. I'm guessing there's an "Plugin" involved or something similar like a script extension involved that tries to integrate with the IDE via it's "revIDE" API.

revIDEStackNameIsIDEStack

Type: function
Syntax: revIDEStackNameIsIDEStack(pStackName)

Associations: IDE library
Summary: Determines whether a stack is considered part of the IDE

Parameters:
pStackName : The short name of the stack
Returns Boolean (not listed in the inline-docs, someone should fix that)

Description
Use the revIDEStackNameIsIDEStack function to determine whether a stack is considered part of the IDE, according to the name of the stack.

A stack is considered part of the IDE if any of the following are satisfied:
Its name begins with "rev"
It was loaded by the initialisation library
Its name begins with "com.livecode."
Its name is "message box, answer dialog, ask dialog, or home"
Its _ideoverride property is true

There is also a similar IDE function : revIDEStackIsIDEStack()

I don't think this revIDE.. handler is the root of this problem, but it might help you figure out what is. I'm sure that it's used in the loop that is causing the problem.

[OpenXTalkPaul]

Here's the actual code for that handler from "revidelibrary.8.livecodescript"

Code: Select all

/**
function revIDEStackNameIsIDEStack pStackName
   -- call revStackNameIsIDEStack in revcommonlibrary
   return revStackNameIsIDEStack(pStackName)
end revIDEStackNameIsIDEStack

here's the code it calls from "revcommonlibrary"

Code: Select all

function revStackNameIsIDEStack pStackName
   if there is a stack pStackName and the _ideoverride of stack pStackName then
      return true
   else if pStackName is among the items of "message box,answer dialog,ask dialog,home" then
      return true
   else if pStackName begins with "com.livecode." then
      return true
   else if pStackName is among the lines of revInternal__ListLoadedLibraries() then
      return true
   else
      return pStackName begins with "rev"
   end if   
end revStackNameIsIDEStack

revInternal__ListLoadedLibraries() used in that last 'else if' should return a return delimited list that looks like this:

devguides
diff
drawing
dropbox
extension-utils
getopt
httpd
messageauthentication
mime
oauth2
qr
revanimationlibrary
revbackscriptlibrary
revcommonlibrary
revdatabaselibrary
revdebuggerlibrary
revdeploylibrary
revfrontscriptlibrary
revgeometrylibrary
revhtml5urllibrary
revidedocumentationlibrary
revideextensionlibrary
revidelibrary
revidemessagehandlerlibrary
revliburl
revmetadatalibrary
revprintlibrary
revprofileslibrary
revsblibrary
revshortcutslibrary
revtablelibrary
revxmlrpclibrary
ws.goulding.script-library.mergjson

[micmac]

Thank you for your attention Paul

I have solved it now.

You mentioning Plugins led me to look in the Development menu.

Script Debug Mode was on. When I turned it off the problem went away.

I do not remember turning it on, maybe it is on by default in new installations.

Thanks to both of you!!!



Michael

[OpenXTalkPaul]

Thank you for your attention Paul

I have solved it now.

You mentioning Plugins led me to look in the Development menu.

Script Debug Mode was on. When I turned it off the problem went away.

I do not remember turning it on, maybe it is on by default in new installations.

Thanks to both of you!!!



Michael

Glad you got it sorted.