LiveCode Forums

What I've tried is: 1) download the Launchee stack from the following livecode lesson - http://lessons.livecode.com/m/4069/l/58672-using-custom-url-schemes This lesson includes teh statement - Once the "launchee" app is on your device you can also launch it from a browser, by going to any URL that s...

I'm developing an app for Android, but after this is working I'd like to also produce an IOS version. I'm currently adding in (hopefully) the final bells and whistles, which includes a very simple email function. I've tried both RevMail and MobileComposeMail - and was able to easily get both working...

I'm not sure if this is related - but on Android I was recently experiencing a big delay in re-drawing a new card (with associated animations) when switching between cards. After a lot of experimentation I was able to solve this by turning Accelerated Rendering OFF. If I really needed AR (it turns o...

Thanks both. Sorry about the delay in acknowledging your replies. I moved house and went on holiday. The 2nd was much more fun than the first. Next week I will experiment with the custom URL scheme feature in the Android standalone settings.

Regards

Using Livecode - how would I go about associating a particular file type with my Android app? 1) User has my app ABC on their Android device. 2) User receives an email on their Android device. The email has an attachment of type XYZ. 3) When the user opens the attachment of type XYZ, Android automat...

Thanks.

Can you give me an exact sequence of events that will trigger this problem? I'm certain that I'm seeing the same thing (only 60% of the screen redraws after the app is re-awakened) "sometimes", but I can't currently reproduce it reliably.

Regards

Solved - after 5 hours of experimentation I had "set the acceleratedRendering of this stack to true" in the PreOpenCard handler of Card 1. When I remove this, my problem goes away. I'm GUESSING that part of acceleratedRendering is making some "optimisations" in what is displayed when switch from one...

Thanks for the suggestion, but unfortunately it did not alter the behavior of the app on Android. This continues to display card 2, while executing the code on card 1. It feels like Android is issuing its own "Lock Screen" command, which I can't influence. It is getting the right end-result, but is ...

Hi I'm writing a puzzle to run on Android devices. There is some heavy lifting in determining the layout of the puzzle, so I've added a "Busy" indicator. This is just a set of dots rotating about a central point. The puzzle, and busy indicator, appear on Card 1. Card 2 is a menu page, which offers t...

Thanks both. At least I now know that it is not just something that I'm doing wrong.

Would it be worth me logging this as a bug or does RunRev already know about it?

Hi I'm using Livecode 7.1, on Windows 7 When I go into the Property Inspector for an object, - I select Colours and Patterns - Then Foreground Colour (sorry - I missed this step in my earlier description); then I'm looking at the Colours pop-up window - I select one of the 16 black Custom Colour slo...

Sorry, I suspect that this will turn out to be a daft question, but I can't work out how to retain my Custom Colours between LiveCode sessions. I have the app that I'm developing. I go through and carefully define the Custom Colours that I want using the IDE (Property Inspector / Colours & Patterns ...

Hi Where did this get to? I suspect that I'm seeing the same thing. LiveCode 7.1; deployed to an Android 5.1 smartphone for testing. The app that I'm testing currently does not implement any scaling / fullscreen commands. Upon re-activating the app, using the recent apps button, after the phone has ...

Hi Bernd

Windows 7

On your suggestion I downloaded a more up-to-date version of Livecode. I'm now on 7.1.0, and the quirk of needing to enter the Unlock Screen command twice has disappeared.

Thanks AGAIN

Kim

Hi BernD Hopefully - here it is. This is the first time I've tried to upload a file to the forum - please let me know if it doesn't work. This code is now doing what I expected, but only after I inserted an "extra" unlock screen command (after reading the earlier comments in this post). I'm just cur...