Timothy
  • Timothy
  • 100% (Exalted)
  • Flock Leader Topic Starter
2008-05-28T16:20:04Z
Here we are -- Release Candidate Stage. Assuming no major bugs are reported over the next week, the next version of RD Tabs will have the debug flags turned off and will be the RTW version of 2.1! (Note: the documentation is almost finished, but the version included in this release is still pretty out of date.)

EDIT: The automatic RD Tabs Update link was incorrect for the 64-bit version. This has been fixed! Sorry about that.

Download links...
x86: http://www.avianwaves.co...-DO_NOT_REDISTRIBUTE.msi 
x64: http://www.avianwaves.co...-DO_NOT_REDISTRIBUTE.msi 

Here is the changelog...
- Added a few more disconnection error codes with regard to Network Level Authentication.
- Fixed a bug where you could still click on the status bar "cancel" button even during times that the remote desktop client control will not accept cancellation, such as during pop-up dialog boxes (can cause odd RD Tabs behavior).
- Added a new catch for another COM exception generated when the RDP control is not registered correctly. This will allow you to automatically launch the self-repair utility if RD Tabs fails as a result.
- Added a new feature to the options where you can disable the input hooking feature that RD Tabs uses for various parts of the application. Certain computers (certain models of laptops mostly) don't respond well to low-level input hooks and RD Tabs may have lags/freezes/slow-response when certain basic window functions are clicked (such as minimize, restore, maximize, or close). Look under the "General" tab in the options for this feature. Typically, if you are experiencing a lagging response to the afforementioned control box functions, disabling the mouse hook is sufficient. The keyboard hook appears to not cause any problems. RD Tabs will let you know which features are affected when you disable any low-level input hooking. Special thanks to the Avian Waves Forums members who reported, worked on, wrote code, and tested this issue with me (I was unable to replicate it on my test machines so the help was GREATLY appreciated).
- RD Tabs user Sebastiaan Brozius was able to convert the low-level mouse hook to an application mouse hook to fix the afforementioned "lag" problem on some computers due to the mouse hook. I'm still leaving the ability to disable input hooking in RD Tabs in case a future problem arises. Many thanks to Sebastiaan! Note: The keyboard hook cannot be converted to an application hook because a low-level hook is required to pre-empt the message pump BEFORE the remote desktop focus in order for the SysKey feature to work correctly. Since the mouse hook features (tab title bar mouse wheel scrolling) do not require a low-level hook, an application hook works just fine!
- Fixed a bug in the Connection Thumbnail Selector where it wasn't showing thumbnails of tabs that were hidden. This is directly related to the optimization made in 2.1.7 for hidden tabs to use less network bandwidth. I forgot to bring them back to a visible state before taking a screen shot.
- When you disconnect in a non-error state, the remote desktop will now provide you with the disconnection details (such as "session closed by remote server" or "sessions disconnected/cancelled by user" etc).
- Disconnection code "3" (disconnected by remote computer) was being called an "error" by RD Tabs, but it is not actually an error as it is a valid forceful disconnection usually by somebody at the console bumping off somebody logged on through remote desktop.
- The bugs are all pretty minor now, so I'm dubbing this Release Candidate. If there are no big errors in the next week, I will turn off debug mode, recompile, and RD Tabs 2.1 will finally be RTW! (Assuming I can finish the 2.1 documentation...)
sullysnet
2008-05-28T18:01:41Z
thank you I love your application and work =d{ would love to see many of the new features you have mentioned in the forum. When I get a chance I plan to donate 🙂
Iskander
2008-06-03T02:01:55Z
Hi Timothy,

<deleted>:^o

8-[ Sorry, had a problem with the Win-key combinations, but alas, you have to set a radio-button to 'on remote computer' for them to work on the 'remote computer'..... 😣

Timothy
  • Timothy
  • 100% (Exalted)
  • Flock Leader Topic Starter
2008-06-03T15:22:22Z
🙂 No problems, my friend!! There are a LOT of options available to remote desktop!
full film