Big Sur?

[SteveWoodward]

Thanks for posting the image. Yes, the 3rd image is what I see when hitting the Back button. The Back button simply take you back to card 1 from card 2.

[jacque]

If you want to send me the stack privately I can take a look. My email is in my signature; replace the appropriate words with punctuation.

[babas66]

After upgrading to Big Sur I noticed that in my test app (still learning LiveCode, former C programmer here) there is interface overlap/corruption when switching between cards (same stack). The first card has a field and a button, the second just a button, in the same location on the cards. Switching between cards causes the controls to overlap and/or parts of the controls get cut off. See below for an idea of what I'm trying to describe (edit: never mind, cannot post link to image). The newly released rc1 exhibits the same behavior.

I have a similar problem with LC 9.6.1 and macOS Big Sur (IDE and Standalone). I don't have this problem with previous version of macOS. Have you find a solution ?

edit : I can add that the problem appears when switching between cards and when hide/show a group.

Regards

[babas66]

Some images of the problems

[babas66]

Hello,

Another example maybe more explicit here : https://synos.ovh/test_collapse.mov (it's a video capture of my screen)

I made a simple Stack with 2 cards :

card 1 :
button "Group"

Code: Select all

on mouseup
Set the visible of group "TT" to not the visible of groupe TT
end mouseup

button "Card2"

Code: Select all

on mouseup
go to cd 2
end mouseup

card 2 :
button "Card1"

Code: Select all

on mouseup
go to cd 1
send "mouseup" to btn "GROUP"
end mouseup

The problem is visible when btn "card1" of the second card is clicked... it's very strange ! and inconvenient...

no one else has encountered this problem ?

Regards

[jacque]

This needs a bug report.

[FourthWorld]

I have a similar problem with LC 9.6.1...

LC v9.6.2 RC1 includes some fixes for the latest macOS. Please try your recipes with the latest version before submitting a report.

You can download the latest version here:
https://downloads.livecode.com/livecode/

Also, see "Specific engine bug fixes" in the Release Notes here:
https://downloads.livecode.com/livecode ... 2_rc_1.pdf

[babas66]

Hello,

thanks for yours replies.

LC v9.6.2 RC1 includes some fixes for the latest macOS. Please try your recipes with the latest version before submitting a report.

I have already try with LC 9.6.2 RC1 and the problem has still here. So with yours advices, I'm going to report this bug.

Edit : here the bug report : https://quality.livecode.com/show_bug.cgi?id=23019

[babas66]

Hello,

A temporary solution (comment 2) : https://quality.livecode.com/show_bug.cgi?id=23019 (thanks to Panos !).

[dalkin]

After updating to Big Sur, LC Indy 9.6.2 RC1, working on my project freezes LC. 3.8GHz Quad-Core 8GB 2400 DDR4 Radeon 680 8GB. Activity monitor shows LC using 100% CPU

[jacque]

After updating to Big Sur, LC Indy 9.6.2 RC1, working on my project freezes LC. 3.8GHz Quad-Core 8GB 2400 DDR4 Radeon 680 8GB. Activity monitor shows LC using 100% CPU

My client has a similar problem on Big Sur, though she doesn't freeze. Activity Monitor shows about 30% CPU usage, but cards are exceptionally slow to load their content. Have you submitted a bug report? If not, could you do that and post the number here so I can track its progress?

Edit: Does your stack work with images? Ours does and I'm wondering if that's part of the problem.

[dalkin]

That's 23025 Jacque.

[jacque]

Thanks! I'll put my name on the watch list.

[SteveWoodward]

Sorry for not getting back to this thread. I am finding more serious things that I'm working on. I found that all of the code related to my data grid has vanished. I had handlers for row clicks amongst other things. If I figure anything out I'll be sure to post.

Steve W

[stam]

I found that all of the code related to my data grid has vanished. I had handlers for row clicks amongst other things.

I have multiple similar handlers but haven’t experienced anything like this... may be a corrupt stack rather than a big sur issue? Do u have backups to test on?