Revisiting Lock Screen

[Bob Sneidar]

I do a lot with DG that is not supported with PG. Also I just discovered that on a MacOS device, the snapshot of the card shows the custom menu, even though the menu is not inside the rect of the card. <sigh>. I will have to calculate the rect as well. No big deal, just more things to have to workaround.

Bob S


On Mar 28, 2024, at 10:30 AM, Mike Kerner via use-livecode <use-livecode at lists.runrev.com> wrote:

what about switching to pg?

On Thu, Mar 28, 2024 at 1:24 PM Bob Sneidar via use-livecode <
use-livecode at lists.runrev.com<mailto:use-livecode at lists.runrev.com>> wrote:

Thanks Mike.

I think I am going to have to come up with an alternative. Something like
taking a snapshot of the window then overlaying it on the window while
processing, then deleting it when done.

The trouble is I have other windows open that will update because they are
synching with the module I am working in. Also this won’t improve
performance the way Lock Screen would (should).

Bob S


On Mar 28, 2024, at 9:31 AM, Mike Kerner via use-livecode <
use-livecode at lists.runrev.com> wrote:

didn't you say your code was modifying a dg?
i see a couple of possible failure points:
* the widget could be doing something unexpected
* the dg could be unlocking the screen.
you could also try two or more lock screens. i believe lock screen is
additive. until idle.

On Thu, Mar 28, 2024 at 12:22 PM Bob Sneidar via use-livecode <
use-livecode at lists.runrev.com<mailto:use-livecode at lists.runrev.com><mailto:use-livecode at lists.runrev.com>>
wrote:

Wow thanks for that! I think I remember now this came up before, and
datagrids were the culprit.

But that does seem odd, doesn’t it? Why would a screen lock interfere with
the datagrid behavior? (That is rhetorical. Only the devs would know that.)

Bob S