[Pidgin] #5248: URI protocolhandler invocation cant find pidgin window (windows)

Pidgin trac at pidgin.im
Tue Mar 18 19:24:46 EDT 2008


#5248: URI protocolhandler invocation cant find pidgin window (windows)
---------------------+------------------------------------------------------
Reporter:  jblittle  |       Owner:  datallah           
    Type:  defect    |      Status:  new                
Priority:  minor     |   Component:  winpidgin (gtk)    
 Version:  2.4.0     |    Keywords:  uri protocolhandler
 Pending:  0         |  
---------------------+------------------------------------------------------
 I couldn't get the "pidgin --protocolhandler=" stuff to work.  It
 complained it couldn't find the running version of pidgin.

 I dug into the code (2.4.0), and did some tests, and I think I see why.
 The code in win32/winpidgin.c:handle_protocol(), calls FindWindowEx() to
 search for a Pidgin message window by window class name, but specifies a
 NULL window name (last arg to FindWindowEx).  However, when that window is
 created in win32/gtkwin32dep.c:winpidgin_message_window_init(), it is
 given the name "WinpidginMsgWin".

 The handle_protocol() code should specify the correct window name that was
 used to create the window.  Using an external Python script with pythonwin
 extensions, I can find the window calling FindWindowEx with the correct
 classname and window name, but not calling it the way Pidgin calls it.

-- 
Ticket URL: <http://developer.pidgin.im/ticket/5248>
Pidgin <http://pidgin.im>
Pidgin


More information about the Tracker mailing list