Slow performance on Big Sur
J. Landman Gay
jacque at hyperactivesw.com
Wed Dec 16 16:36:32 EST 2020
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’ 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 anyway (as I’m sure you’re already aware).
>> On 16 Dec 2020, at 05:55, J. Landman Gay via use-livecode <use-livecode at lists.runrev.com> wrote:
>> 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 remote viewing works, but she said the redraw was quite noticeable.
>>> On 12/14/20 4:45 PM, merakosp via use-livecode wrote:
>>> Hello all,
>>> Does adding a <wait 0 milliseconds> after the <go card myCard> command make
>>> any difference?
>> Jacqueline Landman Gay | jacque at hyperactivesw.com
>> HyperActive Software | http://www.hyperactivesw.com
>> use-livecode mailing list
>> use-livecode at lists.runrev.com
>> Please visit this url to subscribe, unsubscribe and manage your subscription preferences:
> use-livecode mailing list
> use-livecode at lists.runrev.com
> Please visit this url to subscribe, unsubscribe and manage your subscription preferences:
Jacqueline Landman Gay | jacque at hyperactivesw.com
HyperActive Software | http://www.hyperactivesw.com
More information about the use-livecode