I don't understand your code but if I put something like
ToastMessageShow("btFDOk_Click", True)
in each of your click events then I can see that they are being called OK.
Thanks. I've added ToastMessages to all my Click event subroutines. I've also added a screenshot from my Samsung Vibrant to the zip file.
On both my Samsung Vibrant (Android V2.2) and my Acer A500 (Android V4.03) none of my click events fire; no ToastMessages show. The significant click events are for 1. the up arrow at the top, 2. clicking on any of the lines in the ScrollView to select a file or move to a directory, and 3. my two buttons "Ok" and "Cancel". The two buttons from the Custom Dialog, "Ok" and "Cancel", at the bottom both work on my devices. If I get the CustomDialog to work I will remove my Ok and Cancel buttons since they will be redundant.
If in your testing the ToastMessages display upon clicking, that will be interesting.
If I comment out the three lines 278, 279, and 280, then re-compile and re-run, this removes the CustomDialog. Now all my events fire properly on my devices and the ToastMessages show, but I lose Modal-ness, which I really like.
Thanks,
Barry.