What’s New in the Latest Release of the 2X Client for Android?
2X Software recently released a new update to the popular 2X Client for RDP/Remote Desktop. The 2X Client for Android v10.1.1247 includes some new features and improvements to the previous version which we will discuss in this article.
Google Play has the following information but we will describe each item in more detail:
- Added support for custom resolution sizes
- Added support for 3rd party applications to use the 2X Client
- Improved support for Asus Transformer
- Improved mouse right click functionality
- Improved external mouse and mouse pad interactions
- Fixed sending correct Unicode characters in username and password when logging on to a Terminal Server
Added support for custom resolution sizes
In this version, the user now has the ability to configure the desired server side resolution not only from a set of pre-set values but also custom sizes.
Added support for 3rd party applications to use the 2X Client
The new client can now be integrated with other applications that need to connect to remote desktops. A very simple API is available which makes it possible to deploy specific connections. For more information please check this manual link.
Improved support for Asus Transformer
The Asus Transformer running Android v3.2.1 supports mouse hardware and can send input events for left and right clicks. These events are now supported like the events of other devices running Android OS v4 or higher.
Improved mouse right click functionality
If the action bar is visible on screen, the right mouse clicks were sent with the wrong coordinates to the server. This is now corrected.
Improved external mouse and mouse pad interactions
Since we can now distinguish between left and right click, the dragging action we normally use when using standard desktops is also now available in this version. This will however need an OS version that can send right clicks.
Fixed sending correct Unicode characters in username and password when logging on Terminal Server
In the previous versions if you configured a username which has non latin characters, these were not sent correctly to the server resulting in an invalid username so you had to type it again in the remote session. This is now corrected.
