In the attached project I am attempting to recreate an issue that I have found using Wait For with listeners created using JavaObject.
I created the setlistener sub as putting the code in the initialize sub seems to create issues with return values (Which I can understand, and seems best to avoid)
Debug Mode
If you run the app, the listener is called once, then the error:
java.lang.Exception: Sub textchanged_event signature does not match expected signature.
is thrown. (Unless the value happens to be an exit value on the first attempt)
If you uncomment the Sub with the same name, the app runs, but the Wait For callback is only called once (and the actual Sub is not called afterwards for the same event).
Release Mode
If you run the app, the listener is called once, but no error is thrown and the process times out. (Unless the value happens to be an exit value on the first attempt)
If you uncomment the Sub with the same name, the app runs, but the Wait For callback is only called once (and the actual Sub is not called afterwards for the same event).
I'm not sure this is a bug, maybe it needs to be set up differently.
I created the setlistener sub as putting the code in the initialize sub seems to create issues with return values (Which I can understand, and seems best to avoid)
Debug Mode
If you run the app, the listener is called once, then the error:
java.lang.Exception: Sub textchanged_event signature does not match expected signature.
is thrown. (Unless the value happens to be an exit value on the first attempt)
If you uncomment the Sub with the same name, the app runs, but the Wait For callback is only called once (and the actual Sub is not called afterwards for the same event).
Release Mode
If you run the app, the listener is called once, but no error is thrown and the process times out. (Unless the value happens to be an exit value on the first attempt)
If you uncomment the Sub with the same name, the app runs, but the Wait For callback is only called once (and the actual Sub is not called afterwards for the same event).
I'm not sure this is a bug, maybe it needs to be set up differently.