Known Bugs and Issues

The following problems are known to me, either through my own testing or other people's reports:
  • WinBar sometimes crashes after changing colors a lot. I can't figure out what causes this; the code seems sound.
  • WinBar sometimes displays a wrong color after selecting.
  • The total amount of physical memory is 1 or 2 MBs less than it should be. This is normal; the number displayed is the amount reported by Windows. You can fix it by setting a memory size bias.
  • The CPU usage briefly rises to 100% when adjusting CPU module options and when closing the configuration window. This only happens on NT based systems.
  • On Win9x systems, the CPU usage may be abnormally high (60% or higher) even though your system is idle. This is a bug in Windows 9x.
  • On Win9x systems, the lock keys status LEDs may not be updated until you mouse over them. This seems to be a Windows problem.
  • If you have some other AppBar (such as the Windows taskbar) docked at the side of your screen, WinBar may leave a blank corner. You can correct this by starting WinBar with the -screen argument.
  • On Windows XP systems, the main window is hidden when you use explorer's Show Desktop function. This is a bug in the Windows XP shell, which tells WinBar that a fullscreen application has started when in fact it's just the Show Desktop function. I haven't found a workaround for this yet.

    If you find a bug that is not listed in the FAQ or the bugtracker, please let me know by mailing me at johnwoo@winbar.nl.