LiveCode Forums.

-

But not on Android Emulator.
Nor physical Android device.

That's odd. I ran it in the emulator on OS X and it worked okay. I didn't try my tablet. If I get some time I'll do that later today.

Edit: Got curious so tried it immediately. I compiled a standalone and moved it to my tablet running Froyo 2.2. It worked. I'll enclose the test stack so you can see if it runs for you.

-

-

-

-

For the keyboard problem, delete the hidden field (id 1004) on card 1. I used that to create the title image, but it isn't needed for anything now. The engine is probably trying to focus on that field.

The button issue may be related to a strange problem I had when running your example stack. The opencard message was sent but immediate exited. Even though you'd commented out the environment check, it seemed to block the handler execution. When I removed the three lines from the script entirely it worked again. Probably some kind of engine bug, but try deleting those commented lines. What may be happening is that the button doesn't have time to redraw because the opencard handler is blocking any updates.

BTW, I suspect the reason your original splash attempt didn't work is because you used card 3. The engine will always go the first card of the mainstack when the stack opens, so that's the best place to put the splash. Basically it takes advantage of the native engine behavior without having to do any redirects or insert anything into the message path.

I think you made my splash stack look much, much better.

-

-

This is helpful! Thanks. Will it also work on iOS?

Steve

steve10 wrote:This is helpful! Thanks. Will it also work on iOS?

You won't need it. iOS has built-in splash capabilities and the standalone settings dialog allows you to set it up. It's all automatic on that OS.

-

Like "Jackie". More: http://jacque.on-rev.com/jacque/jacque.irev