What makes everything on a card unresponsive?

Klaus major-k klaus at major-k.de
Sun Apr 19 14:02:29 EDT 2020

Hi Graham,

> Am 19.04.2020 um 19:34 schrieb Graham Samuel via use-livecode <use-livecode at lists.runrev.com>:
> Sorry to trouble this list yet again, but the main screen (in fact the the first card) in my mobile app has a “settings” graphic which acts as a button which to take the user to a ‘menu’ card. That card contains buttons and graphics which lead on (via very simple MouseUp handlers) to specialised menu actions, each on its own card. One can return to the main screen from each of these action cards.
> When I run my app in the iPhone simulator, the activities on the main screen all work, with buttons, fields etc. When I click on the ‘go to menu card’ graphic, that always works. But when I get there, sometimes some of the menu buttons work, but sometimes the whole card becomes unresponsive, so that none of the buttons work, not even a ‘cancel’ button whose job is just to go back to the main screen. This didn’t used to happen, so I have messed up somehow. But my question is, what sort of action would make an entire card unresponsive? Maybe the app is stuck doing something I can’t see, but what could it be?
> Any ideas welcome, including a debugging strategy.
> Graham

any script? card, front, back, behavior?
A loop that can get stuck?
Accessing a file that is not there?

Maybe you can post your card script of the "menu card".



Klaus Major
klaus at major-k.de

More information about the use-livecode mailing list