I meant the extensions folder in the app bundle, just don't mentioned it.
Thought that it is clear that all included extensions reside in the app bundle.
;)
> Am 11.12.2023 um 17:36 schrieb Bob Sneidar via use-livecode
> :
>
> That is not where the remote debugger lives on MacOS. It is in th
Bob: There may be a problem with your code.
I believe I have seen the Remote Debugger message when I had a runtime error in
a modal dialog. In earlier versions of LiveCode the dialog would fail silently,
returning to the stack without reporting any error but actually not executing
any code after
See that is the exact problem. Because when enabled, the remoteScriptDebugger
says there is an error, but cannot show me where the error is because the
script is locked, I have no clue as to what script (if any) is causing the
issue. That is why I asked if anyone had the password to the
remoteS
If you have a reproducible script it would be something LC probably should
know about in a bug report.
--
Jacqueline Landman Gay | jac...@hyperactivesw.com
HyperActive Software | http://www.hyperactivesw.com
On December 11, 2023 10:43:27 AM Bob Sneidar via use-livecode
wrote:
Ahah! I removed
Ahah! I removed the folder from the application package extensions folder and I
no longer get the error! Also, my code is not throwing ANY kind of error, so
this is definitely something wrong with the remote debugger or something else
that thinks a remote debugger error has occurred when it hasn
That is not where the remote debugger lives on MacOS. It is in the Application
package. I can try to remove it from there and see what happens.
Bob S
> On Dec 8, 2023, at 4:14 PM, matthias rebbe via use-livecode
> wrote:
>
> Hm, did you already try to delete the folder
> Extensions/com.l
