K
Keith Patrick
I've noticed this for a while with Outlook 2003, and it drives me up the
proverbial wall: if I use Outlook, I can move my mouse pointer all over the
place, no problem (as expected). However, if my printer happens to go to
sleep or get turned off (which is the usual status), simply moving my mouse
pointer *over* the Print toolbar button causes the button to act as if I
pressed it while it literally sits for 30 seconds waiting for a printer
response. This has happened for well over a year, but I have never read
anything about this phenomenon. It's like the office team put some kind of
non-threaded print job in the MouseOver event handler instead of MouseDown,
but it drives me absolutely nuts, as it hangs the entire app
proverbial wall: if I use Outlook, I can move my mouse pointer all over the
place, no problem (as expected). However, if my printer happens to go to
sleep or get turned off (which is the usual status), simply moving my mouse
pointer *over* the Print toolbar button causes the button to act as if I
pressed it while it literally sits for 30 seconds waiting for a printer
response. This has happened for well over a year, but I have never read
anything about this phenomenon. It's like the office team put some kind of
non-threaded print job in the MouseOver event handler instead of MouseDown,
but it drives me absolutely nuts, as it hangs the entire app