LiveCode Forums

Livecode and Mac OSX Big Sur still refuse to play nice and despite reporting a bug (23279) back in July but the problem is now unmanageable, with no clear fix in sight. I have uploaded a video https://youtu.be/zucpqmHgW78 that shows the issue that emerges when I open my project so someone might recognise what's at play and, if that person is LC staff, they might pass it to Panos. It is obviously (to me) a problem with how LC is managing memory but I don't know if that's what it is.

All versions of LC are affected, these are the versions I have installed:

I must be very stupid indeed, but having watched your video
I cannot understand things.

If you could explain what goes wrong in words I might have a chance.

There are 2 cards, and the video shows the transition from one card to the other where the 1st card, at the start of the video, breaks up slowly and in pieces to reveal the 2nd card (orange colour). The transition is triggered by selecting the name in the scrolling list field on card 1. The transition and fragmentation are in real time.

@dalkin: I posted a comment on bug 23279 which I hope will be helpful.

The video shows a known issue in 9.6.1 when running on Big Sur which we fixed in 9.6.3.

Unfortunately the fix to that bug means that it now takes longer to update the screen when any one update occurs - it is advised to use lock/unlock screen judiciously around code which updates multiple interface elements.

In particular, the CPU spike issue reported on the mentioned bug is down to the many default buttons on the Lyricist card - default buttons 'pulse' in some versions of macos, so with several of them the screen is being updated constantly (as they do not pulse on Big Sur, or indeed Catalina at least, we do need to tweak when the animation is attempted to be run based on macOS version).

In the meantime, simply making all those default buttons normal buttons seems to resolve the CPU spiking issue - which will hopefully mean you can use 9.6.4 for your app and thus resolve the graphical fragmentation issues you are seeing with 9.6.1.

Thank you Mark, I would never have picked that up in 7 lifetimes. The interface is working to all intents and purposes with the single exception that I can't seem to delete a card by script. The card is not checked as 'Cant delete' in the property inspector but it seems that there is a running script. The triggered error and the script from the message box are shown here:

Is the Delete button on the card you're trying to delete? You can't do that because the button script is running.

Is the Delete button on the card you're trying to delete? You can't do that because the button script is running.

This looks like a bad case of circular logic.

Strange .. 'delete card' is an entry in the dictionary so the question remains as to how to delete a card by script.

Execute it from the script of any other object than the one being deleted.

Script this: Isn't LCS wonderful?

Yep. Richard's advice to trigger it from another object worked for me. Thank you to everyone who contributes to this forum. A real community. I think you should all be bronzed.