Use timer to test multiple dialogs in Python and RUby

Description:

In C++, as long as the generated code compiles, it will probably run. However, with Python and Ruby, errors in code generation may not show up in a dialog until the dialog is created. That means coverage for multiple dialogs means that each of those dialogs must be opened.

A way to enable testing all dialogs would be to have a global boolean variable that dialogs would access in their OnInit handler. If the variable is true, then create a timer with a delay of a few seconds. The event handler for the timer should post an event to a cancel button and then shut down the timer. This should result in the dialog being closed. This would make it possible to have a test that turns on the global variable, and then creates and displays a series of dialogs. This would ensure that the syntax for all the dialogs is correct, since both Python and Ruby should stop of at the first error it encounter.