Great thread here
I recently wrote an animation loop where I only unlocked the screen every
33 milliseconds via a self calling command in my main stack. seemed to work
partially, but i knew it was too simple.
Interestingly..
That update loop takes nearly no cpu
but ram consumption keep on going
I did not know this! Isn’t anyone else shocked and surprised??
Bob S
On Jan 22, 2021, at 2:33 PM, Ken Ray via use-livecode
mailto:use-livecode@lists.runrev.com>> wrote:
On Jan 21, 2021, at 8:36 AM, Keith Clarke via use-livecode
mailto:use-livecode@lists.runrev.com>> wrote:
Thanks Brian. I lo
I’ll throw in my lot: Some things unlock the screen without an idle. I think
setting the visible of a stack will do it.
Bob S
> On Jan 22, 2021, at 12:56 AM, Terence Heaford via use-livecode
> wrote:
>
> Just looking for clarity with regard to lock screen.
>
> Is there only one state for
Hello LiveCoders,
Our next meeting is Tuesday, 9 Am Est, we’ll blocking two hours in case people
come and go.
I added Henk, but I’m not sure I got an email for Peter (Music in the Air)...
David / Martin, am I missing others?
Sent from my iPad,
Brian
> On Jan 22, 2021, at 4:29 PM, Martin Koo
> On Jan 21, 2021, at 8:36 AM, Keith Clarke via use-livecode
> wrote:
>
> Thanks Brian. I looked at matchChunk in the dictionary & it seems to return a
> boolean, rather than the offset.
The boolean is just whether or not the matchChunk operation was successful; you
need to provide variabl
But there is no print option in
API | Guide
And their in no entry in for “mobile” in
LiveCode User Guide.pdf
?
I think you will need to print the dictionary entries for mobileControlSet and
mobileControlGet and mobileControlDo.
Sent from my iPhone
> On Jan 21, 2021, at 9:31 PM, Sannyasin
Oh ... I dunno ... after all, what goes "in" must come "out"
Douglas Ruisaard
Trilogy Software
(250) 573-3935
-Original Message-
From: use-livecode [mailto:use-livecode-boun...@lists.runrev.com] On Behalf Of
J. Landman Gay via use-livecode
Sent: Friday, January 22,
Eww. Speak for yourself.
--
Jacqueline Landman Gay | jac...@hyperactivesw.com
HyperActive Software | http://www.hyperactivesw.com
On January 22, 2021 10:01:45 AM doc hawk via use-livecode
wrote:
Not so much either/or as it’s a counter, with 0 being unlocked.
Lock increments the counter, and
To ensure that our screen doesn’t accidentally get overlocked,
even though the system may unlock it at idle time, the best
practice is to always unlock it at the proper time within you code.
That way you can’t confuse things and find yourself scratching
your head as to why it looks like your code i
Not all widgets behave that way. Only widgets that use a native control will
layer over everything else. Things like the tree view widget are still
impacted by Lock Screen.
Sent from my iPhone
> On Jan 22, 2021, at 1:07 PM, Terence Heaford via use-livecode
> wrote:
>
> So a widget is not
So a widget is not a real live code object. I presume that the browser widget
is just an overlaid window without its paraphernalia.
Terry
> On 22 Jan 2021, at 16:57, Tore Nilsen via use-livecode
> wrote:
>
> I forgot to write that you import a snapshot of the widget before you set
> out to
I forgot to write that you import a snapshot of the widget before you set out
to perform the visual effect.
> 22. jan. 2021 kl. 17:54 skrev Tore Nilsen :
>
> The browser widget is drawn in a layer of its own and is not affected by lock
> screen. If you need to do a visual effect you then hide t
The browser widget is drawn in a layer of its own and is not affected by lock
screen. If you need to do a visual effect you then hide the widget itself and
perform the visual effect on the snapshot. You can then delete the snapshot
when it is no longer needed.
Best regards
Tore Nilsen
> 22. ja
Thanks for all the replies.
How does lock screen affect widgets?
It does not appear to have any effect as if you run a Javascript in a Browser
having applied lock screen, the Browser widget seems unaffected.
Thanks
Terry
> On 22 Jan 2021, at 16:39, Dan Friedman via use-livecode
> wrote:
>
Same here. Anytime I want to lock the screen, I do this:
on lockTheScreen
if not the lockScreen then
lock screen
end if
end lockTheScreen
When needed, I use this:
on unLockTheScreen
repeat until not lockScreen
unlock screen
end repeat
end unLockTheScreen
That's my 2 cents.
-
Not so much either/or as it’s a counter, with 0 being unlocked.
Lock increments the counter, and unlock excrements.
The counter gets set to 0 when the engine idles, as well
--
Dr. Richard E. Hawkins, Esq.
(702) 508-8462
___
use-livecode mailing list
u
When I have a handler that needs to lock the screen I will often do the
following
begins handler
put the lockScreen into tPreserveLockScreen
if not tPreserveLockScreen then lock screen
...
code
...
if not tPreserveLockScreen then unlock screen
end handler
Code in our main LC app is large enou
We've switched to:
- https://us02web.zoom.us/j/6819268068
For the second half of the meeting.
On Fri, 22 Jan 2021 at 14:07, David Bovill wrote:
> Im in the waiting room?
> On 22 Jan 2021, 13:58 +, David Bovill , wrote:
>
> I’m here :- but only occasionally in email) See you in a minute!
I once got in an unholy mess with a couple of lock screens which, of their own
accord, had sneaked into repeat loops.
> On 22 Jan 2021, at 2:24 pm, Craig newman via use-livecode
> wrote:
>
> Something else you might want to to know, though it may only be academic.
>
> LockScreen commands are
Hi ,
I think the issue is the need for “Thread Safe” and / or “Concurrent Buffering”
for write/read function with MergExt BLE.
Can anyone give guidance on application of the above using Livecode ?
Regards Camm
> On 14 Jan 2021, at 15:09, General 2018 via use-livecode
> wrote:
>
> Hi ,
>
>
Something else you might want to to know, though it may only be academic.
LockScreen commands are queued. So if you lock the screen twice, you have to
explicitly unlock twice in order to clear the locked state.
It does not matter what happens in the flow of code in terms of screen locking,
whe
Im in the waiting room?
On 22 Jan 2021, 13:58 +, David Bovill , wrote:
> I’m here :- but only occasionally in email) See you in a minute!
> On 22 Jan 2021, 05:56 +, Brian K. Duck via use-livecode
> , wrote:
> > Copy to the list...
> >
> > > Begin forwarded message:
> > >
> > > From: "Brian
I’m here :- but only occasionally in email) See you in a minute!
On 22 Jan 2021, 05:56 +, Brian K. Duck via use-livecode
, wrote:
> Copy to the list...
>
> > Begin forwarded message:
> >
> > From: "Brian K. Duck"
> > Subject: Re: xAPI in LiveCode (was Cmi5 eLearning Standard in LiveCode)
> >
I’m sure someone else can be more clear, but when the engine gets to an idle
state then locks should be cleared. In your example, it would probably clear
at the end of that mouseUp handler, but aTest would completely run with the
screen locked.
Sent from my iPhone
> On Jan 22, 2021, at 3:57 A
Just looking for clarity with regard to lock screen.
Is there only one state for the screen, either locked or not locked and when is
that state changed.
---
on mouseUp
lock screen
aTest
end mouseUp
on aTest
— is the screen still locked here
end aTest
25 matches
Mail list logo
