Steve
Scott Rossi wrote:
>
> Hi List:
>
> Am I dreaming or did "lock screen" used to affect only the default stack
> when implemented? I could have sworn you could lock the screen of one
> stack
> while doing something in another.
>
> I have a palette
Hi List:
Am I dreaming or did "lock screen" used to affect only the default stack
when implemented? I could have sworn you could lock the screen of one stack
while doing something in another.
I have a palette that is supposed to show status of updates occurring in a
topLevel stack
8, at 12:34 PM, Eric Chatonet wrote:
Bonjour Thomas,
Actually, lock and unlock screen work as a pair:
They are 'stacked'.
This means that after two 'lock screen', an 'unlock screen' is not
enough to unlock screen: you need two of them.
Parity between lock and unlock sc
Tom,
Deleting an object that contains a running handler would cause an
error. Looking at your original example again, it is logical that your
screen unlocks:
on SomeHandler
lock screen
send "SomeOtherHandler pParam" to me in 5
end SomeHandler
You tell Rev to continue executing s
Jac,
It is not however staying locked. Could it be because the original
handler is in a group that is deleted as a part of the handler jumping?
Tom McGrath
On Apr 22, 2008, at 3:28 PM, J. Landman Gay wrote:
Thomas McGrath III wrote:
Thanks Mark,
You answered both of my questions. They nee
Thomas,
Actually, lock and unlock screen work as a pair:
They are 'stacked'.
This means that after two 'lock screen', an 'unlock screen' is not
enough to unlock screen: you need two of them.
Parity between lock and unlock screen is compulsory :-)
If you are lost
Thanks Jim,
This time I was not but i have been confused at other times by that
while walking through a script.
It turns out the unlock was happening across multiple handlers. I need
to figure a way around that?
Thanks again,
Tom McGrath
On Apr 22, 2008, at 12:03 PM, Jim Ault wrote:
A
Thomas McGrath III wrote:
Thanks Mark,
You answered both of my questions. They need to be paired AND the reason
my screen was unlocking was because the handler that
locked it was finished and a new one was started.
Any ideas on how to keep the screen locked across multiple handlers???
The s
Thanks Mark,
You answered both of my questions. They need to be paired AND the
reason my screen was unlocking was because the handler that
locked it was finished and a new one was started.
Any ideas on how to keep the screen locked across multiple handlers???
Thanks again,
Tom McGrath
On
Bonjour Thomas,
Actually, lock and unlock screen work as a pair:
They are 'stacked'.
This means that after two 'lock screen', an 'unlock screen' is not
enough to unlock screen: you need two of them.
Parity between lock and unlock screen is compulsory :-)
If
unlock screen in between. Or what else is causing the screen update.
>
> Example
>
> on SomeHandler
> lock screen
> send "SomeOtherHandler pParam" to me in 5
> end SomeHandler
>
> --Can still see screen update here
>
> on SomeOtherHandler pParam
> l
Hi Tom,
Locking the screen before switching windows can cause the screen to
inlock or windows to be rendered completely while. Don't do this.
If you want to unlock the screen, you need to issue the unlock command
at least as often as the lock command. The screen is automatically
unlocked
Hello Fellow Revolutionaries,
I need to find out if multiple lock screens will actually cause an
unlock screen in between. Or what else is causing the screen update.
Example
on SomeHandler
lock screen
send "SomeOtherHandler pParam" to me in 5
end SomeHandler
--Can still see scr
he stack, but do not want to show it while a
handler runs in another stack, lock screen will not be very useful.
Lock screen most often only affects the current stack.
Also of note is that style and mode changes sometimes make stacks
flicker.
have fun
Björnke
Thank you very much, Bjömke,
another stack, lock screen will not be very useful.
Lock screen most often only affects the current stack.
Also of note is that style and mode changes sometimes make stacks
flicker.
have fun
Björnke
On 10 Jun 2007, at 14:20, André.Bisseret wrote:
Hi,
I have a main stack from which I can creat
button on the
modal stack..
Well, when this new stack has been created it should be on top of the
screen.
In several places in the handlers (specially at the end), I put « go
to stack « name forename » AND in several places also « lock screen »
bu anyway, the main stack is always
Hi
Thanks to everyone who gave me help and advice I have rewritten my
handlers following your advice and removed all occurrences of select
etc. However I still have to use multiple occurrences of lock screen
but many fewer. In fact, I only have to use and extra two more than
the number of
On 5 Apr 2007, at 20:14, Tereza Snyder wrote:
You don't need to select an object to move it or rename it or group
it. If you have its long ID, which you can obtain after you make it
either with "create" or with "clone": e.g.
clone grp "unsweetened"
put the long ID of it into tMyGrp1
set th
Hi Tereza
I had looped through the names in the groupnames property, selecting
each group as I went and building a complicated do statement. It's
nice to be reminded that there is nearly always a simpler way to do
things in Revolution.
Thanks for the tip.
On 05/04/07, Tereza Snyder <[EMAIL PRO
On Apr 5, 2007, at 11:48 AM, Ian McKnight wrote:
Thanks for the suggestion but I believe that I have to select the
object at some stage because it needs to be moved and renamed etc.
You don't need to select an object to move it or rename it or group
it. If you have its long ID, which you c
Hi Jim
You suggestion has done the trick! I put a lock screen command into a
loop with a multiplier based on the number of times my master group is
cloned and guess what? they all cancel out at the end- and I don't see
the move to card 1 at all. Really strange!
Anyway thanks for your hel
Hi Eric
Thanks for the suggestion but I believe that I have to select the
object at some stage because it needs to be moved and renamed etc.
Thanks again
--
Regards
Ian
===
Ian McKnight
[EMAIL PROTECTED]
===
___
I don't know about the new versions of Rev, but the original HCard lock
screen was a "stack of them", such that if you wanted to unlock the screen
during a single handler, you had to do as many unlock's as lock's. The
method I used was something in a repeat loop.
Your q
lockscreen is true
On 05/04/07, Eric Chatonet <[EMAIL PROTECTED]> wrote:
Hi Ian,
On the other hand:
As you know it: lock and unlock screen go by pairs.
So have you tried to lock the screen twice or three times and unlock
it until the lock screen = false?
Really dirty but worth a try ;-)
Y
Hi
It's definitely something in the loop I just described. When I loop 6
times and put 16 lock screen statements at the top of the main script
everything works as it should ie I don't see card 1.
However if I loop 7 times (for a 7 period day) I must put an extra 2
lock screen messa
4/07, Eric Chatonet <[EMAIL PROTECTED]> wrote:
Hi Ian,
On the other hand:
As you know it: lock and unlock screen go by pairs.
So have you tried to lock the screen twice or three times and unlock
it until the lock screen = false?
Really dirty but worth a try ;-)
You can also add in some p
ow it: lock and unlock screen go by pairs.
So have you tried to lock the screen twice or three times and unlock
it until the lock screen = false?
Really dirty but worth a try ;-)
You can also add in some places: put the lockscreen & cr after msg to
understand which statement makes the lock scr
Hi Eric
Thanks for the suggestions. I have just made the master group visible
on my card 1 and removed the statement to make it visible from the
script but it is still occurring. Script debug mode is off and I am
seeing the entire script execute - so the lock screen command is not
locking
Hi Ian,
I suspect that unlock screen automatically occurs when you set the
visible of an object to true.
Could you return to cd 2 before setting the visibility for all these
objects?
Or, better, do all the job from cd 2: clone grp "Master" of cd 1, set
the name of last grp of cd 1 to , etc.
Hi Richard
To create my table I have a hidden group consisting of 6 fields on
card 1. When the script executes this group is selected, cloned, made
visible and the clone renamed. This is then re-cloned anything from 6
to 10 times, with each new group being renamed, its constituent fields
renamed
. The
scripts are located at the stack level and this process works as
expected.
However I want to hide the creation of this 'table' from the user so I
lock screen
go card 1
-- create table
go card 2
unlock screen
but the lock screen doesn't work, I still see the table being pu
1, cloning and renaming
a hidden group and assembling the table then going back to card 2. The
scripts are located at the stack level and this process works as
expected.
However I want to hide the creation of this 'table' from the user so I
lock screen
go card 1
-- create table
go car
Dear fellows and gals,
I am working with a script that cycles a bit during a mouseDown event
and checks and populates a field for display. Anyway on the Mac I
lock screen and populate the field and then unlock sreen. It works
and even though the item is still cycling there is no flicker
On 11/20/05 1:20 PM, "Ken Ray" <[EMAIL PROTECTED]> wrote:
> On 11/20/05 8:26 AM, "Raymond E. Griffith" <[EMAIL PROTECTED]> wrote:
>
>> I wonder if adding the following might achieve what you are looking for:
>>
>> on mouseUp
>>open invisible stack "OtherStack" to false
>
> Actually you
On 11/20/05 8:26 AM, "Raymond E. Griffith" <[EMAIL PROTECTED]> wrote:
> I wonder if adding the following might achieve what you are looking for:
>
> on mouseUp
>open invisible stack "OtherStack" to false
Actually you don't need the "to false" part of this (I'm sure it was a
copy/paste error
t;>>>> Hi everyone,
>>>>>
>>>>> I'm using Mac OSX. Why is it that when I use the following script I get
>> a
>>>>> flash of stack "otherStack"? I thought lock screen wouldn't allow that
>> to
>>>>&g
In a message dated 11/19/05 11:58:23 PM, [EMAIL PROTECTED] writes:
> >>> Hi everyone,
> >>>
> >>> I'm using Mac OSX. Why is it that when I use the following script I get
> a
> >>> flash of stack "otherStack"? I thought lock scr
ript I get a
>>> flash of stack "otherStack"? I thought lock screen wouldn't allow that to
>>> happen.
>>>
>>> on mouseUp
>>> lock screen
>>> push cd
>>> go stack "OtherStack"
>>> pop
In a message dated 11/19/05 2:19:47 PM, [EMAIL PROTECTED] writes:
> > Hi everyone,
> >
> > I'm using Mac OSX. Why is it that when I use the following script I get a
> > flash of stack "otherStack"? I thought lock screen wouldn't allow that to
> &
On 11/19/05 12:52 PM, "[EMAIL PROTECTED]" <[EMAIL PROTECTED]> wrote:
> Hi everyone,
>
> I'm using Mac OSX. Why is it that when I use the following script I get a
> flash of stack "otherStack"? I thought lock screen wouldn't allow that to
> happ
Hi everyone,
I'm using Mac OSX. Why is it that when I use the following script I get a
flash of stack "otherStack"? I thought lock screen wouldn't allow that to
happen.
on mouseUp
lock screen
push cd
go stack "OtherStack"
pop cd
unlock sc
Hi Lars,
in additon to what Scott Rossi posted, you can always access data
from stacks that are not open!
(Substacks or even stackfiles on the hard disk!)
Just use the exact and long descriptor.
Like:
...
put CR & fld "xyz" of cd abc" of stack "cde" after fld "bbc" of cd
"mtv" of stack "a
fault stack will not be visible
until the current handler ends you call unlock screen. Lock screen is often
used when initializing a stack's objects, populating objects with content,
or employing a visual effect, such as:
lock screen
go next card
unlock screen with visual dissolve
Locking scr
Thanks for responses. I saw the debug mode note, but I am not in
debug mode and it's both the IDE and the standalone. Here's where
the flicker occurs:
1. lock screen
go stack "abc"
go stack "cde" -- a smaller stack that is now in front of
"
If you are running it in the development environment, did you see this note
on lock screen?
When using script debug mode, the screen cannot be locked and the lock
screen command has no effect.
At 03:26 PM 6/14/2005, you wrote:
I was wondering what it takes to get lockScreen to do what the
On 6/14/05 3:26 PM, Lars Brehmer wrote:
I was wondering what it takes to get lockScreen to do what the docs say
it does. I have several scripts that do all kinds of things that
should be hidden, but it still looks like all of these things happen
after unlockScreen with all kinds of flicker
I was wondering what it takes to get lockScreen to do what the docs
say it does. I have several scripts that do all kinds of things that
should be hidden, but it still looks like all of these things happen
after unlockScreen with all kinds of flicker. For some things I took
some old advic
Thank you so much! Both suggestions cleaned everything right up!
I keep learning more 'n more every day. Never had those handlers in the
Hyper/Super products.
> Your openstack handler is a little non-standard; normally invisible
> things are done on preOpenStack where locking isn't necessary. In
I can:
>
> Here is a snippet of code from stack "A" that requests stack "B" to open.
>
>lock screen
>sheet stack "B"
>unlock screen
>
> (I would have much prefered to say 'sheet cd x of stack "B"', but that
> syn
On 9/12/04 5:59 PM, Arthur Urban wrote:
>>>Lock screen/unlock screen does not seem to work with stacks
>>
>>opened as
>>
>>>modal. Is this a known bug by any chance?
>>
>>I'm not sure I'm clear on what you are asking, but a common
&
> > Lock screen/unlock screen does not seem to work with stacks
> opened as
> > modal. Is this a known bug by any chance?
>
> I'm not sure I'm clear on what you are asking, but a common
> misperception is that "lock screen" means "lock the whol
On 9/11/04 2:39 PM, Arthur Urban wrote:
Lock screen/unlock screen does not seem to work with stacks opened as modal.
Is this a known bug by any chance?
I'm not sure I'm clear on what you are asking, but a common
misperception is that "lock screen" means "lock the whole s
Lock screen/unlock screen does not seem to work with stacks opened as modal.
Is this a known bug by any chance?
~~~ Arthur
"Never interrupt your enemy while he is making a mistake."
___
use-revolution mailing list
[EMAIL PROTE
vokes window-related messages.
Just make sure that the "lock/unlock screen" block is within the
"lock/unlock messages" block.
on mouseup
-- lock screen
growit
--unlock screen
end mouseup
on growit
lock messages
lock screen
put the width of this stack into sw
put the he
On 7/30/04 4:34 AM, Mark Schonewille wrote:
>> The "lock messages" command does not stop all messaging. It mostly
>> only stops the navigation messages -- such as openCard, openStack,
>> preOpenCard, etc.
>
>
> This is not true. The "lock messages" command stops all messages that
> are not sent fro
On Jul 27, 2004, at 8:28 PM, Erik Hansen wrote:
you intended,
set the height of this stack to sh+1
right?
Yes, this was just a simple example to do two things: 1) evoke the
resizeStack message, which is where I was having problems in my stack,
and 2) provide a visual cue that the button script wa
n preceded by a Lock Screen command. This looks to me like a
bug.
Regards,
Howard Bornstein
---
D E S I G N E Q
www.designeq.com
___
use-revolution mailing list
[EMAIL PROTECTED]
http://lists.runrev.com/mailman/listinfo/use-revolution
> On 7/27/04 2:51 PM, Howard Bornstein wrote:
> > on growit
> > lock messages
> > -- This causes the resizeStack handler
> > -- to trigger.
> > put the width of this stack into sw
> > put the height of this stack into sh
> > set the width of this stack to sw+1
> > set the height of
On 7/27/04 2:51 PM, Howard Bornstein wrote:
Whew, this one took me two days to track down. I'd appreciate it if
someone can confirm this.
Create a stack with one button. In the button put this script:
on mouseup
lock screen
growit
unlock screen
end mouseup
on growit
lock mes
Well, I don't get any messages if I comment out the lock/unlock screen
(as expected). I only get one message with them in. I'm not sure why
you'd expect two in any case. Do you expect the Answer stack to
generate a resizeStack message also?
No, actually I was guessing that "unlock screen" might
On Jul 27, 2004, at 4:00 PM, Brian Yennie wrote:
This is just a guess, but perhaps unlocking the screen sends a
resizeStack message? What happens if you change your resizeStack
handler to "answer the ticks" and comment out the lock/unlock messages
code? Do you get two resizeStack messages?
Well,
u describe...
Whew, this one took me two days to track down. I'd appreciate it if
someone can confirm this.
Create a stack with one button. In the button put this script:
on mouseup
lock screen
growit
unlock screen
end mouseup
on growit
lock messages
-- This causes the resizeStack han
Whew, this one took me two days to track down. I'd appreciate it if
someone can confirm this.
Create a stack with one button. In the button put this script:
on mouseup
lock screen
growit
unlock screen
end mouseup
on growit
lock messages
-- This causes the resizeStack handler to tr
Don Pederson wrote:
> How do I keep users from moving the window around on the monitor screen. I
> would like to lock the position centered on the monitor screen.
You can remove the drag bar by setting the decorations of the stack to none.
--
Richard Gaskin
Fourth World Media Corporation
D
How do I keep users from moving the window around on the monitor screen. I
would like to lock the position centered on the monitor screen.
Thanks,
Don
--
Dr. Donald Pederson
School of Music
University of Tennessee
1741 Volunteer Blvd.
Knoxville, TN 37996
[EMAIL PROTECTED]
(865) 974-7550
When I uncomment the lock screen message, then buttons with icons and
radio buttons do not print correctly. I added the lock screen because
on Windows all the cards were flashing by as the print job was
generated. This does not appear to happen on OS X. Is lock screen known
to break printing
At 11:07 PM -0800 1/12/02, John Cuccio wrote:
>1. When I set the lockscreen to true I still get a flick of the screen.
>White then back to the starting point. I am useing push & pop card.
>
>on handler
>lock screen
>push card
>go to stack "order"
>pop card
&g
op card.
on handler
lock screen
push card
go to stack "order"
pop card
end handler
___
use-revolution mailing list
[EMAIL PROTECTED]
http://lists.runrev.com/mailman/listinfo/use-revolution
68 matches
Mail list logo
