In our app, we have a lot of handlers (internal APIs) that get called by
other handlers and, as multiple developers are involved, knowing what is
calling what takes some effort. To address the issue of screen locks, we
adopted a coding standard as follows:
If a handler should lock the screen,
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. . I will have to calculate
the rect as well. No big deal, just more things to have to workarou
what about switching to pg?
On Thu, Mar 28, 2024 at 1:24 PM Bob Sneidar via use-livecode <
use-livecode@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
>
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 mod
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
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
On Mar 28, 2024, at 8:48 AM, Mike Kerne
there are many (many) datagrid functions and commands that unlock the
screen,
the behavior script for dg's is 11,597 lines long.
i started copying/pasting the signature of them, but finally decided there
were many too many. instead of deleting the rest of this post, i left them
in place.
i reiterat
The issue may be with the datagrids. It appears that Lock Screen is not
preventing changes to the datagrids from refreshing the screen.
Bob S
> On Mar 28, 2024, at 8:28 AM, Bob Sneidar wrote:
>
> Hi Craig thanks for responding. I am not updating fields per se as the only
> thing changing is
Hi Craig thanks for responding. I am not updating fields per se as the only
thing changing is the datagrid selection(s) and the status of the checkbox.
Curiously I am not seeing the tab widget selection change but I am seeing the
hiding and showing of the datagrids as each tab is selected.
Bo
Hi Alex. Thanks for responding.
I have a module in my app called Software. I have 5 datagrids, one for software
and 4 others for the entities the software license is linked to. Each datagrid
has associated fields as well. Customers, Sites, Devices and Files. Each of
these entities can be linke
No I am using 9.6.11.
Bob S
> On Mar 27, 2024, at 8:43 PM, Tom Glod via use-livecode
> wrote:
>
> Bob,
> Sorry I can't double check at the moment, but I was reading the release
> notes for 10 dp7 and there was some stuff about that in there
> (Its possible I am . mis-remembering.)
> Is
Bob.
I have no idea what you are facing with such a basic issue. To be sure, please,
somewhere in the stack you are having the issue, make a button and a field and
run this:
on mouseup
lock screen —comment out for the first run
repeat 3
put random(999) into fld 1
wait 20
end repeat
end m
Hi Bob,
I'm not sure from your description how / when you are seeing the
(unexpected) changes happening.
Remember that lockscreen is automatically set to false when there is no
handler running, so unlerss you have an intensive handler running, you
will see these changes.
If it's not that -
Bob,
Sorry I can't double check at the moment, but I was reading the release
notes for 10 dp7 and there was some stuff about that in there
(Its possible I am . mis-remembering.)
Is that the version you are using?
On Wed, Mar 27, 2024 at 7:02 PM Bob Sneidar via use-livecode <
use-livecode@list
Oh, but it gets better. I put at the entry point of the script:
lock screen
put the lockscreen into tScreenIsLocked — I checked and this is true
Then at the exit point:
put the lockscreen
STILL TRUE in spite of the fact that I see everything that the app is doing to
the screen the en
Hi all.
I read in the dictionary that Lock Screen does not work in Script Debug mode.
Okay so I turn it off, put the command “Lock Screen” at the entry point to a
selectionChanged handler which goes on to do a number of things that change the
appearance of the screen. The screen is decidedly N
16 matches
Mail list logo
