On 24.03.2014 at 18:13 Uhr + Martin Baxter apparently wrote:
Turns out that, when startup is run in the IDE, setting the stack rect
works as I would expect, the size and position are modified correctly.
But in a standalone, the stack size is set but not its position. So the
startup handler
but not its position. So the
startup handler obviously runs, but setting the stack rect doesn't have
the side-effect of setting the loc.
The same line in a preopenstack handler does work correctly however, so
it is specifically in a standalone's startup handler that this issue
appears
This:
on startup
set the rect of this stack to 100,100,300,300
end startup
Does not seem to work in version 6.6 (at least for me, on Linux)
Obviously the idea is to set the initial position of an application window.
What happens is that the window is correctly sized to 200 * 200 px, but
the
Martin.
What happens if you run this line from msg after the window is open?
Craig
-Original Message-
From: Martin Baxter mblivec...@harbourhosting.co.uk
To: How to use LiveCode use-livecode@lists.runrev.com
Sent: Mon, Mar 24, 2014 10:22 am
Subject: set stack rect in startup
that the on startup handler runs, because the stack is resized to
200 by 200, but is not placed at screen loc 300,300 as expected.
However the line does work as desired if placed into the preopenstack
handler instead of on startup.
I'm not keen to move my configuration code to the app's preopenstack if
I can avoid
If I remember correctly, the startup message isn't available to our
stacks in the IDE. Otherwise (in standalones) it should be.
Phil Davis
On 3/24/14, 7:21 AM, Martin Baxter wrote:
This:
on startup
set the rect of this stack to 100,100,300,300
end startup
Does not seem to work in
Hi Phil,
That's correct, although as Craig pointed out you can run the startup
handler in the IDE from the message box, which I did on his suggestion
as a test.
Turns out that, when startup is run in the IDE, setting the stack rect
works as I would expect, the size and position are modified
n' 2 together. I also get an
un-encrypted montreal on iOS.
I'll report it as a problem.
I know the big yellow banner at the top of my screen says don't waste space
saying thanks. So I won't :-)
--
View this message in context:
http://runtime-revolution.278305.n4.nabble.com/startup
On 11/29/11 10:36 AM, Bob Sneidar wrote:
I get the password clear, then unencrypt the stored
password and check it against the entered one. After I am done I
delete the variables.
SSL isn't supported on mobile yet, so this solution won't work there.
That's one reason I ranked SSL as a high
Hi, just wondering if there is something special about the startup handler.
The following code (executed in the IDE) does nothing:
on startup
if the cpassword of this stack is empty then
ask password Please enter a new password:
put it into temp1
ask password Please re-enter
On 11/28/11 8:31 PM, Mark Smith wrote:
Hi, just wondering if there is something special about the startup handler.
The following code (executed in the IDE) does nothing:
on startup
if the cpassword of this stack is empty then
snip
Startup is sent only once when the engine is first
On 11/28/11 10:15 PM, Mark Smith wrote:
Now, before I begin, both the stack in the IDE and tested on the iPhone
simulator report the encrypted pw as \VUw|1,A so, no difference there.
I get a difference.
The above code works fine on the IDE when the correct pw is entered
(montreal), and
also get an
un-encrypted montreal on iOS.
I'll report it as a problem.
I know the big yellow banner at the top of my screen says don't waste space
saying thanks. So I won't :-)
--
View this message in context:
http://runtime-revolution.278305.n4.nabble.com/startup-handler-tp4117800p4118166
13 matches
Mail list logo