Android Question Another wary to call Subs

This is the only way to do it directly.
What is the problem you face with this?

To make it cleaner I usually set a module or parent object in each class that sets it up in Initialize.

The problem is for lisibility and maintenance.
It is more clear to read Main.btn2_click than CallSub(Main, "btn2_click")
And if one day btn2_click becomes btn3_click, the error will not be detected on compilation.

I have some classes and they call each other. But I don't know how to manage these function in the Main code

In that case, I would do it differently.

In the class initialize, create something like
Sub Initialize(pModule as Object, pEventname as String)

and then assign them to local class variables (mModule, mEventname).

Later when you need to call the main activity, do:
CallSub(mModule, mEventname)

Then in the Main activity,
have the event as a sub:

Sub clsManager_Update
btn3_Click
End Sub


This way, all the view or dependent logic is still inside the activity, and the class can be reusable.

You can have a look at some examples of classes on the forums.