>I am having some strange behavior with a system tray routine. After activating it it appears to work properly sending the proper messages to the application (maximizing it, sending tray menu selections to the app for processing, etc.) - all is normal. But...
>
>Minimize the application for a while (times vary but I can generally reproduce it if I leave it alone for a half hour as many of my clients are apt to do) and it seems that the application 'goes to sleep'. I can confirm that the systray object is sending proper messages to the application through the windows api; however, the application does not appear to process them UNLESS I can restore it and get the mouse over it (so the windows mouse api methods fire I guess).
>
>Has anyone seen this behavior in a systray/application connected system? It all seems pretty straightforward in the code. It's as if there is something in the application that stops processing windows api stuff until it gets focus again - catch 22.
>
>Anyway, hope someone has seen this before and knows what I'm talking about.
>
>Thanks,
>
>Steven Supinski


Just an update. The bug appears to be with VFP based systray solutions and not in activex based ones. Eric on the Foxite site was able to reproduce another report of the behavior - we now have 3 reports - and Eric's reproduction. It's been reported to Microsoft. For now, be careful if you use the systray sample solution with your applications... Go for an activex based one until it's worked out.