LiveCode Forums.

jacque wrote: Tue Jul 27, 2021 11:06 pm I wonder if a lockscreen would overcome the flash.

weirdly no... lock screen was already on. I think the send in xx time stops the lock screen?

FourthWorld wrote: Tue Jul 27, 2021 9:32 pm Stam, is that for Mayo?

Hey Richard - if you mean Mayo Clinic, no.... but for a UK-equivalent of the Mayo.

I think the send in xx time stops the lock screen?

I was afraid it might, lockscreen resets on idle and sending in time allows idle. Worth a try though.

Setting traversalOn to false for both fields would stop the selection. Do it on preopencard, then send a message in time to set it back to true after opencard.

Alternately, you could try changing the send in time to 1 or 2 milliseconds with your current method. That might make the flash less noticeable than a half second lag.

jacque wrote: Wed Jul 28, 2021 7:10 am Alternately, you could try changing the send in time to 1 or 2 milliseconds with your current method. That might make the flash less noticeable than a half second lag.

Actually what i did was hide the entire stack then show it again. The app starts with a splash stack which then initialises and launches the mainstack. But if i hide the mainstack while it does it's own initialisations and then show it, there is no flashing, just a 0.5s delay between the splash stack going away and the mainstack appearing, which fine.

I'm sure there must be a more elegant way of doing it, but this does the job well