Dave Page wrote:
>
> Problem is that in both cases I get a crash in wx code, when none of our
> functions are on the call stack, after the new dialogue has been created. If
> running in the VC++ debugger, it breaks telling me I've hit a user
> breakpoint inside wx's assert handling code (where there definitely aren't
> any breakpoints that I've inserted). It won't let me break properly from the
> assert dialogue.
After lengthy investigation the answer is quite simple: wx is broken.
The dialogs sample has the same problem.
Regards,
Andreas