🚀 go-pugleaf

Hi Gary,
> I'm trying to better understand the Win32 api by making a MDI 
> application with toolbar support.
[...]
> Has anyone out there been thinking about how to trigger on the 
> entering the idle state? Does windows post WM_ENTERIDLE at the 
> right time? Is there a better way to trigger on enter idle state?

IIRC, the WM_ENTERIDLE message is used mainly with dialog boxes and menus. 
An application is traditionally considered "idle" when its message queue is
empty.   You can use the PeekMessage() function to determine if there are
any messages in the queue; the function will return zero if there are no
messages, indicating an idle state.  The TApplication class, for example,
calls the PeekMessage() function from within its main message-processing
loop [embedded within TApplication::Run()]: if PeekMessage() returns
non-zero, the message is dispatched and processed; if PeekMessage() returns
zero, various idle-related events are fired (e.g., TApplication::OnIdle,
TCustomForm::UpdateActions).  If you're creating a VCL application, stick
with the TAction and TActionList classes.  If you're creating a pure API
application, you'd call PeekMessage() within your message-processing loop to
determine whether to process the message [e.g., via GetMessage()*] or
whether to call your "OnIdle" code.

* You'd call GetMessage() if you used PM_NOREMOVE with PeekMessage(); if you
use PM_REMOVE, you've already removed the message from the queue so you'd
call TranslateMessage() and DispatchMessage() directly.

HTH,
-- 
Damon (TeamB)
BCBCAQ--http://bcbcaq.bytamin-c.com