Hi all,
Let's say I've 3 or 4 dialogs and each one has it's own layout file.
From what I've been learning about B4X, we build the layouts, we generate the members (variables and methods) and we associate the code to them (great).
My question is:
What's the best practice in organizing the code for this? On the apps I've been developing I end up having a lot of:
If we've a layout that has multiple buttons and uses 3 or 4 different dialogs, this list start betting big... also, if the dialogs have similar buttons, let's say "Save" button, we end up having:
btnSave_Click
and we need to start thinking on having a dialog name prefix to identify the method, like:
btnDlg1Save_Click
Is there any "best practice" to deal with this? Is there any recomended way to organize the code for these situations or this is the way it is and I'm on the right path here?
Thanks for the help.
Let's say I've 3 or 4 dialogs and each one has it's own layout file.
From what I've been learning about B4X, we build the layouts, we generate the members (variables and methods) and we associate the code to them (great).
My question is:
What's the best practice in organizing the code for this? On the apps I've been developing I end up having a lot of:
If we've a layout that has multiple buttons and uses 3 or 4 different dialogs, this list start betting big... also, if the dialogs have similar buttons, let's say "Save" button, we end up having:
btnSave_Click
and we need to start thinking on having a dialog name prefix to identify the method, like:
btnDlg1Save_Click
Is there any "best practice" to deal with this? Is there any recomended way to organize the code for these situations or this is the way it is and I'm on the right path here?
Thanks for the help.