There is no member named SetDeviceOrigin.Disabling display 1 to avoid infinite recursion.

The only way I can prevent this crash is by either commenting out the contents of UpdateButtonOnScreen or preventing it being called on rollover (i.e. it gets called at left button down/up, but not when the mouse hovers over the button).

I'm using 0.92 as published on this site. Should I be using the source from the wxW CVS?

Last edited by gnschmidt on Fri Oct 20, 2006 5:13 am, edited 1 time in total.

I narrowed the problem down to the close-on-click behaviour. The error occurs only when the mouse moves while the close pane is pressed and the left button is released on another pane (or worse in between, in which case a raw NULL pointer is dereferenced in UpdateButtonOnScreen).

Not all occurrences are down to NULL pointers, though: at times moving to another pane managed by wxFrameManager is enough to crash the application.

My solution is to add the following lines near the top of UpdateButtonOnScreen at framemanager.cpp l. 3345 (immediately after wxDocUIPart *hit_test = HitTest(event.GetX(), event.GetY());).

Just a quick note to say that I recently took the CVS version and this crash persists. I know the proposed patch affects the symptom rather than the cause, but it's a little worrying that anyone can crash wxAUI apps by clicking on a close button and releasing the mouse button between panes or (sometimes) just on another pane.