On Wed, Jun 01, 2011 at 04:28:56PM +0200, Christian Ehrlicher wrote: > Hi, > > I've a problem with xembed + qt (4.7,4.8) + fvwm2 (2.6.1). The attached > testcase works fine with kde. > > How to reproduce: > - compile the two programs (qmake, make) > - start 'x11embedwidget' > - start 'x11embedcontainer <winId>' whith the winid provided by x11embedwidget > > On KDE I now see a red window and when pressing a key both applications > receive this event (the widget will receive it twice - don't know if this is > correct but that's another problem).
It's correct. > On Fvwm2 I see a blue window and when I resize the window a small red area > appears. Key events are only visible on both applications when the mouse > cursor is in the blue area. In the red area the embedcontainer doesn't get > keyevents at all. That's right again, because one is a child of the other internally. > When I comment out the calls to 'setGeometry(0,0,100,100)' in one of the > applications, I only see the red window. The problem with the keys then only > appears sometimes (maybe depending on the focus). > > I hope someone can take a look on this or at least can give me some hints > where inside the fvwm source the xembed handling occours so I can look by > myself. But FVWM isn't doing anything wrong that I can tell -- and FVWM isn't even XEmbed aware. All that's happened here is yout widget has been reparented inside the container you've setup -- which itself is managed by FVWM. Key presses to the application (top-level) will propagate down to the descendents like any other window. Of course, this will depend upon the attributes you've set for the container as to how it is to behave if it is ever reparented. I've not looked at your source code, as I have no interest and don't understand Qt; something, incidentally, I want to remain clueless about. -- Thomas Adam
