Re: [wxVTK] wxVTKRWI, wxAuiManager and reparenting

[Mathieu M. <mat...@gm...>]

Hi Quoc Cuong

On Sat, Aug 23, 2008 at 10:27 PM, PHAM Quoc-Cuong 203899
<Quo...@ce...> wrote:
> Hi
> I use a wxVTKRenderWindowInteractor (1.3 and VTK 5.0.4) in a wxAuiManager pane (wxWidgets 2.8.7) (like in thread http://sourceforge.net/mailarchive/forum.php?thread_name=ba0d923e0804211200o65a12c6dtce4ccbf846bdd8ea%40mail.gmail.com&forum_name=wxvtk-users)

Link does not work for me :(

> The pane is dockable and when moving the pane, the application crashes with the following error:
>
>
> Gdk-ERROR **: The program 'BaliseDAM' received an X Window System error.
> This probably reflects a bug in the program.
> The error was 'BadWindow (invalid Window parameter)'.
>  (Details: serial 7 error_code 3 request_code 2 minor_code 0)
>  (Note to programmers: normally, X errors are reported asynchronously;
>   that is, you will receive the error a while after causing it.
>   To debug your program, run it with the --sync command line
>   option to change this behavior. You can then get a meaningful
>   backtrace from your debugger if you break on the gdk_x_error() function.)
> aborting...

Yup, I got that one quite a few time when developing wxVTK :)

> It appears that the error occurs in the function Render() in the case of reparenting (indeed, wxAuiManager creates a floating frame that becomes the new parent)

If I understand what you are syaing we are entering wxVTKRWI::Render()
function, then goes to the second if: if ( GetHandleHack() )

But for some reason the value return by GetHandleHack is not a valid
window anymore, right ?

Can you print the value of those handles ? If you are not making any
progress, please send a small example to reproduce the issue.

Thanks,
-- 
Mathieu