Re: Slow performance on Big Sur

2020-12-16 Thread J. Landman Gay via use-livecode
The screen is already locked on closeCard and unlocked on openCard. In between a bunch of stuff happens. Maybe that sequence of lock/unlock isn't working in Big Sur? On 12/16/20 3:46 AM, Pi Digital via use-livecode wrote: What about using ‘lock screen’? Then go card. For preopen it ‘shouldn’t’

Re: Slow performance on Big Sur

2020-12-16 Thread merakosp via use-livecode
Hello all, We have tried to reproduce this issue on Big Sur, but with no success. We have filed a report for this issue - could you please attach a stack (and a recipe) that demonstrates the problem here: https://quality.livecode.com/show_bug.cgi?id=23037 If the stack is confidential, feel free

Re: Slow performance on Big Sur

2020-12-16 Thread Pi Digital via use-livecode
What about using ‘lock screen’? Then go card. For preopen it ‘shouldn’t’ make a difference but I have found this to be a cause for stammering in the past. Don’t bother putting an ‘unlock screen’ at the end of the preopencard or opencard as it will unlock itself at the end of the open sequence

Re: Slow performance on Big Sur

2020-12-15 Thread J. Landman Gay via use-livecode
I had my client try it. Adding "wait 0 milliseconds" after a "go card" didn't make any difference really. The first four card changes were pretty fast, and after that it got slower and slower with each subsequent card change. I was watching her screen remotely but I couldn't see it due to how

Re: Slow performance on Big Sur

2020-12-14 Thread merakosp via use-livecode
Hello all, Does adding a after the command make any difference? Cheers, Panos -- On Tue, 15 Dec 2020 at 00:24, J. Landman Gay via use-livecode < use-livecode@lists.runrev.com> wrote: > I also populate a field and adjust its rect from custom properties, as > well as adjust some > controls

Re: Slow performance on Big Sur

2020-12-14 Thread J. Landman Gay via use-livecode
I also populate a field and adjust its rect from custom properties, as well as adjust some controls based on stored custom property settings. I also load an image from an unplaced background. So, lots of setup on preOpenCard. On 12/14/20 1:14 PM, Marty Knapp via use-livecode wrote: I have a

Re: Slow performance on Big Sur

2020-12-14 Thread J. Landman Gay via use-livecode
On 12/14/20 2:46 PM, Paul Dupuis via use-livecode wrote: On 12/14/2020 2:04 PM, J. Landman Gay via use-livecode wrote: My client is running Big Sur and says that changing cards in a stack causes a very slow, stuttering display. The background image appears in chunks and text in the fields comes

Re: Slow performance on Big Sur

2020-12-14 Thread Paul Dupuis via use-livecode
On 12/14/2020 2:04 PM, J. Landman Gay via use-livecode wrote: My client is running Big Sur and says that changing cards in a stack causes a very slow, stuttering display. The background image appears in chunks and text in the fields comes in as sequential pieces. The order of the display

Re: Slow performance on Big Sur

2020-12-14 Thread Marty Knapp via use-livecode
I have a customer with a brand new Mac Pro with tons of memory (and two 49 inch curved screens!) running Big Sur and he sent a video showing slow performance when populating a half dozen text fields from a custom property - took about 3 seconds (in a standalone). Marty > On Dec 14, 2020, at