Tooltipfixer is een klein programma dat volgens de ontwikkelaars een bug oplost die terug te herleiden is naar Windows 95, en sinds de release van dat besturingssysteem door Microsoft nog steeds niet opgelost is. Het programma zorgt er voor dat de tooltips - ook wel ballonnetjes genoemd - niet meer achter de taakbalk worden gerenderd, maar juist voor de taakbalk worden gezet. Enkele dagen geleden heeft Neosmart, de ontwikkelaar achter het programma, in de vorm van versie 2.0 een nieuwe build van Tooltipfixer uitgebracht. De nieuwe versie kan door te klikken op deze link voor Windows 95 en nieuwer worden gedownload. De release notes van Tooltipfixer 2.0 zien er als volgt uit:
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 incessantly then you can choose to only run TTF when you need it!
ToolTipFixer 2.0 – (Oct. 14, 2008):ToolTipFixer 1.0.1 – (Jun. 27, 2007):
- Installer options for service vs. application
- Minimize memory usage as much as possible
- Create standalone ToolTipFixer module
- Remove .NET Dependencies
ToolTipFixer 1.0.0 – (Jun. 26, 2007):
- Debug file "c:\t.txt" still created
- Glitch in uninstall may not remove service
- Low-level improvements to memory usage
- Improvements to window handling
[break]
- Initial Release
Voor en na gebruik van Tooltipfixer