Re: lock screen

n't think this has > anything to do with the lock screen. > > Sean > > On Sat, 23 Jan 2021 at 05:11, Tom Glod via use-livecode < > use-livecode@lists.runrev.com> wrote: > > > Great thread here > > I recently wrote an animation loop where I only unlocked the screen e

Re: lock screen

Hi Tom, Make a sample stack (sounds like you already have) and make a bug report labelled 'Memory leak on looping field update'. I don't think this has anything to do with the lock screen. Sean On Sat, 23 Jan 2021 at 05:11, Tom Glod via use-livecode < use-livecode@lists.runrev.com>

Re: lock screen

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 < > use-livecode@lists.runrev.com> wrote: > > > > Just looking for clarity with regard to lock screen. > > > > I

Re: lock screen

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 th

RE: lock screen

: Friday, January 22, 2021 10:27 AM To: How to use LiveCode Cc: J. Landman Gay Subject: Re: lock screen 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 w

Re: lock screen

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

Re: lock screen

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

Re: lock screen

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: > >

Re: lock screen

u 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 the widget >> itself and pe

Re: lock screen

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 y

Re: lock screen

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 >

Re: lock screen

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 >

Re: lock screen

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

Re: lock screen

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

Re: lock screen

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

Re: lock screen

es > throughout. All is reset at idle time. > > Craig > > -Original Message- > From: use-livecode [mailto:use-livecode-boun...@lists.runrev.com] On Behalf > Of Brian Milby via use-livecode > Sent: Friday, January 22, 2021 6:50 AM > To: How to use LiveCode &g

RE: lock screen

to use LiveCode Cc: Brian Milby Subject: Re: lock screen 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

Re: lock screen

:57 AM, Terence Heaford via use-livecode > wrote: > > 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 > > loc

lock screen

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

Re: Lock Screen does NOT work!

Oooohky... So the problem is not calling selectionChanged while another selectionChanged is running. The problem is setting the dgData (or dgText I will assume) while a selectionChanged handler is running. I remember I tracked that down before this. Setting the dgData is obviously

RE: Lock Screen does NOT work!

dim...@evergreeninfo.net -Original Message- From: use-livecode [mailto:use-livecode-boun...@lists.runrev.com] On Behalf Of Bob Sneidar via use-livecode Sent: Thursday, January 24, 2019 2:29 PM To: How to use LiveCode Cc: Bob Sneidar Subject: Re: Lock Screen does NOT work! For those interes

Re: Lock Screen does NOT work!

he > datagrid updates. That would pop an idle message and cancel the screen lock. > > Bob S > > >> On Jan 24, 2019, at 10:52 , Bob Sneidar via use-livecode >> wrote: >> >> Hi all. Bold subject line I know. Here's how I know. >> >> I used Fi

Re: Lock Screen does NOT work!

now. > > I used Find in This Stack and it's SubStacks to find "lock screen". I > replaced all with "-- lock screen" effectively commenting out ALL of the lock > screen statements. I verified by checking one of the found scripts and indeed > lock screen is

Lock Screen does NOT work!

Hi all. Bold subject line I know. Here's how I know. I used Find in This Stack and it's SubStacks to find "lock screen". I replaced all with "-- lock screen" effectively commenting out ALL of the lock screen statements. I verified by checking one of the found scripts and

Re: lock screen gotcha revisited

update > occurs, all widgets would get an OnUpdate event, and this would all > happen atomically under a lock screen. (Indeed, this mechanism would > also make engine control UI animations and animated GIFs less CPU > run-loop intensive - they are currently all implemente

Re: lock screen gotcha revisited

get works. The clock widget uses the 'schedule timer' syntax to do the equivalent of 'send in time'. Indeed, this is implemented using the same mechanism as 'send in time' and so each pending message (timer, in this case) is dispatched separately, and not under a lock screen. I spent some time

Re: lock screen gotcha revisited

re isn't one - although you can use 'execute script' to use LCS's > lock/unlock screen. > > Indeed, I should check whether LCB does currently use an implicit lock > screen - it probably should as LCB handlers, when called from LCS, are > meant to be 'atomic' in some sense. >

Re: lock screen gotcha revisited

The general consensus is that it doesn't. I think there was something else going on where my screen was not updating even after 5 successive screen unlocks, and I never figured out why, but I went through my app and every place there was a lock screen, I added an unlock screen to the end

Re: lock screen gotcha revisited

LCB does currently use an implicit lock screen - it probably should as LCB handlers, when called from LCS, are meant to be 'atomic' in some sense. This interacts with LC Script, timed widgets (clocks, animations) want their own screen updates ... Screen updates of widgets only happen upon

Re: lock screen gotcha revisited

The real interesting thing is now for me how to lock the screen in LC Builder? I couldn't find a way to do that. Who knows? This interacts with LC Script, timed widgets (clocks, animations) want their own screen updates ... ___ use-livecode mailing

Re: lock screen gotcha revisited

On 08/21/2017 10:28 AM, Mark Waddingham via use-livecode wrote: On 2017-08-19 04:41, J. Landman Gay via use-livecode wrote: Except when it doesn't. There seems to be an override in the lock count if any unlock uses a visual effect. I'm not sure if that's on purpose or not. Internally there is

Re: lock screen gotcha revisited

On 8/21/17 5:47 PM, prothero--- via use-livecode wrote: I didn't realize that the lockscreen command only applied to the handler that sets it. No, it doesn't (or shouldn't) apply only to the handler that sets it. Does this mean that each script has to set lockscreen if it needs it? It's a

Re: lock screen gotcha revisited

k will open it up. That seems more intuitive. >> >> Initially it's more intuitive, but if it were done this way you couldn't >> have handlers that manage locks both independently and when called from >> amother handler. For example: >> >> on updateThings >&g

Re: lock screen gotcha revisited

independently and when called from amother > handler. For example: > > on updateThings > lock screen > set the rect of > set the loc of > updateAllButtonLabels > unlock screen > end updateThings > > on updateAllButtonLabels > lock screen > repeat with i

Re: lock screen gotcha revisited

locks both independently and when called from amother handler. For example: on updateThings lock screen set the rect of set the loc of updateAllButtonLabels unlock screen end updateThings on updateAllButtonLabels lock screen repeat with i = 1 to the number of btns set

Re: lock screen gotcha revisited

I agree with Bill. If you lock a door twice on a car, it is still just locked. One unlock will open it up. That seems more intuitive. Sent from my iPhone > On Aug 21, 2017, at 2:19 PM, prothero--- via use-livecode > wrote: > > Seems like it would be much

Re: lock screen gotcha revisited

Seems like it would be much simpler if lockscreen just kept the screen locked until unlockscreen was invoked, but there was an update screen command when forced updates were needed. No counters to keep track of. Best Bill William Prothero http://ed.earthednet.org > On Aug 21, 2017, at 10:40

Re: lock screen gotcha revisited

I used to have an example, I struggled with the problem until I figured out the reason, and then I modified the script to work around it. It actually didn't happen in the IDE, only on Android. (I didn't test on iOS.) Now I can't remember what the original problem script was. But I'll see if I

Re: lock screen gotcha revisited

I would have to recreate it as my production stack has already been gone through, and it seems to be working as advertised, which would argue against it being an engine issue. I'll see if I can create a sample stack in the next couple days. Right now I have a couple service calls to go out on

Re: lock screen gotcha revisited

On 2017-08-19 04:41, J. Landman Gay via use-livecode wrote: Except when it doesn't. There seems to be an override in the lock count if any unlock uses a visual effect. I'm not sure if that's on purpose or not. Internally there is a counter - and only one - the engine uses it too when it needs

Re: lock screen gotcha revisited

times >> straight and I do not lock the screen to that many levels. It still did no >> unlock the screen, so now it may be that one handler cannot unlock another >> handler's lock screen, which I was unaware of. > > -- > Jacqueline Landman Gay

Re: lock screen gotcha revisited

ll did no unlock the screen, so now it may be that one handler cannot unlock another handler's lock screen, which I was unaware of. -- Jacqueline Landman Gay | jac...@hyperactivesw.com HyperActive Software | http://www.hyperactive

Re: lock screen gotcha revisited

e screen to that many levels. It still did no unlock the > screen, so now it may be that one handler cannot unlock another handler's > lock screen, which I was unaware of. > > Bob S > > >> On Aug 18, 2017, at 18:37 , Mark Wieder via use-livecode >> <use-livecode@

Re: lock screen gotcha revisited

Yup. My troubles came when I had a handler unlock the screen 5 times straight and I do not lock the screen to that many levels. It still did no unlock the screen, so now it may be that one handler cannot unlock another handler's lock screen, which I was unaware of. Bob S > On Aug 18, 2

Re: lock screen gotcha revisited

On 08/18/2017 07:41 PM, J. Landman Gay via use-livecode wrote: Except when it doesn't. There seems to be an override in the lock count if any unlock uses a visual effect. I'm not sure if that's on purpose or not. Thanks. Good to know. I've just been using the barebones lock. -- Mark Wieder

Re: lock screen gotcha revisited

Except when it doesn't. There seems to be an override in the lock count if any unlock uses a visual effect. I'm not sure if that's on purpose or not. -- Jacqueline Landman Gay | jac...@hyperactivesw.com HyperActive Software | http://www.hyperactivesw.com On August

Re: lock screen gotcha revisited

On 08/18/2017 03:50 PM, Bob Sneidar via use-livecode wrote: Hard to say. I'm almost done finding every place I lock the screen and adding an unlock screen in the same handler. And that, of course, is the best procedure. Locking/unlocking the screen works on sort of a reference-counting

Re: lock screen gotcha revisited

Hard to say. I'm almost done finding every place I lock the screen and adding an unlock screen in the same handler. Bob S > On Aug 18, 2017, at 14:03 , J. Landman Gay via use-livecode > wrote: > > That doesn't sound right, though I've seen issues with nested

Re: lock screen gotcha revisited

That doesn't sound right, though I've seen issues with nested locks too. What happens if you call this handler: on unlockReally repeat until the lockscreen is false unlock screen end repeat end unlockReally On 8/18/17 3:54 PM, Bob Sneidar via use-livecode wrote: okay after some

Re: lock screen gotcha revisited

okay after some testing it seems only the script that locked the screen, maybe only the actual handler can clear it's own lock. If this is not right I'd like to know it. Seems there ought to be an unlock all command or some such thing. Bob S > On Aug 18, 2017, at 13:37 , Bob Sneidar via

lock screen gotcha revisited

Hi all. I have some screen updates I do that take time because I query a database first, and it may not be local. To keep the screen from progressively updating, I lock the screen. I then decided to put a status message field at the bottom of each "form" (meaning card in a stack) so I have

Re: lock screen doesn't

Okay never mind I think I see what is going on. If the script editor is open and debug is on, even t hough there are no breakpoints or traces in effect, lock screen is still disabled. Bob S > On Jul 21, 2017, at 14:44 , Bob Sneidar via use-livecode > <use-livecode@lists.runrev.c

lock screen doesn't

Hi all. I know this has been hashed through before, but I am locking screen just about every place I can and the screen is still not staying locked! Any way to easily and reliably NOT UPDATE SCREEN while scripts are running? Bob S ___

AW: AW: can I lock screen over more than one handler?

Auftrag von Jonathan Lynch via use-livecode Gesendet: Donnerstag, 6. Juli 2017 12:52 An: How to use LiveCode <use-livecode@lists.runrev.com> Cc: jonathandly...@gmail.com Betreff: Re: AW: can I lock screen over more than one handler? Tiemo, have you tried using a browser widget instead? Sen

Re: AW: can I lock screen over more than one handler?

he Nachricht- >> Von: use-livecode [mailto:use-livecode-boun...@lists.runrev.com] Im Auftrag >> von Tiemo Hollmann TB via use-livecode >> Gesendet: Mittwoch, 5. Juli 2017 18:46 >> An: 'How to use LiveCode' <use-livecode@lists.runrev.com> >> Cc: Tiemo H

Re: AW: can I lock screen over more than one handler?

use-livecode Gesendet: Mittwoch, 5. Juli 2017 18:46 An: 'How to use LiveCode' <use-livecode@lists.runrev.com> Cc: Tiemo Hollmann TB <toolb...@kestner.de> Betreff: AW: can I lock screen over more than one handler? Hi Randy, it worked out that the issue wasn't related to the design of two

AW: can I lock screen over more than one handler?

icht- Von: use-livecode [mailto:use-livecode-boun...@lists.runrev.com] Im Auftrag von Tiemo Hollmann TB via use-livecode Gesendet: Mittwoch, 5. Juli 2017 18:46 An: 'How to use LiveCode' <use-livecode@lists.runrev.com> Cc: Tiemo Hollmann TB <toolb...@kestner.de> Betreff: AW: can I lock scree

Re: AW: can I lock screen over more than one handler?

ost can't see it, but on Win 8 with the standard violet title bar it is an ugly flickering, each time I set the filename (which happens very frequently in a quiz loop). And I can't prevent this flickering with a lock screen right before the setting of the filename. The setting of the filename seems to relea

AW: can I lock screen over more than one handler?

Nachricht- Von: use-livecode [mailto:use-livecode-boun...@lists.runrev.com] Im Auftrag von Randy Hengst via use-livecode Gesendet: Mittwoch, 5. Juli 2017 17:56 An: How to use LiveCode <use-livecode@lists.runrev.com> Cc: Randy Hengst <iowahen...@mac.com> Betreff: Re: can I lock screen ov

Re: AW: can I lock screen over more than one handler?

boun...@lists.runrev.com] Im Auftrag > von Tiemo Hollmann TB via use-livecode > Gesendet: Mittwoch, 5. Juli 2017 15:57 > An: 'How to use LiveCode' <use-livecode@lists.runrev.com> > Cc: Tiemo Hollmann TB <toolb...@kestner.de> > Betreff: AW: can I lock screen over mor

Re: can I lock screen over more than one handler?

It’s been a long time since I’ve messed with player objects… but what about putting both of the handlers into a “run” handler: on runMyHandlers LOCK SCREEN handler1 handler2 UNLOCK Screen end runMyHandlers > On Jul 5, 2017, at 10:42 AM, Tiemo Hollmann TB via

AW: can I lock screen over more than one handler?

15:57 An: 'How to use LiveCode' <use-livecode@lists.runrev.com> Cc: Tiemo Hollmann TB <toolb...@kestner.de> Betreff: AW: can I lock screen over more than one handler? Thanks Jonathan, Trevor and Sean for your comments. Meanwhile I could drill down my "flickering" proble

Re: AW: can I lock screen over more than one handler?

, it should always cover the transition. Sent from my iPhone > On Jul 5, 2017, at 10:19 AM, jonathandly...@gmail.com wrote: > > I have found that lock screen only blocks screen updates within the main LC > context. > > So, for example, it does not block whatever is happ

Re: AW: can I lock screen over more than one handler?

I have found that lock screen only blocks screen updates within the main LC context. So, for example, it does not block whatever is happening in a browser. For some reason, it also sometimes seems smoother to call a function rather than a handler, but perhaps I misperceived what was happening

AW: can I lock screen over more than one handler?

can't prevent this flickering with a lock screen right before the setting of the filename. The setting of the filename seems to release the lock screen or it takes the focus of the window off and back. Very ugly in my case. Tiemo -Ursprüngliche Nachricht- Von: use-livecode [mailto:use-livecod

Re: can I lock screen over more than one handler?

nrev.com> wrote: > > > > > > Is this possible? > > > > on handler1 > > > > lock screen > > > > -- do some stuff here > > > > send "handler2" in 0 milliseconds > > > > end handler1 > > > > > &g

Re: can I lock screen over more than one handler?

On Wed, Jul 5, 2017 at 6:45 AM, Tiemo Hollmann TB via use-livecode < use-livecode@lists.runrev.com> wrote: > > > Is this possible? > > on handler1 > > lock screen > > -- do some stuff here > > send "handler2" in 0 milliseconds > > end handl

Re: can I lock screen over more than one handler?

o Hollmann TB via use-livecode > <use-livecode@lists.runrev.com> wrote: > > Hello, > > Is this possible? > > > > on handler1 > > lock screen > > -- do some stuff here > > send "handler2" in 0 milliseconds > > end han

can I lock screen over more than one handler?

Hello, Is this possible? on handler1 lock screen -- do some stuff here send "handler2" in 0 milliseconds end handler1 on handler2 -- do some other stuff here unlock screen end handler2 in my real case the screen seems to be unlocked before handler2 has finished and

Re: Lock Screen command not locking the screen

Yes, this is also my (original) question. Is there any answer??? Peter Bogdanoff On Nov 28, 2016, at 8:07 AM, Bob Sneidar wrote: > So THAT is my problem!!! IS there any way to lock the screen to prevent card > changes from displaying? I use a method of

Re: Lock Screen command not locking the screen

So THAT is my problem!!! IS there any way to lock the screen to prevent card changes from displaying? I use a method of encapsulating certain functionality in the script of a particular card (my Database Setup card is a perfect example). By simply going to the card all the variables and

Re: Lock Screen command not locking the screen

NVM Jacque recinded in what ammounts to a completely different thread in my email app becase of the way other people use the list. Bob S On Nov 28, 2016, at 08:07 , Bob Sneidar > wrote: So THAT is my problem!!! IS there any way

Re: Lock Screen command not locking the screen

On 11/26/16 1:03 PM, dunb...@aol.com wrote: on mouseUp -- lock screen go cd 2 wait 20 put random(999) into fld 1 wait 20 put random(999) into fld 1 end mouseUp You see the new numbers appear. But if you lock the screen, you do not. You're right, and I misinformed the list

Re: Lock Screen command not locking the screen

Hi. I make a new stack with two cards. I make a field on cd 2. I put this in a button script on cd 1: on mouseUp -- lock screen go cd 2 wait 20 put random(999) into fld 1 wait 20 put random(999) into fld 1 end mouseUp You see the new numbers appear. But if you lock

Re: Lock Screen command not locking the screen

If you are looking the screen and issuing a "go" command, LC is behaving as expected. The screen is always unlocked on a card change. To do things before the card is displayed, use a preopencard handler to set things up. Jacqueline Landman Gay | jac...@hyperactivesw.com

Re: Lock Screen command not locking the screen

We'll probably need more of a look at your code and stack. On Sat, Nov 26, 2016 at 3:23 AM, Peter Bogdanoff wrote: > I’m going to another card and I want the screen to lock while controls on > the this second card are being worked on: old controls deleted, new fields > and

Lock Screen command not locking the screen

I’m going to another card and I want the screen to lock while controls on the this second card are being worked on: old controls deleted, new fields and graphics created, an image loaded from a remote server and the like. I set the lockScreen to true and then issue the commands to go to the

Re: lock screen question and detect field question

One caveat: if you are assembling a great deal of text in small chunks, you should likely do it in a variable and then toss it into the field in one go. Field updates are slower than many (most?) other things you might be doing, and one field update with 10,000 lines will be *much* faster than

Re: lock screen question and detect field question

Hi Larry, As well as the afore mentioned, all excellent comments, you can use the 'if exists(fld myField01) then' script. I also encapsulate all sorts of things in try...end try commands. These are extremely powerful although could be considered a little lazy. For example, when using iPhone

lock screen question and detect field question

if 2) Other than creating a substack to overlay my main stack with a Loading field that adds a period after Loading.. is there a way to lock the screen (so the user doesn't see the fields being created) and still show a field with the Loading... going on? Like: on createMyFields lock screen

Re: lock screen question and detect field question

On Mon, Oct 13, 2014 at 10:05 AM, la...@significantplanet.org wrote: 1) I have a program where I'm creating and deleting fields. Why are you creating them and deleting them? Why aren't the fields already there and you just show and hide them? ___

Re: lock screen question and detect field question

that. Thanks, Larry - Original Message - From: Kay C Lan lan.kc.macm...@gmail.com To: How to use LiveCode use-livecode@lists.runrev.com Sent: Sunday, October 12, 2014 8:14 PM Subject: Re: lock screen question and detect field question On Mon, Oct 13, 2014 at 10:05 AM, la

Re: lock screen question and detect field question

On 10/12/2014, 9:05 PM, la...@significantplanet.org wrote: 1) I have a program where I'm creating and deleting fields. If I try to delete a field that hasn't yet been created, I get a script error. So is there a way to first find out if the field exists? Did you look up exists in the

Re: lock screen question and detect field question

one field so I'm left with one field that can act as both as an input field and an output field. In my script, where I would normally: hide fld input show fild output I simply change the properties of my single field to reflect what I'm using it for: lock screen if the label of btn selectMethod

Re: lock screen question and detect field question

Accidently hit the Send button. Here is what I meant to type: lock screen if the label of btn selectMethod = Output then set the height of fld multipurpose to 123 set the width of fld multipurpose to 456 set the loc of fld multipurpose to 200,200 etc put

Re: Lock screen layering of stacks?

On Thu, Jul 24, 2014 at 3:57 AM, BNig bernd.niggem...@uni-wh.de wrote: could it be that what you see is related to an open Project Browser? Try your code without Project Browser open. If the Project Browser had the card(s) of the two stacks inspected and you just close it by dismissing it

Re: Lock screen layering of stacks?

Charles, your script works, without lock screen, until newest LC all the same as it should (but sadly flickering). The second,I added some lines, on mouseUp lock screen -- lock messages go stack Second go stack First -- unlock messages unlock screen put the openstacks end

Re: Lock screen layering of stacks?

... on mouseUp lock screen go stack Second go stack First end mouseUp ... then the flicker disappears, as expected, but stack Second ends up on top. Is it supposed to work like this? Cheers, - Charles -- Charles E. Buchwald CEO/Director General Museografica Digital http

Re: Lock screen layering of stacks?

Hi Charles, this works for me on mouseUp lock screen lock messages -- needed to avoid flickering go stack Second put the milliseconds into field 1 -- test if it actually was visited go stack First unlock screen -- needed to avoid flickering end mouseUp

Re: Lock screen layering of stacks?

then that would explain why lock messages helps here. Kind regards Bernd -- View this message in context: http://runtime-revolution.278305.n4.nabble.com/Lock-screen-layering-of-stacks-tp4681363p4681374.html Sent from the Revolution - User mailing list archive at Nabble.com

Re: Lock screen layering of stacks?

, 2014 6:57 am Subject: Re: Lock screen layering of stacks? Hi Charles, could it be that what you see is related to an open Project Browser? Try your code without Project Browser open. If the Project Browser had the card(s) of the two stacks inspected and you just close it by dismissing it via

Re: Lock screen layering of stacks?

stack First. A button in stack First has this script: on mouseUp go stack Second go stack First end mouseUp If I press the button, it behaves as I expect. There is a bit of a flicker, and stack First ends up on top. If add a line... on mouseUp lock

Lock screen layering of stacks?

. There is a bit of a flicker, and stack First ends up on top. If add a line... on mouseUp lock screen go stack Second go stack First end mouseUp ... then the flicker disappears, as expected, but stack Second ends up on top. Is it supposed to work like

Lock Screen on preOpenCard

Hi all, I’m navigating through cards with visual effect at all times. And in the destination card’s preOpenCard handler I lock and unlock screen. card1: _on mouseUp __lock screen for visual effect __go card 2 __unlock screen with visual effect “dissolve fast” _end mouseUp card2: _on preOpenCard

RE: Lock Screen on preOpenCard

Yes Ender, it is... Date: Thu, 13 Feb 2014 18:19:35 +0200 From: endern...@keehuna.com To: use-livecode@lists.runrev.com Subject: Lock Screen on preOpenCard It came to my mind that the latter may be pointless, former lock/unlock may encapsulate the second, hence the **pre**OpenCard

RE: Lock Screen on preOpenCard

Thanks, John… ~ Ender From: John Dixon John Dixon Reply: John Dixon dixo...@hotmail.co.uk Date: February 13, 2014 at 18:21:47 To: How to use LiveCode use-livecode@lists.runrev.com Subject:  RE: Lock Screen on preOpenCard Yes Ender, it is... Date: Thu, 13 Feb 2014 18:19:35 +0200 From

Re: Lock Screen on preOpenCard

more complex you can run the risk of piling up nested lock screen and then not having the visual effect you desire when you unlock screen. I've found the easiest solution is to: if the lockScreen is false then lock screen If you only ever use this then their will be no nested locked screens, so you

Re: Lock Screen on preOpenCard

From: Kay C Lan Then you don't have to bother about keeping track of pairs and can rest  easy at nights ... Thank you Kay, that seems the most fail-proof solution and will definitely ease my mind :) Best, ~ Ender ___ use-livecode mailing list

lock screen and visual effect advice needed

just locked, then unlocked the screen without a visual effect). I tried using: lock screen for visual effect -- --draw the new set of people into the same rect as the old ones, while the screen is locked -- show object with push down --the object occupies the same rect as the set of people

RE: lock screen and visual effect advice needed

Hi Phil... Use unlock screen instead of show object... lockscreen for visual effect --draw the new set of people into the same rect as the old ones, while the screen is locked unlock screen with push down From: p...@liverpool.ac.uk Subject: lock screen and visual effect advice needed

  1   2   >