ToolTipFixer sits silently and invisibly in the background, intercepting this problem and fixing it as it happens 芒?? letting you read those ToolTips and use your PC the way you should be able to.
Now for the good stuff: the number one request we've had was to eliminate the Microsoft .NET Framework as a requirement for using ToolTipFixer. As a matter of productivity and preference, Microsoft's .NET Framework has a special place in our hearts, but we realize that many people would prefer something a bit芒?娄 lighter and as such ToolTipFixer 2.0 has been rewritten from scratch in C++ with no dependencies 芒?? not even the MSVC++ runtime libraries.
The second oft-made request was improvements to ToolTipFixer's memory usage. This particular component is tightly-tied to the development platform of choice, and with the switch over to unmanaged C++, it's become possible to further-tune the amount of memory that TTF uses and bring it down as much as possible, something that芒??s not in the developers' hands when using the .NET Framework 芒?? which, with its automated garbage cleanup, makes memory usage highly variable at best.
TTF 2 has drastically improved memory management 芒?? it芒??ll take so little memory, you won't even know it's there (from 0.3 to 1.5 MiB in our extended testing, depending on OS and platform).
Then there are those 64-bit Windows users, and more of them than ever before. Just because you have 4+ GiB of RAM in that machine of yours doesn't mean you can芒??t get rid of this bug too 芒?? ToolTipFixer 2.0 has full support for Windows XP/Vista x64!
And to save the best for last, ToolTipFixer can now be run in what we call "standalone mode." During setup, you芒??ll have the option of either installing TTF the traditional way 芒?? as a system application sitting silently and invisibly in the background 芒?? or as a standalone module that you run only when you need it. Some people experience the tooltip corruption problem less often than others, and if it doesn't bother you ...
