J JDS Active Member Licensed User Longtime User Dec 3, 2019 #1 Is there a way to prevent this? It happens when using the notification I create when I start the app (to let the user know the app is active). https://www.b4x.com/android/forum/threads/killing-previous-instance-main-with-gcm.41979/
Is there a way to prevent this? It happens when using the notification I create when I start the app (to let the user know the app is active). https://www.b4x.com/android/forum/threads/killing-previous-instance-main-with-gcm.41979/
Erel B4X founder Staff member Licensed User Longtime User Dec 3, 2019 #2 A properly built application should be able to handle this case. It is not possible to prevent it from happening. Which issue have you encountered? Upvote 0
A properly built application should be able to handle this case. It is not possible to prevent it from happening. Which issue have you encountered?
J JDS Active Member Licensed User Longtime User Dec 3, 2019 #3 We've got the situation that at a certain point that the driver is unloading his truck. We are timing this so we set date, time and a identifier (and save it to a file). The driver has to wait (and needs to get back a few menu's). However he gets there faster by swiping down and tap the notification. The app gets killed and starts but the "unloading" work is not ended. If the driver had used "back" than the "work" was properly ended. We want a chronologic time schedule of the driver. 07:00 - 07:45 - driving 07:45 - 07:55 - unloading 07:55 - 08:10 - driving 08:10 - 08:30 - pause etc. Any thoughts? Upvote 0
We've got the situation that at a certain point that the driver is unloading his truck. We are timing this so we set date, time and a identifier (and save it to a file). The driver has to wait (and needs to get back a few menu's). However he gets there faster by swiping down and tap the notification. The app gets killed and starts but the "unloading" work is not ended. If the driver had used "back" than the "work" was properly ended. We want a chronologic time schedule of the driver. 07:00 - 07:45 - driving 07:45 - 07:55 - unloading 07:55 - 08:10 - driving 08:10 - 08:30 - pause etc. Any thoughts?
Erel B4X founder Staff member Licensed User Longtime User Dec 3, 2019 #4 1. Move whatever you can to the starter service. 2. Save the UI state in Activity_Pause and restore it in Activity_Create. Upvote 0
1. Move whatever you can to the starter service. 2. Save the UI state in Activity_Pause and restore it in Activity_Create.
LucaMs Expert Licensed User Longtime User Dec 3, 2019 #5 Erel said: 2. Save the UI state in Activity_Pause and restore it in Activity_Create. Click to expand... Is this still working (at that time there were no B4XView, XUI, etc.)? https://www.b4x.com/android/forum/t...applications-settings-and-state.9777/#content Upvote 0
Erel said: 2. Save the UI state in Activity_Pause and restore it in Activity_Create. Click to expand... Is this still working (at that time there were no B4XView, XUI, etc.)? https://www.b4x.com/android/forum/t...applications-settings-and-state.9777/#content
Erel B4X founder Staff member Licensed User Longtime User Dec 3, 2019 #6 LucaMs said: Is this still working (at that time there were no B4XView, XUI, etc.)? Click to expand... Yes. Tip: B4XView = View. It is just a cross platform wrapper above the same native objects. Upvote 0
LucaMs said: Is this still working (at that time there were no B4XView, XUI, etc.)? Click to expand... Yes. Tip: B4XView = View. It is just a cross platform wrapper above the same native objects.
