LiveCode Forums.

Hi,

I have a livecode stack that I can load into LC 5.5.3 and it will cause the iDE to Lock up consistently (Mac Beachball, Force Quit only - no Cmd-. break out, generates a system diagnostic file!) when I try to go to the code inspector. It's only the one LC stack - not all of them. I have set the IDE to not do Script Debugging, turned Off messages and have waited 5 minutes before attempting to go to the code screen after loading the stack. All to no avail. So I am a little stumped as to how I can edit the code for the stack to see what might be causing it - as the only way I know of to look at the code is through the IDE.

Does anyone have any alternative way of editing LC stacks that doesn't use the LC IDE? Preferably something not written in LC - and therefore not likely to have the side-effect interaction issue of having an IDE that runs in 'real-time' the code that is being written (a dumb concept in my opinion!)

I am getting tired of Livecode now - mainly due to the IDE, which is so buggy as to be unusable at times. But the bugs are probably not built in to the IDE but are all side-effects of the stacks loaded into it - and the 'running' of said code.

Can anyone help me start enjoying LC again?

Cheers,
Dave

Hi Dave,
the best thing to do is to send the "locking" stack to RunRev support so they can understand why the IDE Lock and Crash.

Guglielmo

Hi Dave,

1. I can ake a look at the stack if you like, Dave! Maybe I can find out something...
Send it to: klaus AT major-k.de

2. Since this is definitively NO feature request (HINT, HINT!), I will move this thread to "Talking Livecode".


Best

Klaus

Dave...

Can you post your stack ?... It would be interesting to look at..

Dixie

I've been using the LiveCode engine since 1997 and have rarely seen the IDE lock up. Since this is happening with a stack you've written, without seeing that stack it won't be possible to determine where its scripts went south.

Thanks all,

Klaus found the problem - it was a reference to an 'http://localhost" image that couldn't be resolved as the local server was not running. Why that should cause a lock-up instead of a simple error message I'm not sure, but anyway!! Thanks Klaus for finding that.

Thanks also Mr K for moving it to the more appropriate forum area - though the 'feature request' would be... Much better checking in the IDE for runaway requests/loops/etc and to give the option for breaking out of them, when they occur, more easily

Still partially enjoying LC - when the IDE lets me

Cheers,

Dave

Hi Dave, hi all,

what was really puzzling me was the fact that I got a "recursion limit exceeded"
error when checking the stack in the MetaCard IDE!

What the heck has that to do with an unsolvable image URL?


Best

Klaus

That may be a bug in LibURL, worth filing a report against now that there's a recipe.