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

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 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: 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
link: Thanks @oparra that's an avenue I will pursue.

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

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: Newbie question. I modified the Two Activities example to see if I could learn how to call multiple activities without an event. I copied Activity2,

Hi @beelze69 Glad that you understood the power and methods of B4XPages. I think you can mark Lucas post as solution. Actually we are so wired on Android Activity life cycle (this true if you try in AStudio or other Android development tools) that it takes a while to understand power of B4XPages.

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: 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: 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: 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

Clearly you don't understand neither the underlying workings of the "wait for" neither the way ANDROID handles activities... You should start by reading the "Activities Life Cycle tutorial"... It has well aged over the years, just like a good wine... After reading it, I'm sure it will bring you a co

Move all Wait For's to Activity_Resume. This is just how resumable subs work with Android's app life cycle. Android calls Activity_Create and upon it finishing, Activity_Resume is called (in B4A's case). With the first Wait For in Activity_Create, you are pretty much exiting/finishing Activity_Creat
link: Hi to all! I have an old project and I needed to update it, but now I have sync problems with subs in Activity_Create and Activity_Resume, in which no

Powered by ColBERT