From: quendezus (quendez_at_[hidden])
Date: 2002-01-16 04:25:35
--- In boost_at_y..., "David Abrahams" <david.abrahams_at_r...> wrote:
>
> ----- Original Message -----
> From: "Jason Shirk" <jasonsh_at_m...>
>
> > I assume the question is how to suppress any message box or
window that
> > any random assert implementation might use.
> >
> > If so, I don't have the answer. The ideas I do have are too
complicated
> > to bother with for this problem.
>
> I remember a trick I had to use when imlementing printing on
windows, in
> order to get a record of the printer's settings without making them
deal
> with a dialog box. It involved some kind of hook that posted an
event to
> press the dialog's OK button before it was ever seen. This was from
MSDN,
> I'm pretty sure. Ugly, but effective.
>
> -Dave
If it can help, I have a very small win32 tool that runs an
executable and waits for its completion. After a certain amount of
time, if the executable has not terminated, the tool closes it by
sending WM_CLOSE events to all windows. This works well for programs
that generate assertions on win32 (in fact, the tool has been
designed for this purpose).
Sylvain