Răsfoiți Sursa

I don't think we need or want AttachThreadInput()

David Rose 16 ani în urmă
părinte
comite
e4169cfbc9
1 a modificat fișierele cu 8 adăugiri și 2 ștergeri
  1. 8 2
      panda/src/windisplay/winGraphicsWindow.cxx

+ 8 - 2
panda/src/windisplay/winGraphicsWindow.cxx

@@ -888,16 +888,22 @@ open_regular_window() {
       y_origin = _properties.get_y_origin();
     }
 
+    nout << "Creating embedded window\n";
     _hWnd = CreateWindow(wclass._name.c_str(), title.c_str(), 
                          WS_CHILD | WS_VISIBLE | WS_CLIPCHILDREN | WS_CLIPSIBLINGS ,
                          x_origin,y_origin,
                          x_size, y_size,
                          _hparent, NULL, hinstance, 0);
-    
+    nout << "Done creating embedded window, _hwnd = " << _hWnd << "\n";
     
     if (_hWnd) {
       // join our keyboard state with the parents
-      AttachThreadInput(GetWindowThreadProcessId(_hparent,NULL), GetCurrentThreadId(),TRUE);
+
+      // Actually, let's not.  Is there really any reason to do this?
+      // It causes problems with the browser plugin--it deadlocks when
+      // the parent process is waiting on the child process.
+      //AttachThreadInput(GetWindowThreadProcessId(_hparent,NULL), GetCurrentThreadId(),TRUE);
+
       // set us as the focus window for keyboard input
       SetFocus(_hWnd);