Changes since 0.4.5:

• Added a new "supported only" mode. If the XALIA_SUPPORTED_ONLY environment variable is set to a value other than "0", Xalia will only activate for windows that are considered "supported". These are windows that use only controls and toolkits that are expected to work, or from applications that have been specifically tested.
• GUDL: Added a "wait" action, meant for executing other actions with a delay. Usage: wait(number_of_seconds)
• Updated SDL to 2.30.11.
• GUDL: Added support for reading environment variables. Usage: environ.NAME_OF_VARIABLE
• Interaction with the "Input" tab of Unity3D launchers on Windows has been disabled. For many games, the "Input" tab is simply broken, ineffective, or responds to gamepad input in a way that breaks Xalia (specifically, it listens for gamepad input at all times, and binds the most recent input when activated).
• GUDL: Added the is_hwnd_dialog property for consistency with other provider properties.
• Win32: Added support for SysLink controls.
• Win32: Fixed a bug where controls with MSAA providers would be accessed via UIAutomation.
• Win32: Fixed handling of VT_EMPTY returns from get_accChild.
• Buttons with the "owner draw" flag are now only targetable if they have no child controls. Sometimes these "owner draw" buttons are used as frame controls (which for some reason on Win32 are buttons), and there's no reliable way to tell, but this should work in most cases.
• Fixed RPG Maker games having a targetable control detected in the upper-left corner.
• Marked "Trine" and "Trine 2" launchers as having built-in gamepad support.
• Win32: When MSAA controls return the "client" role, this will now be reported only in the msaa_role property, while the role and control_type generic aliases will fall back to other sources.