in procedure app you forgot the argument x, which is required there
you can't use labels in the background, use a notification instead or use the text to speech component or use the notifier to log something you can read in logcat, Capturing Device Logs using adb logcat
if you want to trigger the Clock1.Timer event in the background, then you have to register that event for background processing and use a background handler which looks like a procedure...,how to register events see for example here Battery checker reminding you to unplug when fully charged
Both run in the background, a process runs in foreground mode and needs to display a permanent notification
You might want to read post 1 of the itoo thread again
Itoo is for advanced developers who do not hesitate to follow the guidelines memtioned earlier and are ready to experiment a little bit
here is a test project for you, which does more or less what you were trying to do
after clicking button start you hear a voice saying "This is the beginning", the app will close and after 5 seconds the voice will say "This is the end"
Take a look at what i have done based on Taifun app.
App is running also in android home screen and android lock screen and both.
When redisplay app the label is up to date and that is very good.
I hope i can continue in this direction with my app.
this is because you never closed the app... you just move it to the back and it was still running... to close the app use the close application block...
to be on the safe side use the FetchProperty method to fetch label text in the Screen.Initialize event
what you want is to reliably have the app running in the background
if you only move the app to the back, it is still running but can be closed any time by the Android operating system in case more system resources are required. Also not everything is doable in this state.
please also understand the purpose of the valueIfTagNotThere socket... in your case you use numbers, so that default value should be 0 and not the text zero
if you use itoo correctly, then yes
currently you use a clock running in the foreground and another clock in the background... that clock in the foreground might be stopped by Android if you move the app to the back...
see my new example how to do it correctly only in the background...
I have some doubts about the extension, i have already made some work using local variables and store/fetch property to transmit values, is it good practices ?
Speed of calculation is important for real time and i wonder if store/fetch property do not make some lag.
But now i have to manage some lists, labels, buttons and canvas with sprites and i wonder how to do.
