Search Results

Activity_Pause is the last place to save important information. Generally there are two types of mechanisms that allow you to save the activity state. Information that is only relevant to the current application instance can be stored in one or more process variables. Other information should be sto
link: After a while an activity goes to the background android will kill it so its importent to store your variables so if you send an activity to the bac

I have a tablet that sits in a dock In general the dock just supplies power to the tablet When the tablet is removed from that dock my B4XPages application seems to be killed and restarts as if for the first time This does not happen when connected to a normal power supply and plugging it in and unp
link: Thanks @oparra that's an avenue I will pursue.
link: Some time ago something similar happened to me, the solution was to check the configuration of the tablet so that the energy saving is not activated a

Basic activity life-cycle issue... Any activity, being it a B4x created app or any other, when in background for long risk being terminated by the OS and the ap will start fresh when brought to foreground. A way to managed and minimise this standard behaviour is to use the StarterService to manage t
link: In my opinion, if other panels do not act as, say "pop-ups", yes, you could or perhaps should move them to another activity. It depends on what you're
link: Hi, My app runs a first activity. With a call, I hide the main panel and load a second. Meanwhile, I got a service module running. Problem: when the

I also developed a strategy for developing and maintaining the apps. In b4i, the ActivityClass handles the execution of the relevant Android activity life-cycle subs. It uses a NavigationController in the Main b4i module to handle the UI for the b4a Activity module. Recommended strategy for devel
link: I made a significant update to the class and examples. These changes make the apps mimic the activity life cycle of Android very closely. See the tab
link: I made an update to ActivityClass.bas and cross_platform_starter_1.2.zip. In the b4i project there were some changes to subs in the Main module that
link: I found and fixed a few bugs/omissions. There was a bug in Map_B4X, so you will need to replace this in your projects. I missed the step of call

I recommend you to start with this very important tutorial: Android Process and activities life cycle 1) Activity_Pause of the current activity will be called and then the next activity will be started. Events will only be raised in the visible activity. Use a service if you need a timer to continu
link: Thanks Erel. I have read the "Activities Process and Activities Life Cycle" several times, but probably not to the depth that I should have because c
link: Do you load all 20 layout files to the same activity? Might be better to use multiple activities instead. As a general rule you need to load the acti
link: Sorry it took so long to reply as I was busy making up the infographic (below): 35128 The infographic shows how my current game operates -- everyth

The OS is only ever running one of your activities at a time. Your activity 1 would call activity 2, in activity 2 you have a "next" button which calls activity 3, or back to 1 if cancel, etc. See: https://www.b4x.-process-and-activities-life-cycle.6487/
link: It's not a matter of fighting, you have to understand that once you start the 2nd activity, the 1st one is literally no longer running, so there's no
link: Thanks for your reply. I watched that video twice before I posted; I believe you that the OS only runs one activity at a time. But there should be a w
link: OK, Jeffrey, I understand better now. What you said about "there's no place to "go back to" when the 2nd activity is finished" is very, very helpful.

There is a special thread that explains exactly this, called "activities lifecycle"... You should give it a peek... Wich I'm having trouble finding it.... Still, I found this one, which is as good... https://www.b4x.-life-cycle-of-a-b4a-activity.40515/#post-242241
link: Thanks both. So after that first time it is never true for the full life cycle of the app? I'd thought that it is true when loading the activity fr
link: Don't worry about it. If the Activity is no more needed the system the system will destroy it. But "when" belongs to Android, if you run in low memory
link: imagine this, Activity3 is a set-up activity, where you define for example, a typeface for the text of some of your views. now imagine that you set th

Then I think you should handle such situation in Activity_Resume and maybe you should make something on Activity_Pause https://www.b4x.-life-cycle-of-a-b4a-activity.40515/
link: Maybe this could be helpful: https://www.b4x.-process-and-activities-life-cycle.6487/

The design consideration behind B4XPages is that it simplifies the activity cycle of Android by eliminating Pause and Resume. This helps in making the App cross-platform (Desktop, Android, iOS), but it also means a commitment to a given orientation. (As I mentioned, you can detect first how the user

Read about activities life cycle: create, pause and resume events. https://www.b4x.-process-and-activities-life-cycle.6487/#content
link: Cableguy...thanks for pointing me to the activity_resume. This is exactly what I was looking for instead of recalling the activity_create. Makes a l
link: Take care to read carefully activity life cycle. Android is not simple...

Powered by ColBERT