Firsttime in activity_create

Hello Bees,

First time works correct.
The same compiled apk was first started from B4A and then from your device.
If you copy the apk file to your device yourself, you will see the message.

Succes en groeten,
Helen.

Merlot2309 said:

Hello Bees,

First time works correct.
The same compiled apk was first started from B4A and then from your device.
If you copy the apk file to your device yourself, you will see the message.

Succes en groeten,
Helen.

Click to expand...

Hello Helen,

The same problem when I copy the apk to the sdcard and install from there. If I press open after the installation it works as expected. Closing the app and start it again the wrong message is shown

Dank je,

Stephen

When you close an application it is not directly closed. The OS closes it at some time depending on the memory lacks and requirements. So when you close an app and you restart it again, FirstTime will mostly not be True because the app was not yet closed, this makes starting app faster.

Best regards.

Hoi Stephen,

Dutch: FirstTime is echt alleen de 1e keer; als je bv een database wilt kopieren van de harde schijf naar device.
Als je iets wilt instellen dat iedere keer als de app wordt gestart wordt uitgevoerd, dan gebruik je Activity_Create.
Ik hoop wel dat ik je goed begrijp.

Helen

klaus said:

When you close an application it is not directly closed. The OS closes it at some time depending on the memory lacks and requirements. So when you close an app and you restart it again, FirstTime will mostly not be True because the app was not yet closed, this makes starting app faster.

Best regards.

Click to expand...

Ok I understand, took out the battery and then it works ok.
Is there a way to force the closing of an app.
For now I just use a global variable and reset it when the back key is pressed.

Thanks,

Stephen

Merlot2309 said:

Hoi Stephen,

Dutch: FirstTime is echt alleen de 1e keer; als je bv een database wilt kopieren van de harde schijf naar device.
Als je iets wilt instellen dat iedere keer als de app wordt gestart wordt uitgevoerd, dan gebruik je Activity_Create.
Ik hoop wel dat ik je goed begrijp.

Helen

Click to expand...

Hoi Helen,
Gebruik het inderdaad om te kontroleren en indien nodig kopieren van
een database, maar ook om wat variabelen te zetten.

Dank je,

Stephen

bees said:

Is there a way to force the closing of an app.

Click to expand...

I know Erel doesn't like it, but you could use ExitApplication which forces the app to close (FirstTime should be true on subsequent runs)

FirstTime vs Global

In the example of SMTP you put the initialisation in Activity_Create/ Firsttime. I had problems with it as firsttime did not always fire (is logical, but not easy).

I therefore moved the initialisation code to Globals which works fine.

Sub Globals
SMTP.Initialize("smtp.gmail.com", 465, "xxx@gmail.com", "xxx", "SMTP")
SMTP.UseSSL = True 'Gmail requires SSL.
End Sub


Now I am wondering if this is officially supported as in all text that I read, Global seems to be for initialisation of variables only.

Can you shed some light about the differences?

It is better to start a new thread for this question.

SMTP should be declared as a process global variable and be initialized only when FirstTime is true.

boten said:

I know Erel doesn't like it, but you could use ExitApplication which forces the app to close (FirstTime should be true on subsequent runs)

Click to expand...

Well, I do like it, as for now ExitApplication releases me from some unwanted behaviour that i couldn't otherwise correct.

My current project shows data from an CSV-file into a choice of three listviews of which one at a time is shown (using the Visible parameters). From this listview a choice is made for an item that then will be shown for all fields of that item in a new listview. After the user closes this view, it returns to the former.

This all works well, except when the app gets closed by the user with the BACK-key and then restarted from the icon or from the recent apps list.

Then, when an item is selected and the second list pops up, I get an error message which states that an index of an array I keep track off is out of bound, although it should have reinitialized to 0 and I have no idea why the program is getting into the routine that uses the variable.

I see the same behaviour and exact the same error either if I show the second list in a separate activity or if I show the second list in the same activity but in a different panel.

ExitApplication, as for now, solved this problem for me. I just wonder what really is the problem, though.

Have a read of the Android Process and activities life cycle, it might help you better understand what Android does with an Activity when you exit it or move on to another Activity.

Are you using Process_Global variables and finding that when you return to your Acitvity that the Process_Global variable is no longer initialized?

Martin.

warwound said:

Have a read of the Android Process and activities life cycle, it might help you better understand what Android does with an Activity when you exit it or move on to another Activity.

Are you using Process_Global variables and finding that when you return to your Acitvity that the Process_Global variable is no longer initialized?

Martin.

Click to expand...

Thanks for the link, I have read it a few times before. As far as it is possible, I understand closing and resuming activities. But it doesn't explain why the described out of range message is popping up.
The only place where this variable i is used is in the second activity and it is not shared other then in this sub that populates a list of 46 items. Once closed and restarted the activity reports an out of range error for i, whose value then is 47.

With ExitApplication to close the activities, I know it shuts down the whole activity so it has to be rebuild when restarted. Since this prevents the out of range error, I'm fine with that.

In the meantime I have moved from starting a second activity to showing just a second panel above the first one. This works out very fine and is a bit faster. Only drawback is that I will need an additional 4 panels for showing data later in the app, which could make it difficult to define in the Designer.