J JaunLukePicard Member Licensed User Longtime User Sep 18, 2015 #1 If I understand it correctly we can use the Starter Service to start the application as Earl indicated and initialize things that are used throughout the application globally. In my case this would seam a good place to initialize use of a database that several Activities would need access to. Would I be correct in this asumption? From Starter we have: Process_Globals Service_Create Service_Start and Service_Destroy Do I call the Starter Service from the Main Activity. Think so. Then I should have access to the database throughout the app? Can I use the Starter Service to initialize a class used throughout the app? I just don't want to create too much extra work Last edited: Sep 18, 2015
If I understand it correctly we can use the Starter Service to start the application as Earl indicated and initialize things that are used throughout the application globally. In my case this would seam a good place to initialize use of a database that several Activities would need access to. Would I be correct in this asumption? From Starter we have: Process_Globals Service_Create Service_Start and Service_Destroy Do I call the Starter Service from the Main Activity. Think so. Then I should have access to the database throughout the app? Can I use the Starter Service to initialize a class used throughout the app? I just don't want to create too much extra work
R Roycefer Well-Known Member Licensed User Longtime User Sep 18, 2015 #2 Don't call the Starter Service yourself. It is called automatically. The Starter Service's Service_Create and Service_Start will have been executed before the Main Activity's Activity_Create. You can do your initialization of stuff in Service_Create. Upvote 0
Don't call the Starter Service yourself. It is called automatically. The Starter Service's Service_Create and Service_Start will have been executed before the Main Activity's Activity_Create. You can do your initialization of stuff in Service_Create.