You probably won't need to do much with this class. wxEuphoria creates a wxApp object automatically.
Yields control to pending messages in the windowing system. This can be useful, for example, when a time-consuming process writes to a text window. Without an occasional yield, the text window will not be updated properly, and on systems with cooperative multitasking, such as Windows 3.1 other processes will not respond.
Caution should be exercised, however, since yielding may allow the user to perform actions which are not compatible with the current task. Disabling menu items or whole menus during processing can avoid unwanted reentrance of code.
Note that Yield() will not flush the message logs. This is intentional as calling Yield() is usually done too quickly update the screen and popping up a message box dialog may be undesirable.
Calling Yield() recursively is normally an error and an assert failure is raised in debug build if such situation is detected. However if the onlyIfNeeded parameter is true, the method will just silently return false instead.
This is the procedure that should be used to exit the program. If you create an on close event for your main frame, this must be called from the event handler, or your application will not close. wxEuphoria automatically does this for you if you do not define an on close event.
Returns the application name.
wxWidgets sets this to a reasonable default before calling wxMain, but the application can reset it at will.
Returns the application's vendor name.
Returns true if the application is active, i.e. if one of its windows is currently in the foreground. If this function returns false and you need to attract users attention to the application, you may use request_user_attention() to do it.
Sets the name of the application. The name may be used in dialogs (for example by the document/view framework). A default name is set by wxWidgets.
Sets the name of application's vendor. The name will be used in registry access. A default name is set by wxWidgets.