Locked stack??

[dunbarx]

I have a stack of one card that has several scrollable fields and a few buttons. Nothing fancy about any of those controls. The stack is a year old.

All of a sudden, though each of the fields can be both edited and scrolled by hand, and each can be selected, resized and moved around, nothing else responds. I cannot open the message box, add a new button, etc. The "Object" menu is completely disabled, though it does not show any change. No other menu works at all, though the submenus for each do appear. I cannot even close the stack or quit LC itself; I have to force quit in order to get out of it.

It is almost as if messages are blocked, though they are not, but that would not account for some of the other behaviors I see. All other stacks work normally. Restarting LC or the machine makes no difference.

The stack is oddly corrupted, unless I am missing something. I can send it to anyone who asks, though I am not sure I would want such a thing on my machine.

Craig

[jacque]

It sounds like a frontscript. Try locking messages in the toolbar before opening the stack and see if that works. If so, scan the scripts for a frontscript, or anything else that might interfere.

[richmond62]

You could try opening it with "an alternative IDE", then performing a 'Save As' in that "alternative IDE",
and then open the new version in LiveCode.

Odd as that may sound, it has saved me 3 times in the last 8 months.

[dunbarx]

Jacque,

Locking messages before opening changes nothing.

I have played with front and backScripts, long ago, but neither of those are present in this stack. This must be something in the stack itself, because I can open others which all work just fine. Interestingly, if any other stack is open and in front, since all the menus there are intact, CMD-Q quits LC just fine.

Richmond.

I recall a discussion of these alternative IDE's, but I do not know what they are. You do not mean another instance of LC, do you?

Craig

[richmond62]

You do not mean another instance of LC, do you?

No, I don't. But I have been asked not to name it here.

[dunbarx]

Ah, now I remember a little. Another venue. Not interested in that experiment. I will chalk this one up as just another of my usual indescribable issues.

Craig

[richmond62]

Not interested in that experiment.

Even at the risk of appearing narrow-minded?

That is most definitely not an experiment.

[dunbarx]

Richmond.

How will, regardless of the outcome, migrating my stack to that other place tell me anything? Maybe I do not know what exactly goes on over there?

Craig

[richmond62]

Ah: good point.

I thought you were ONLY interested in making the problem go away: NOT understanding what was causing it.

[dunbarx]

Richmond.

I would be happy to learn how to fix my stack. I can access its data, but that is all. It is as if messages were BEYOND VERY locked. All other stacks work fine, of course, which makes me believe it is a corruption of the stack itself.

Craig

[jacque]

I'd look for any mouse handlers that may be blocking. I agree there's something in the scripts that interfere. Comment out various suspicious parts to see if you can find it.

[dunbarx]

Jacque. Great idea, but, you see, when I tried that of course I could not even open the message box.

I thought I would be clever, go to another stack, which you recall works just fine, open msg, and then go back to the weird stack. But when I got there I forgot that nothing works. So then I was really proud of myself when I went back to the working stack, and tried to open the card script of the weird stack from there.

Just guess what did not happen.

Craig

[dunbarx]

Jacque, Richmond,

I cannot prove this, even to myself, being locked out, but the functionality of the weird stack is so simple, residing purely in the scripts of a few buttons, that I do not believe that is the cause.

Recall that this stack worked just fine for many months, and only when I opened it again was it not responsive. The "object" menu will not even open, and though all other menus open, no action of any of the menuItems works.

Recall that all the fields are accessible; they scroll, are ostensibly editable, though nothing can be saved or even copied, and can be moved and resized. So certain mouse and keyboard related actions are allowed, which is odd.

It's the stack, all right, but something deeper and more sinister than some handler trapping and burying, what, every possible message? Including select OS managed messages?

Craig

[jacque]

That's too weird. I'd be tempted to send it to support and see if they know what's wrong. Or send it to me and I'll see if it works here, I'm still running an older Mac OS.