Since I can't replicate the issue, that's not a bad idea. It's a 2005 project currently. It's pretty large. I'll zip it up and split it. Excuse the sloppy code! The code is not exactly secret, so an NDA is not necessary. However, the same license applies as is shown in the installer. You just now officially have the requisite "written permission" to examine it. I just ask you don't fork RD Tabs and make your own product. 🙂 That's the only thing I'm worried about. 🙂

About the forking: don't worry. That's something I wouldn't like, either...
Maybe I can help you tidy up some things... (maybe not....) 😉

Let me know how it goes. Feel free to let me know if I can do anything to assist.

It looks like the culprit has been found and a possible solution has been mailed to TImothy so he can incorporate it into the source. Since 2.1.8 Beta just has been released, I think this will be one for the 2.1.9-release... 😉

Timothy, Anything that you can be do to get me a speedy maybe non standard build I'm in favor of! I'm dying over here! :|

dpreuss - Unfortunately, Iskander's fix broke other functionality, so I had to abandon it. 😞 But now that I know where the problem is, I made a change that removes the mouse hook that he discovered that was holding up the control box processing in your cases. I don't know if it works because I can't test it on my computer (I never experienced the problem), but I emailed it to Iskander to test, and can email it to you if you contact me via the contact form (top of this page) so I have an address to email it to. In the interim, if you go into the Avian Waves\RDTabs\user.config file in your application data folder, you can set the property DisableGlobalMouseHook to True and that should provide a temporary fix. Using the mouse scroll wheel to scroll tab titles will no longer work after setting that property. The fix I can email you can use the scroll wheel without the mouse hook, so I was able to remove the mouse hook completely.

I just thought of something. Both of you are using Dell laptops. Do both of you have Dell Quickset installed? Quickset uses low-level input hooks (the thing RD Tabs is trying to use but is freezing in your cases). I'm wondering if that's part of the problem. I don't have a Dell laptop to test on at the moment (my Dell laptop is 64-bit Vista and my laptop doesn't have a 64-bit version of Quickset, so I can't install it). I just wonder if maybe they are somehow "competing" at the low-level for certain types of input...

Also, let me know if disabling RD Tabs' low-level mouse hook fixes the problems at all! I'm very interested to see where this goes.

Disabling the low level check resolved the issue for me! I don't have quickset installed. Thanks to both of you for getting us this far. I didn't even know you could scroll wheel tabs so it's no functionality lost for me and a whole lot of happiness gained.

Do you have the Alps or Synaptic touch pad driver? Does the problem occur with a USB mouse or with the touchpad or both? I know that multiple monitors are involved, but I'm trying to narrow down something in the pointing device input layer. In the interim, I'm very glad the workaround is acceptible for you!

It happens with any pointing device whether it be a logitech usb mouse or the touchpad

Iskander reworked the mouse code and sent me an update. I'm going to test it on Tuesday. Either way, I'm going to keep the ability to turn off mouse/kb hooking, just in case a new problem pops up later on. Since the keyboard hook isn't causing problems at the "low level" i'm going to keep that code the same as the original as app-level hooking doesn't seem to pre-empt the remote desktop from tests I did a while back, which keeps the syskey feature from working correctly.

Hoping the new code works! Thanks, both of you, for your diligent efforts at debugging this problem. I'm sure you helped lots of other users and I never would have been able to fix it on my own since I can't replicate it!

:-)

I just installed the new code by Iskander. It seems to work great for me! I will be introducing it into the 2.1.9 release candidate.

dpreuss - Please re-enable mouse hooks on 2.1.9 when it is released (possibly today, but maybe later this week) and see if the problem is fixed once and for all!

Everyone here is working as if it were 2.0.13 :)

Thanks to both of you for getting it resolved and implemented. Now I just wait for more command line support 🙂