On Thu, Jul 24, 2014 at 3:57 AM, BNig 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
> via the red dot
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 open
Hi Scott,
I have a commercial project... the most complex thing I've done in LiveCode,
with substacks, stack files, and lots going on. I have some "flickering" there.
I figured it was the way I'm using lockScreen, so I made a test stack. While
testing with the test stack I noticed this odd behav
gt; encountering strange behavior it is a good idea to start LC without Project
> Browser.
>
> If it is the Project Browser then that would explain why "lock messages"
> helps here.
>
> Kind regards
> Bernd
>
>
>
> --
> View this message in con
r.
If it is the Project Browser 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
If it is the Project Browser 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 mail
n 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 i
That is indeed some odd behavior.
What end result are you trying to achieve?
Regards,
Scott Rossi
Creative Director
Tactile Media, UX/UI Design
On 7/23/14 9:19 PM, "Charles E Buchwald" wrote:
>I feel like I'm missing something really basic here...
>I have 2 stacks.
>Stack "Second" overlaps
I feel like I'm missing something really basic here...
I have 2 stacks.
Stack "Second" overlaps 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.
