4.3 version

[Mr. Kibernetik]

Do you mean that SB is removed from the background as well? If not, could you implement the EXIT statement in that way?
(I frequently use a little SB app. When i forget to delete SB from the background, my iphone is totally dead after some hours, which is very nasty sometimes).

I would like to, but it is impossible for application to remove itself from memory completely. Frankly speaking, it is even not permitted to exit application from inside application itself - in Apple they think that only user can close app by pressing Home button, and not in any other way. So, any kind of programming exit violates Apple's guidelines, and they have no proper means to perform this task.
I think that EXIT should terminate all activity inside application, but memory will not be automatically freed.

[Henko]

I think that EXIT should terminate all activity inside application, but memory will not be automatically freed.

Well, that should do the trick. I think that just occupying memory does not take much power. Overnight, the iPhone looses only a small amount of power, even with a lot of apps in the background, except when SB is one of them.
In the present state, SB in the background probably eats all processor cycles available, heating up the phone.

[Mr. Kibernetik]

In the present state, SB in the background probably eats all processor cycles available, heating up the phone.

When this happens? If sB app is idle and is just in files list? Or if some program was running and you turned off the device?

[Henko]

In the present state, SB in the background probably eats all processor cycles available, heating up the phone.

When this happens? If sB app is idle and is just in files list? Or if some program was running and you turned off the device?

I am a bridge player and made a SB app to be used during house bridge sessions: 4 players who play 3x8=24 rounds .
Each round starts with bidding; the winning contract is entered in the app. Trying to save power, i then send SB to the background with the home button and press the on/off button to deactivate the screen.
The round is then played,which takes 10 to 15 minutes.
I then activate the phone with the home button and bring up the app to enter the results. After that a new round begins.
So, the app is active about 1 to 2 minutes each round and 10 to 15 minutes inactive with a black screen.
Yet the phone starts warming up and after about 3 hours the battery is almost depleted.
When i deactivate the app, it is waiting for input using a list with a command like:
wait : if list_selected("list_id")=-1 then wait
I cannot stop the app, because data would be lost. I just send it to the background.

Another exemple is the password encryption app (in the program section of this board). It is also using interface objects like a list and input fields. If i use it and forget to remove it from the background, i find the phone dead in the morning.

[Mr. Kibernetik]

Application will be updated for 64-bit devices.

[basiccode]

I don't think smart basic runs in the background.
If you find smartBasic or any other app depleting your battery then it's the iOS device. There seems to be something fishy with iOS devices when it comes to long term usage.

[Mr. Kibernetik]

I don't think smart basic runs in the background.
If you find smartBasic or any other app depleting your battery then it's the iOS device. There seems to be something fishy with iOS devices when it comes to long term usage.

Well, actually it runs. Even if device is off. I made it like this to be able to play music in the background. Now I have to do something with that...

[basiccode]

I just remembered with the new audio features smartBasic does run in the background but your battery still should not go flat, it is definitely an iOS or device issue.
Try leaving any other app running and see if the same thing happens.

[Henko]

I don't think smart basic runs in the background.
If you find smartBasic or any other app depleting your battery then it's the iOS device. There seems to be something fishy with iOS devices when it comes to long term usage.

That thought struck my mind too. But i didn't need testing to know that the device is ok. Overnight, with some apps in the background (but no navigation apps and SB) the battery usage is only a few percentages.
The solution is to not forget to remove certain apps from the background, but the bridge program i mentioned must not be stopped during the bridge session. It would require additional programming (saving and reloading intermediate statusses to/from a file) and extra handling between each round.
I'll wait and see if mr. K comes up with something.

[basiccode]

The same thing happened to me with the battery but for all apps.