Hi,
please add these 2 warning notices if possible.
1) Warning if a Msgbox2Async is built into a class.
I knew that you can't put Msgbox2Async in a class, but you often forget it.
2) Warning if a procedure with an incorrect number of parameters is started with CallSubs.
This can happen if you use the same code module in different apps and you change the number of parameters.
You can use Msgbox2Async in classes as long as the class has an activity context. As usual if you switch to B4XPages, you can forget about such issues.
You can use Msgbox2Async in classes as long as the class has an activity context. As usual if you switch to B4XPages, you can forget about such issues.