Android Question Ho to realize a class for obtain a MsgBox usable from code in a module?

[amorosik]

"...The best solution is to use a class instead of a code module. You can then initialize the class in each of the activities. It will allow you to share more features between the activities..."
These are the word of Erel
The question is: how write a class to obtain a messagebox usable from code/service module?
For example, an app with 3 form and 1 module
When app start form1 is displayed, then operator press and go on form2, on module1 an sms is received and the code on module1 need to visualize a message
How write a class to display the messagebox and how instantiate it in form1, form2, form3?

 

[Alessandro71]

Convert the code module to a class and remember a service can’t show dialogs, just toast messages

 

[Sagenut]

To just show a MsgBox I think it's not needed to make a Class.
Try this.
It has a Service that every 5 seconds show a MsgBox.
It will show it on the currently displayed Page.

 

[Jeffrey Cameron]

an sms is received and the code on module1

I think a better approach would be to have a service handle the SMS, then have the service raise a common event that each form you need may handle.

 

[amorosik]

To just show a MsgBox I think it's not needed to make a Class.
Try this.
It has a Service that every 5 seconds show a MsgBox.
It will show it on the currently displayed Page.

The entire trick is the row
CallSubDelayed3(B4XPages.GetManager.GetTopPage.B4XPage, "ShowMessage", "FROM SERVICE", "WORK!!!")
that call a subroutine 'ShowMessage' on a form actually displayed
Timer is not needed
Perfect for me

 

[amorosik]

I think a better approach would be to have a service handle the SMS, then have the service raise a common event that each form you need may handle.

I'm interested about your post, why you think that a better approch is via service?
Exactly for wich reason?

 

[GMan]

If you dont click OK In the given example, after 5 seconds a 2nd MsgBox appears over the other one.
So, after 15 secs you have to click OK 3 times

 

[amorosik]

If you dont click OK In the given example, after 5 seconds a 2nd MsgBox appears over the other one.
So, after 15 secs you have to click OK 3 times

Yes this is a cons
But there are a pro to use the service approch?

 

[Sagenut]

Timer was just to simulate some work from the service.
In your project the event will be raised every time that an SMS is received, if I understood correctly.

 

[Jeffrey Cameron]

I'm interested about your post, why you think that a better approch is via service?
Exactly for wich reason?

I'm sure @Erel can explain why better than I can.

My general design approach is to put anything that deals with external input (e.g. async, database, SMS, telephony, etc.) inside services and then have the service raise events that activities can handle.