Hello,
I've done some more testing since my last message. I've also upgraded my TP++ and PPA versions and the same problem is still happening.
What I have discovered is this: If the screen resolution/magnification is set at anything *except* 100% the issue happens. I tried 125, 150, 175, 200.
As a workaround I've reduced my screen resolution from 2880x1800 which is what I would like it to be set at down to a resolution that allows me to keep the magnification setting to 100%. It works correctly in this scenario. Obviously I would like to be able to use it at my desired configuration of 2880x1800 w/150% magnification.
I see that another user has posted regarding the same issue.
The other issue I mentioned about the mouse not moving fast enough to suit my ideal usability preferences you suggested turning on the turbo option. I already had that option on and it just isn't fast enough for me, especially at full retina resolution. As I stated before I typically set my mouse speeds at max or near max (with acceleration) depending on the mouse manufacturer/driver. I prefer it that way but when others try to use my computers they have to change it back to normal because they simply can't control the mouse at my desired speed. I guess I'd like you to enhance the product to allow for much faster speeds and the equivalent of "acceleration" where the mouse moves fast the faster i move the mouse (or in this case the fingers on the trackpad. This is a feature request and is not nearly as important as resolving the bug issue above.
The other thing I notice is that with PPA installed my keyboard backlights do not some on, ever, as far as I can tell. I really like to have my keyboard backlit so if you have any idea on that I'd really appreciate it.
Just as a reminder my Mac is a: Macbook Pro 15" (Retina) - Late 2013. As I mentioned earlier in this thread I do have VMWare Fusion 6 Pro installed into this Boot Camp partition since there are times I want to quickly use something from Windows but not have to boot directly into the Boot Camp Windows partition. However, since I've installed your utilities I have *not* attempted to run my BC Windows through VMWare Pro 6, I've only booted directly into the Windows partition.
Hopefully this information will help you resolve the 3 finger issue which is critical. As soon as this is resolved I will gladly pay for the product. In addition I hope you will consider my feature request regarding mouse speed and look into the keyboard backlighting issue.
Please let me know if there is anything else I can do to help you diagnose and/or resolve these issues.
Regards,
Kelly E Major
@kemajor: First, please let me clarify the situation regarding the Power Plan Assistant and keyboard backlight. Actually, this is the feature of Power Plan Assistant. Furthermore, it's top feature. The story is, absolutely most people had been irritated with keyboard backlight being forced on the maximum level every time they boot to Windows. I had been asked many times to fix this, and I have created Power Plan Assistant with this feature being one of its master features. Please note that the keyboard backlight is still controllable via top row keyboard keys, it just doesn't run at full brightness after you login to Windows. With Power Plan Assistant it shall gently dim to a zero level instead. If you prefer the keyboard backlight being set to max after you login to Windows, you can safely uninstall the Power Plan Assistant, as it's mandatory to install it only once, before the Trackpad++. To uninstall correctly, please quit the Power Plan Assistant first: right-click its tray battery icon and choose 'Exit'.
@MattNaddeo, @kemajor: Now about the Trackpad++ 3-finger drag. We are getting as close to locating the problem, as never before. I friend of mine who owns Late-2013 Retina Macbook Pro has agreed to sacrifice his perfectly working Windows 8.1 installation and is going to put Windows 7 instead. Thus, soon I will be able to personally install the Trackpad++ and observe the situation. As I indicated in the previous posts, on his Late-2013 rMBP the 3-finger drag feature works with any DPI scaling and any resolution - verified by me personally. But, verified only in Windows 8.1, which may not be the same as 8 and 7 in this regard.
@kemajor: First, please let me clarify the situation regarding the Power Plan Assistant and keyboard backlight. Actually, this is the feature of Power Plan Assistant. Furthermore, it's top feature. The story is, absolutely most people had been irritated with keyboard backlight being forced on the maximum level every time they boot to Windows. I had been asked many times to fix this, and I have created Power Plan Assistant with this feature being one of its master features. Please note that the keyboard backlight is still controllable via top row keyboard keys, it just doesn't run at full brightness after you login to Windows. With Power Plan Assistant it shall gently dim to a zero level instead. If you prefer the keyboard backlight being set to max after you login to Windows, you can safely uninstall the Power Plan Assistant, as it's mandatory to install it only once, before the Trackpad++. To uninstall correctly, please quit the Power Plan Assistant first: right-click its tray battery icon and choose 'Exit'.
@MattNaddeo, @kemajor: Now about the Trackpad++ 3-finger drag. We are getting as close to locating the problem, as never before. I friend of mine who owns Late-2013 Retina Macbook Pro has agreed to sacrifice his perfectly working Windows 8.1 installation and is going to put Windows 7 instead. Thus, soon I will be able to personally install the Trackpad++ and observe the situation. As I indicated in the previous posts, on his Late-2013 rMBP the 3-finger drag feature works with any DPI scaling and any resolution - verified by me personally. But, verified only in Windows 8.1, which may not be the same as 8 and 7 in this regard.
@ayurmedia: Trackpad++ driver is only for the real Windows 7/8.1 installation via Boot Camp, so Parallels (and other VMs) are definitely incompatible. The driver is already deactivated if VM boot is detected, so the problems, if any, are on the VM vendor's side. Honest 'no' is better than false 'maybe': I cannot be responsible for anything that happens in unsupported environment, so whereas I wish to help, there is nothing to do from my side.