LiveCode Forums.

Hi! I just did a lot of work on a stack that has DataGrid in it. Now when I attempt to open it the stack only shows the window outline and top window bar and the IDE locks up completely before it fills the stack window. I can still change the active window with the mouse, but none of the menu or toolbar items are selectable. The system is not in a loop, the CPU is mostly idle. The only way to restart is to kill the IDE and restart. I have tried selecting Suppress Messages, Suppress Errors, start up in debug mode, and munging event and command names in the binary, to no avail. I can move the stack's window around but it just carries the image of the desktop around with it. The Toolbar can be closed but not the IDE bar or the stack window. Are there any other ways to open up a stack incrementally so I can at least clean out or skip whatever is doing this? Or is there any kind of rev file disassembler/decoder that might spot where the stray neutrino flipped a bit?

One interesting, maybe spurious note - I had the DataGrid tutorial open when I first created the stack. I had copied some of the script code over manually (using cut and paste on the text), but a lot of other scripts that I had NOT copied over from the tutorial now appear in my stack's REV file. I didn't copy over any objects, so I'm not sure how they got in there. Have there been any bugs involving stack objects getting mixed up during save? I had saved and reopened it a few times before this happened. The changes I made just before this happened were (I thought) innocuous, like changing some object dimensions, nothing involving start up in any way. The other project I was working on at the same time still works perfectly, so it does not appear to be the IDE which is damaged.

Any thoughts would be helpful. Thanks, Walt

I opened it with Message Watcher - the last message is preOpenControl called just after _CreateAlternatingColorImage. It locks up Message Waycher as well.

If you can't get it, feel free to contact me by email.

Thanks Curry. I took the scripts out of the binary and rebuilt it. I am trying to reproduce the issue now to see if I can cause it to happen again with a new stack. My first culprit is failing to put a "get" before a function call (which is a pilot error I found in another related stack that shares some code). Normally this spits up the script window when encountered and allows a graceful exit. The first function call I am suspecting is the "binaryDecode" function.

Walt