ui.wait(long) throws exception when called from test

[r4fterman]

Calling ui.wait(long) with just a miliseconds values throws the following exception:

java.lang.IllegalMonitorStateException: current thread is not owner

	at java.base/java.lang.Object.wait0(Native Method)
	at java.base/java.lang.Object.wait(Object.java:366)

Seems there is an issue to pause the current UI thread properly.

[r4fterman]

This is expected behaviour. Calling ui.wait(long) ends up on Object.wait(long) which is intended for thread communication.

Cause:

Here the expectation is to pause the UI execution for while so that a screen can come up or an execution can be finished.
Call ui.wait(long) is caused by misleation, because IUIContext offers wait(ICondition) methods.

Solution:
To avoid further confusion we will migrate away from methods called wait() to something more meaningful like waitFor(), await() or pause(). Overloading these methods with ICondition and timeout milliseconds will help the users to pick the right method.